Mail Archives: djgpp/2015/05/23/05:49:04
> Date: Sat, 23 May 2015 12:24:08 +0300
> From: "Ozkan Sezer (sezeroz AT gmail DOT com)" <djgpp AT delorie DOT com>
>
> Using an unmodified 2.03-based toolchain/djgpp environment,
> current cvs fails like the following:
>
> ../../../lib/libc.a(crt1.o)(.text+0x25d):crt1.c: undefined reference
> to `_environ'
> ../../../lib/libc.a(crt1.o)(.text+0x2c4):crt1.c: undefined reference
> to `_environ'
> ../../../lib/libc.a(crt1.o)(.text+0x2d0):crt1.c: undefined reference
> to `_environ'
> ../../../lib/libc.a(crt1.o)(.text+0x2f7):crt1.c: undefined reference
> to `_environ'
> ../../../lib/libc.a(crt1.o)(.text+0x516):crt1.c: undefined reference
> to `_environ'
> ../../../lib/libc.a(spawnvp.o)(.text+0x11):spawnvp.c: more undefined
> references to `_environ' follow
> make.exe[3]: *** [../../../bin/symify.exe] Error 1
>
> However, if I specify djgpp.djl on the make line, like:
> make DJGPP_DJL=c:/v205/lib/djgpp.djl
> ... then build happily succeeds.
>
> Why are we using the toolchain-provided linker script instead
> of source tree-provided one? If this was an oversight, I can
> easily change this.
I'm guessing that no one envisioned the linker script will be ever
modified.
Using the script from the source tree is TRT, IMO.
Thanks.
- Raw text -