Compiling Issues

[Capn_Fish]

I've recently been getting "multiple definitions of xyz: first defined here" errors when I try to build stuff. What causes them? I'm assuming that since I'm trying to build stable/release code, it's not a code error.

I'm using the flags:

Code: [Select]

-O3 -mtune=xscale -mcpu=xscale -ffast-math -fomit-frame-pointer -fno-common
I copied the ZGCC image contents to a MD partition and took some stuff (SDL headers, OGG/Vorbis headers, etc) that I have from my own builds.

Any help would be much appreciated.

[adf]

I've recently been getting "multiple definitions of xyz: first defined here" errors when I try to build stuff. What causes them? I'm assuming that since I'm trying to build stable/release code, it's not a code error.

I'm using the flags:

Code: [Select]

-O3 -mtune=xscale -mcpu=xscale -ffast-math -fomit-frame-pointer -fno-common
I copied the ZGCC image contents to a MD partition and took some stuff (SDL headers, OGG/Vorbis headers, etc) that I have from my own builds.

Any help would be much appreciated.

After all  this technical stuff, you still haven't told us what this "Issues," you said you were going to compile even does

[Capn_Fish]

Sure I did. The "Error: multiple definitions of xyz: first defined here" errors. They just cause the build to stop/fail.

[koan]

It's a link error. You have the same function defined more than once at object level (.o).

For example, file1.c  defines function doA() and file2.c also defines doA() - the linker doesn't know which function to link to.

Just because you are using "stable/release" code doesn't mean it is guaranteed to compile out of the box on any other system.

[Capn_Fish]

OK, so going into the code and editing it is the way to go. I assume I should send patches to the devs as well?

Thanks.

[koan]

OK, so going into the code and editing it is the way to go. I assume I should send patches to the devs as well?

Thanks.

You should do a grep to find which functions are duplicated in which files.

It could be that your compiler is too old so didn't make a distinctive enough name for the linker. It could be that those extra files you mentioned are being linked too and causing confusion. If the code is C++ then you have to get into name mangling... Anyway, I'm just trying to say that it could be you have a broken set up and there is no problem in the original code. On the other hand a lot of projects release broken source code.

[Capn_Fish]

I guess the pdaX compiler is broken, the code builds fine on my Debian box.

EDIT: Turning off my custom flags seems to make it build OK. I'm trying now with only

Code: [Select]

-O3 -mtune=xscale -mcpu=xscale
EDIT2: That worked, so I guess using some options can cause the compiler to break.