Ralf S. Engelschall wrote:
On Thu, Feb 09, 2006, Doug Summers wrote:


Using OpenPKG 2.5.1 with the following rpm's installed:

binutils-2.16.1-2.5.0
bison-2.1-2.5.0
flex-2.5.31-2.5.0
libiconv-1.10-2.5.0
m4-1.4.3-2.5.0
make-3.80-2.5.0

I've tried both the release and current sources for GCC and both die at
the same point (after stage 2):

configure: creating cache ./config.cache
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether /syscfg/opkg/bin/make --no-print-directory sets
$(MAKE)... yes
checking for x86_64-unknown-linux-gnu-gcc...
/syscfg/opkg/RPM/TMP/gcc-4.0.2/obj/gcc/xgcc
-B/syscfg/opkg/RPM/TMP/gcc-4.0.2/obj/gcc/
-B/syscfg/opkg/x86_64-unknown-linux-gnu/bin/
-B/syscfg/opkg/x86_64-unknown-linux-gnu/lib/ -isystem
/syscfg/opkg/x86_64-unknown-linux-gnu/include -isystem
/syscfg/opkg/x86_64-unknown-linux-gnu/sys-include  -m32
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
See `config.log' for more details.
make[1]: *** [configure-target-libstdc++-v3] Error 1
make: *** [bootstrap-lean] Error 2

I'm using GCC 3.4.4 from RedHat.


As the message tells, please have a look into the config.log file which
is written under /syscfg/opkg/RPM/TMP/gcc-4.0.2/... There you hopefully
can find more details why it failed. Sorry, I've no RHEL4/amd64 box
available for testing it myself.

                                       Ralf S. Engelschall
                                       [EMAIL PROTECTED]
                                       www.engelschall.com
BTW - this affects GCC 3.4.5 as well.

Doug
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
User Communication List                      openpkg-users@openpkg.org

Reply via email to