From: Mike Diehl <mdiehl@diehlnet.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge apache
Date: Sat, 19 Jan 2008 17:18:45 -0700 [thread overview]
Message-ID: <200801191718.45497.mdiehl@diehlnet.com> (raw)
In-Reply-To: <20080119111223.148e4c33.rzilka@gvid.cz>
On Saturday 19 January 2008 03:12:23 am Roman Zilka wrote:
> Hi Mike!
>
> > g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtbeginS.o: No such file or
> > directory
> > g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtendS.o: No such file or
> > directory
>
> i486 - this is kinda weird for a brand new box.
Ya, very weird. Here is what I've got in /etc/make.conf:
CHOST="i686-pc-linux-gnu"
MAKEOPTS="-j2"
USE="-acl -cups -dri -fortran -gpm -iconv -ipv6 -isdnlog -midi -mudflap -nls
-openmp -pppd -reflection -session -tcpd -truetype-fonts -type1-fonts
-unicode -xorg"
Seems rational to me. The box is going to be a stripped-down server.
> What's does your
> 'emerge --info' look like?
> Maybe you've got a wrong CHOST set up. What
> does 'ls /usr/lib/gcc/*/*/crt*S.o' report (just to be sure)? Are you
> able to emerge any other packages?
>
> -rz
# gcc-config -l
[1] i686-pc-linux-gnu-4.1.2 *
# ls /usr/lib/gcc/*/*/crt*S.o
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/crtbeginS.o /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/crtendS.o
It almost seems like it might be easier to start over.... What do you think?
--
Mike Diehl
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-20 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 3:28 [gentoo-user] Can't emerge apache Mike Diehl
2008-01-19 10:12 ` Roman Zilka
2008-01-20 0:18 ` Mike Diehl [this message]
2008-01-20 8:09 ` Alan McKinnon
2008-01-19 10:20 ` Alan McKinnon
2008-01-19 14:21 ` Kevin
2008-01-26 23:14 ` Mike Diehl
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=200801191718.45497.mdiehl@diehlnet.com \
--to=mdiehl@diehlnet.com \
--cc=gentoo-user@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