From: Andreas Jaeger <aj@suse.de>
To: "Carlos Ordonez" <carloso@us.ibm.com>
Cc: gcc@gcc.gnu.org, pcarlini@unitus.it
Subject: Re: missing gcc_eh
Date: Tue, 30 Jul 2002 12:07:00 -0000 [thread overview]
Message-ID: <hosn21458d.fsf@gee.suse.de> (raw)
In-Reply-To: <OFC658A2D6.FE439622-ON85256C06.0050E64F@pok.ibm.com> ("Carlos Ordonez"'s message of "Tue, 30 Jul 2002 11:01:38 -0400")
"Carlos Ordonez" <carloso@us.ibm.com> writes:
> Andreas, Paolo, thank you for your quick response. I am trying to build
> rpms for gcc 3.1, glibc 2.2.5 and binutils The system I am building is
> Linux for S/390 - SuSE SLES 7 kernel version 2.4.7. I built binutils rpm
Oh, S390.
> 1st and installed it:
> pbc99213:/usr/src/packages/SPECS # rpm -qa | grep binutils
> binutils-2.12.1-1
> pbc99213:/usr/src/packages/SPECS # ld -version
> GNU ld version 2.12.1
> Copyright 2002 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License. This program has absolutely no warranty.
>
> Then I built GCC 3.1 and install it (I am thinking I should have done glibc
Better use GCC 3.1.1, it contains some important bugfixes for s390.
> 2.2.5 first and then GCC 3.1 - should I?) :
The order is ok.
> pbc99213:/usr/src/packages/SPECS # rpm -qa | grep gcc
> gcc-objc-3.1-0.1
> gcc-3.1-0.1
> gcc-c++-3.1-0.1
> pbc99213:/usr/src/packages/SPECS # gcc -dumpversion
> 3.1
>
> Now I am trying to build glibc 2.2.5 with the following options:
> CC="$GCC" CFLAGS="$BuildFlags -g -O3" ../configure --prefix=%{_prefix} \
> --enable-add-ons --without-cvs --disable-profile \
> --disable-nls --enable-omitfp %{_target_cpu}-suse-linux
>
> The last few lines before the error shows are:
> rm -f /usr/src/packages/BUILD/glibc-2.2.5/build-s390-linux/libc.so.lds
> make -s -C csu others
> make -s -C iconv others
> make[2]: Entering directory `/usr/src/packages/BUILD/glibc-2.2.5/iconv'
> make[2]: Leaving directory `/usr/src/packages/BUILD/glibc-2.2.5/iconv'
> make -s -C iconvdata others
> make[2]: Entering directory `/usr/src/packages/BUILD/glibc-2.2.5/iconvdata'
> /usr/bin/ld: cannot find -lgcc_eh
libgcc_eh.a should be in /usr/lib/gcc-lib/s390-suse-linux/3.1. Please
check that it's there. If not, your build/installation of GCC is
wrong.
> collect2: ld returned 1 exit status
> make[2]: ***
> [/usr/src/packages/BUILD/glibc-2.2.5/build-s390-linux/iconvdata/ISO
> 8859-1.so] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory `/usr/src/packages/BUILD/glibc-2.2.5/iconvdata'
> make[1]: *** [iconvdata/others] Error 2
> make[1]: Leaving directory `/usr/src/packages/BUILD/glibc-2.2.5'
> make: *** [all] Error 2
> Bad exit status from /var/tmp/rpm-tmp.19724 (%build)
>
> I built a working system with kernel 2.4.17, based on SuSE kernel 2.4.7
> that I am using to build the rpms, which I have gcc 3.1, glibc 2.2.5,
> binutils 2.12.1. I am almost positive I build glibc 2.2.5 before gcc 3.1
> and everything appears to be working fine. Maybe I should build glibc with
> my previous gcc and then build the rpm for gcc 3.1. Thanks for any help you
> can offer. Carlos :-)
Btw. you can find SuSE RPMs (with additional patches) for S390 of the current
toolchain consisting of glibc, binutils, gcc in my ftp directory:
ftp.suse.com/pup/people/aj/Current_Toolchain/
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-07-30 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 11:36 Carlos Ordonez
2002-07-30 12:07 ` Andreas Jaeger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 16:55 Carlos Ordonez
2002-07-30 11:18 Carlos Ordonez
2002-07-30 9:46 Carlos Ordonez
2002-07-30 10:33 ` Paolo Carlini
2002-07-30 10:38 ` Andreas Jaeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=hosn21458d.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=carloso@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=pcarlini@unitus.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).