From: Sebastian <selist@arcor.de>
To: gentoo-user-de@lists.gentoo.org
Subject: Re: [gentoo-user-de] gcc will nicht gebaut werden
Date: Wed, 5 Mar 2008 14:35:09 +0100 [thread overview]
Message-ID: <200803051435.10549.selist@arcor.de> (raw)
In-Reply-To: <200803050723.18853.Tobias.Kraehling@semibyte.de>
Hallo,
>
> > /usr/lib/gcc/i686-pc-linux-gnu/4.2.2/../../../../i686-pc-linux-gnu/bin/ld
> >: crt1.o: No such file: No such file or directory
> > collect2: ld gab 1 als Ende-Status zurück
>
> ld sucht crt1.o, die nicht gefunden wird. Wenn ich mich richtig erinner,
> wird die zwingend für den Linker benötigt. Ist die crt1.o denn irgendwo bei
> dir vorhanden, bei mir liegt sie in /usr/lib. Wenn die nicht mehr vorhanden
> ist, sie kommt aus sys-libs/glibc.
>
Die Datei crt1.so scheint es nicht zu geben. aber ein emerge sys-libs/glibc
geht ja nicht weil der Compiler nicht geht. Jedenfalls erhalte ich dabei die
Meldung:
checking size of long double... configure: error: cannot compute sizeof (long
double)
See `config.log' for more details.
*
* ERROR: sys-libs/glibc-2.7-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3349: Called eblit-run 'src_compile'
* environment, line 1090: Called eblit-glibc-src_compile
* src_compile.eblit, line 179: Called toolchain-glibc_src_compile
* src_compile.eblit, line 120: Called
glibc_do_configure 'src_compile'
* src_compile.eblit, line 97: Called die
* The specific snippet of code:
* "${S}"/configure ${myconf} || die "failed to configure glibc"
* The die message:
* failed to configure glibc
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located
at '/var/tmp/portage/sys-libs/glibc-2.7-r1/temp/build.log'.
* The ebuild environment file is located
at '/var/tmp/portage/sys-libs/glibc-2.7-r1/temp/environment'.
Wo liegt config.log?
Zu dem hinweis von Arnold folgenden Auszug. Das brachte jedenfals auch keinen
Erfolg.
*
r1-gentoo sebastian # gcc-config -l
[1] i686-pc-linux-gnu-4.2.2 *
r1-gentoo sebastian # fix_libtool_files.sh 4.2.2
* Scanning libtool files for hardcoded gcc library paths...
* [1/9] Scanning /lib ...
* [2/9] Scanning /usr/lib ...
* [3/9] Scanning /opt/blackdown-jdk-1.4.2.03/jre/lib/i386 ...
* [4/9] Scanning /opt/firefox ...
* [5/9] Scanning /usr/i686-pc-linux-gnu/lib ...
* [6/9] Scanning /usr/kde/3.5/lib ...
* [7/9] Scanning //usr//lib/opengl/xorg-x11/lib ...
* [8/9] Scanning /usr/local/lib ...
* [9/9] Scanning /usr/qt/3/lib ...
r1-gentoo sebastian #
Gruß
Sebastian
--
gentoo-user-de@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-05 13:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 12:58 [gentoo-user-de] gcc will nicht gebaut werden Sebastian
2008-02-22 14:35 ` Ergänzung: " Sebastian
2008-02-22 15:08 ` [gentoo-user-de] " Arnold Krille
2008-02-22 17:19 ` Justin
2008-03-01 9:11 ` Sebastian
2008-03-04 23:02 ` Sebastian
2008-03-05 6:23 ` Tobias Krähling
2008-03-05 13:35 ` Sebastian [this message]
2008-03-05 15:02 ` Arnold Krille
2008-03-05 16:29 ` Tobias Krähling
2008-03-05 7:47 ` Arnold Krille
2008-03-07 21:44 ` Sebastian
2008-03-07 22:26 ` Sebastian
2008-03-20 21:10 ` [gentoo-user-de] " Sebastian
2008-03-20 21:26 ` Arnold Krille
2008-03-20 22:03 ` Sebastian
2008-03-20 22:06 ` André Glücksmann
2008-03-20 22:47 ` André Glücksmann
2008-03-21 16:37 ` Sebastian
2008-03-21 19:44 ` André Glücksmann
2008-03-21 19:48 ` Joerg Bornkessel
2008-03-28 8:12 ` Sebastian
2008-03-28 8:53 ` Arnold Krille
2008-04-13 14:06 ` Sebastian
2008-03-21 20:21 ` Arnold Krille
2008-03-20 22:42 ` Arnold Krille
2008-03-20 21:28 ` André Glücksmann
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=200803051435.10549.selist@arcor.de \
--to=selist@arcor.de \
--cc=gentoo-user-de@lists.gentoo.org \
/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