This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Possible configure problem in mainline?
- From: Bradley Lucier <lucier at math dot purdue dot edu>
- To: gcc at gcc dot gnu dot org
- Cc: Bradley Lucier <lucier at math dot purdue dot edu>
- Date: Sat, 15 Apr 2006 18:29:19 -0500
- Subject: Possible configure problem in mainline?
I'm trying to build a 64-bit mainline compiler on powerpc-darwin; I
want gcc to generate 32-bit binaries by default, I just want cc1,
etc., to be 64-bit binaries so I can compile large files.
This works in 4.1, but not on mainline. This is reported at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26892
The problem is that the makefile is trying to link libiconv.dylib,
which is only 32 bit, into a 64-bit makedepend.
This doesn't happen on 4.1, where configure finds iconv.h, but
realizes that it can't use libiconv:
[lindv2:gcc/gcc-4.1.0/objdir] lucier% grep iconv build.log
checking for iconv... no, consider installing GNU libiconv
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking for iconv... no, consider installing GNU libiconv
checking for iconv.h... yes
checking for iconv... no, consider installing GNU libiconv
For some reason, the tests for iconv in mainline don't rule out using
libiconv; some details are given in the preceding bugzilla report.
Does anyone have any suggestions?
Brad