Doug Summers <[EMAIL PROTECTED]> writes:
> 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.
I think I have found the problem and solution. I also had the problem
on a new server running RHEL4 x86_64. This allowed me to build
various rpms but failed on gcc.
$ cd /openpkg/RPM/PKG
$ ls -la *.rpm
total 11564
-rw-r--r-- 1 root root 4028747 Mar 29 11:24
binutils-2.16.1-2.5.0.amd64-rhel4-ope.rpm
-rw-r--r-- 1 root root 175833 Mar 29 11:20
make-3.80-2.5.0.amd64-rhel4-ope.rpm
-rw-r--r-- 1 root root 6963248 Mar 29 12:32
openpkg-2.5.1-2.5.1.amd64-rhel4-ope.rpm
-rw-r--r-- 1 root root 133338 Mar 29 11:33
openpkg-tools-0.8.47-2.5.0.amd64-rhel4-ope.rpm
The gcc failed as you indicated. I had been building 32-bit rpms
(standard RH rpms) on a similar server so I looked at the installed
rpm list. On that server (if you make rpm show the %arch you can see
2 glibc and 2 glibc-devel rpms.
# rpm -q --queryformat "%{name}-%{version}-%{release}-%{arch}\n" glibc
glibc-devel
glibc-2.3.4-2.19-x86_64
glibc-2.3.4-2.19-i686
glibc-devel-2.3.4-2.19-i386
glibc-devel-2.3.4-2.19-x86_64
On the box I was using to build OpenPKG gcc I did not have
glibc-devel.i386 so it could not build 32-bit binaries.
I installed glibc-devel.i386 and then tested the test program that
failed before. This now builds without problems. I am retrying to
build OpenPKG gcc again and hope that this time it will work. Will
confirm tomorrow if this goes ok.
On a side-note I don't know what the rpms come out with a
amd64-rhel4-ope suffix as the server has twin 3GHz Xeon processors. This is a
bit confusing[1].
[EMAIL PROTECTED] PKG]$ cat /proc/cpuinfo | grep "model name"
model name : Intel(R) Xeon(TM) CPU 3.00GHz
model name : Intel(R) Xeon(TM) CPU 3.00GHz
model name : Intel(R) Xeon(TM) CPU 3.00GHz
model name : Intel(R) Xeon(TM) CPU 3.00GHz
Sybase also name their 64-bit binaries in this way...
Hope this info helps.
Regards,
Simon
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
