This is the mail archive of the
mailing list for the GCC project.
Re: probs cross-building current libstdc++-v3, because of need to link?
- From: Phil Edwards <phil at jaj dot com>
- To: cgd at broadcom dot com
- Cc: gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org
- Date: Tue, 12 Aug 2003 02:31:22 -0400
- Subject: Re: probs cross-building current libstdc++-v3, because of need to link?
- References: <email@example.com>
Adding libstdc++ to the Cc list.
On Mon, Aug 11, 2003 at 11:08:11PM -0700, firstname.lastname@example.org wrote:
> configure:2335: checking for C compiler default output
> configure:2338: /home/cgd/proj/gcc-testing6/work/mipsisa64-elf.build/gcc/xgcc -B/home/cgd/proj/gcc-testing6/work/mipsisa64-elf.build/gcc/ -nostdinc -B/home/cgd/proj/gcc-testing6/work/mipsisa64-elf.build/mipsisa64-elf/newlib/ -isystem /home/cgd/proj/gcc-testing6/work/mipsisa64-elf.build/mipsisa64-elf/newlib/targ-include -isystem /home/cgd/proj/gcc-testing6/combined/newlib/libc/include -B/home/cgd/proj/gcc-testing6/work/mipsisa64-elf.install/mipsisa64-elf/bin/ -B/home/cgd/proj/gcc-testing6/work/mipsisa64-elf.install/mipsisa64-elf/lib/ -isystem /home/cgd/proj/gcc-testing6/work/mipsisa64-elf.install/mipsisa64-elf/include -isystem /home/cgd/proj/gcc-testing6/work/mipsisa64-elf.install/mipsisa64-elf/sys-include -L/home/cgd/proj/gcc-testing6/work/mipsisa64-elf.build/ld -O2 -g -O2 -O2 -g -O2 conftest.c >&5
> collect2: cannot find `ld'
> configure:2341: $? = 1
> (I'm not sure which new-autoconf macro causes that test to be emitted,
One of the ancilliary macros inside AC_PROG_CC.
> It seems to me that the fact that the 'ld' symlink isn't created
> (because 'LD' is set and since it's absolute passes "test -x") may be
> a bug.
> On the other hand, it's not clear that anything in the libstdc++-v3
> build process should depend on being able to final-link programs.
I agree. The ugliest chunks of the v3 configury are all due to this precise
fact; we hardcode lots of information about known-good cross targets, because
we can't perform the link tests needed to discover the information instead.
...yah, methinks I know what I've forgotten. Patch in progress.
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
- Brian W. Kernighan