From: "Timothy A. Holmes" <tholmes@mcaschool.net>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] problem with a world update
Date: Wed, 6 Sep 2006 14:33:47 -0400 [thread overview]
Message-ID: <17CD9CE4C0FA574A8B29EF02D49B385D2A921E@srvexch-01.mcaschool.local> (raw)
In-Reply-To: <b79f23070609060959v2f2a15b3q5a097b77391fbc3a@mail.gmail.com>
> -----Original Message-----
> From: James Ausmus [mailto:james.ausmus@gmail.com]
> Sent: Wednesday, September 06, 2006 12:59 PM
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] problem with a world update
>
> On 9/6/06, Timothy A. Holmes <tholmes@mcaschool.net> wrote:
> > Hi folks;
> >
> > I have a server that im getting ready to build as a file server --
the
> > OS is installed (several months ago-- its been idleing) and im doing
an
> > emerge -NDuav world to get it all up to date.
> >
> > Im getting the following error, and I have no clue what to do about
it,
> > can someone please point me in the right direction?
> >
> >
> >
> > ** adjusting tabset paths
> > sed -f run_tic.sed
> > /var/tmp/portage/ncurses-5.5-r2/work/ncurses-5.5/misc/terminfo.src
> > >terminfo.tmp
> > make[1]: Leaving directory
> > `/var/tmp/portage/ncurses-5.5-r2/work/narrowc/misc'
> > cd c++ && make DESTDIR="" all
> > make[1]: Entering directory
> > `/var/tmp/portage/ncurses-5.5-r2/work/narrowc/c++'
> > /usr/bin/g++ -I../c++ -I../include
> > -I/var/tmp/portage/ncurses-5.5-r2/work/ncurses-5.5/c++
-DHAVE_CONFIG_H
> > -I/var/tmp/portage/ncurses-5.5-r2/work/ncurses-5.5/c++/../include
-I.
> > -I../include -D_GNU_SOURCE -DNDEBUG {-O2 -march=pentium4 -pipe
> > -fomit-frame-pointer} -fPIC -c
>
> It looks like your CFLAGS setting in /etc/make.conf might be screwed
> up - contains some curly braces {} ?
>
> HTH-
>
> James
> --
> gentoo-user@gentoo.org mailing list
[Timothy A. Holmes]
James:
The setting is set per the handbook -- with a couple mods for speed
CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="{$CFLAGS}"
MAKEOPTS="-j4"
Timothy A. Holmes
IT Manager / Network Admin / Web Master / Computer Teacher
Medina Christian Academy
A Higher Standard...
Jeremiah 33:3
Jeremiah 29:11
Esther 4:14
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-06 18:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 14:57 [gentoo-user] Exluding some apps from emerge --update world Alex Fortwinder
2006-07-04 19:58 ` Paul Sebastian Ziegler
2006-07-30 15:45 ` Jarry
2006-07-31 0:28 ` Neil Bothwick
2006-07-30 15:25 ` Robert G. Siebeck
2006-07-30 16:24 ` Randy Barlow
[not found] ` <20060730211741.50a8e533.alex_fortwinder@gmx.net>
2006-07-30 17:28 ` Tim Igoe
2006-09-06 8:31 ` Daevid Vincent
2006-09-06 8:48 ` Neil Bothwick
2006-09-06 9:22 ` Daevid Vincent
2006-09-06 10:00 ` Hieu, Luu Danh
2006-09-06 13:01 ` [gentoo-user] problem with a world update Timothy A. Holmes
2006-09-06 15:53 ` Jean-Marc Beaune
2006-09-06 16:49 ` Timothy A. Holmes
2006-09-06 16:56 ` Jean-Marc Beaune
2006-09-06 17:56 ` Timothy A. Holmes
2006-09-06 19:46 ` Richard Fish
2006-09-06 16:59 ` James Ausmus
2006-09-06 18:33 ` Timothy A. Holmes [this message]
2006-09-06 18:49 ` Gian Domeni Calgeer
[not found] <200609062045.35870.bo.andresen@zlin.dk>
2006-09-06 18:50 ` Timothy A. Holmes
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=17CD9CE4C0FA574A8B29EF02D49B385D2A921E@srvexch-01.mcaschool.local \
--to=tholmes@mcaschool.net \
--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