We are experiencing a strange problem when we build projects for
uClinux: On some PCs, the build proceeds as one would expect, project
after project. On other PCs, the build fails consistently, regardless of
the project. The build and, more specifically, the link seem to be PC
dependent. The toolchain, installation and relevant directory structures
are identical in all test PCs.
The output from a failed linker step looks like:
:
Invoking: C Linker(uClibc)
m68k-uclinux-gcc -msep-data -Wl,-elf2flt
-L"C:\SBCToolsV3\boards\wildfire\uclinux\rtl\lib" -m5307 -o"toto"
./main.o -lwildfirertl -lc -lgcc
m68k-uclinux-ld.real.exe: cannot open linker script file
/SBCToolsV3/compiler/m68k-uclinux-3.4.0/m68k-uclinux/lib/elf2flt.ld: No
such file or directory
collect2: ld returned 1 exit status
But, elf2flt.ld ***DOES*** exist and is exactly where it should be.
The output from a successful linker step looks like:
:
Invoking: C Linker(uClibc)
m68k-uclinux-gcc -msep-data -Wl,-elf2flt
-L"C:\SBCToolsV3\boards\wildfire\uclinux\rtl\lib" -m5307 -o"toto"
./main.o -lwildfirertl -lc -lgcc
Finished building target: toto
Because the toolchain, its installation and relevant directory
structures are identical in all test PCs we suspected an environment
variable. But, the Windows (XP) Path environment variable is identical
in all test PCs.
And, oh, yes, there was a strange artifact when linking failed: Instead
of generating an exec called exec_name, the failed linker step generated
a file exec_name.elf2flt (???).
Baffled,
Bob Furber
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
