link problem, huge number of files

Kristof · Post by **Kristof** » Thu Sep 29, 2005 11:32 pm

Hi,

I'm facing a bad problem while linker. The command stops quickly with a simple "make: *** [out] Error 1" and no error message.

My guess is that the number of objects I have is too big (330). (I'm recompiling C64 Vice emulator).

Someone know if there is a limitation of the number of objects that can be linked .... ??

Reducing number of object make the link work (I means, It fail with link error, but do not stop before making something).

Second question : I can create two libs files containing each half of the object. But what are the options of psp-ld to create a .a file ?

Thanks

holger · Post by **holger** » Fri Sep 30, 2005 12:48 am

static .a-archives are created using "ar cru <libname.a> <objects>".

Kristof · Post by **Kristof** » Fri Sep 30, 2005 1:01 am

Thanks, I'm going to try this ...

Kristof · Post by **Kristof** » Fri Sep 30, 2005 1:26 am

It works fine.

Thanks a lot !!!

Now I have another problem with macro PSP_MODULE_INFO in C++ that do not want to compile.

Post by **mrbrown** » Fri Sep 30, 2005 2:16 am

Kristof wrote:Now I have another problem with macro PSP_MODULE_INFO in C++ that do not want to compile.

You need PSPSDK from SVN, as the PSP_MODULE_INFO C++ thing was fixed shortly after the beta release.

Kristof · Post by **Kristof** » Fri Sep 30, 2005 3:01 am

Thanks mrbrown.

I'm not using beta release. I'm using subversion base from 31 August. I'll try an update to see if things have change whith that macro.

Kristof · Post by **Kristof** » Fri Sep 30, 2005 3:53 am

No way of compiling that line ... :(

I'm got rid of it by recopyng the whole macro in my main. This is not the best method, but it compile. Not sure it will work (actually it fails when launching, but I do not know why).

The outpatch.exe also say me "modulename" not found. I think all is linked.

This kind of stuff are the very bad side of developpement. So much time wasted.

groepaz · Post by **groepaz** » Fri Sep 30, 2005 4:00 am

outpatch? err....thats no more needed with the latest pspsdk... check one of the latest examples on how they are build, maybe that solves the problems for you.

Kristof · Post by **Kristof** » Fri Sep 30, 2005 4:05 am

In fact, I did not manage to compile samples in pspsdk. The auto generated makefile did not work for samples. So I do not have any valid make makefile for sample, and I took a makefile from another package "pspdev"...

As I'm very weak in makefile, I admit I do not understand everything around it.

I've check the makefiles in pspsdk and they are complex as hell. I'm going to check on the forum if someone already posted a simple single makefile for pspsdk samples.

--

For PSP_MODULE_INFO I'm going to forget C++.

groepaz · Post by **groepaz** » Fri Sep 30, 2005 4:24 am

uhm that indicates serious problems with your setup.... if pspsdk is installed correctly, the samples should just compile. i'd fix that first and then try again whatever you are doing.

holger · Post by **holger** » Fri Sep 30, 2005 4:44 am

Try using a Makefile from pspgl/test-*/, these are based on the pspgl/tools/psp-install script, this simplifies them somewhat.

Nevertheless your toolchain seems broken, maybe you're better deleting your toolchain installation and restart toolchain.sh to get a fresh one...

Kristof · Post by **Kristof** » Fri Sep 30, 2005 5:41 am

maybe you're better deleting your toolchain installation

I already spend hours installing it, better die than reinstalling the whole thing again :)

Try using a Makefile from pspgl/test-*/

I'll try this thanks.

PSP_MODULE_INFO is not compiling in C (different error).

Kristof · Post by **Kristof** » Fri Sep 30, 2005 6:07 am

Try using a Makefile from pspgl/test-*/

The PSP_MODULE_INFO of that package compile well. Thanks. :)

Now it produce a pbp but it does not boot... Still need to search...

Kristof · Post by **Kristof** » Fri Sep 30, 2005 6:59 am

I just compiled a sample of pspsdk (cube) using makefile and changing the minimum of things in it ... it generate a nice bootable elf, but that elf is not bootable "impossible launch".

Still need to read this forum again :)

groepaz · Post by **groepaz** » Fri Sep 30, 2005 7:21 am

try "make kxploit" :)

Kristof · Post by **Kristof** » Fri Sep 30, 2005 7:29 am

I'm already using the kxploit tool to transfert the eboot file to psp.

But thanks for hints. The "make kxploit" does not work, but I like the idea :)

groepaz · Post by **groepaz** » Fri Sep 30, 2005 7:38 am

But thanks for hints. The "make kxploit" does not work, but I like the idea :)

well it should. you really should fix your setup

Kristof · Post by **Kristof** » Fri Sep 30, 2005 4:39 pm

Yes I know, but so close to my goal, I really do not want to reinstall the whole thing again. I'm very ignorant in autoconfig makefile, so when it fail in the middle of installation, it is very embarassing.

I'll try to find what is going wrong with the samples.

holger · Post by **holger** » Fri Sep 30, 2005 6:33 pm

when you built and installed the toolchain properly, the samples and test programs should compile&run out-of-the-box, without touching anything.

Kristof · Post by **Kristof** » Fri Sep 30, 2005 6:59 pm

You are right.

The packages are always like this. If everything is ok then it is simple, but if there is one error then it is hell.

I'm going to check everything to understand how it works. The best way to solve problems is to understand them.

---

No results. I bet I'll have to make the installation again :)

But I'm understanding more things everyday. I'll soon understand the mystery of building a version.

==> In fact, I need to install the toolchain. I never succeded in completing the script installation, so I took the toolchain of the zip "pspdev".

Kristof · Post by **Kristof** » Fri Sep 30, 2005 10:45 pm

Following you advices, I just start a fresh installation from scratch.

This time the toolchain built well (after 1h30).

I think my other PC (the one were the build failed) have a problem. (cygwin tell me he can not create the /tmp dir, that's surely a problem).

Thanks all.