From: "Eugene Wong" <disposable_eugene@hotmail.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] How to upgrade to portage-2.0.46-r12?
Date: Mon, 10 Feb 2003 14:07:21 -0800 [thread overview]
Message-ID: <F20W1WaeAQyR1y5Qogr000061ee@hotmail.com> (raw)
Hi.
I'm using portage-2.0.46-r9 & would like to ugrade to portage-2.0.46-r12.
I've included a few lines from the beginning of the output, then cut out the
middle part, then included a few lines from the end. Is this something to do
with configurations in /etc? Is there anything else that I need to tell you?
I must confess that I tried to edit make.globals, but I tried to put it back
to the way that it was, & it still didn't help.
Calculating dependencies ^H\^H^H ...done!^M
>>>emerge (1 of 1) sys-apps/portage-2.0.46-r12 to /^M
>>>md5 ;-) portage-2.0.46-r12.tar.bz2^M
>>>Unpacking source...^M
tar xjf /usr/portage/distfiles/portage-2.0.46-r12.tar.bz2^M
>>>Source unpacked.^M
In file included from tbz2tool.c:1:^M
/usr/include/stdio.h:34:21: stddef.h: No such file or directory^M
In file included from /usr/include/stdio.h:36,^M
from tbz2tool.c:1:^M
/usr/include/bits/types.h:29:20: stddef.h: No such file or directory^M
In file included from /usr/include/bits/types.h:143,^M
from /usr/include/stdio.h:36,^M
from tbz2tool.c:1:^M
/usr/include/bits/pthreadtypes.h:48: parse error before "size_t"^M
/usr/include/bits/pthreadtypes.h:51: parse error before "__stacksize"^M
/usr/include/stdio.h:489: parse error before "fread"^M
/usr/include/stdio.h:489: parse error before "size_t"^M
/usr/include/stdio.h:492: parse error before "fwrite"^M
/usr/include/stdio.h:492: parse error before "size_t"^M
/usr/include/stdio.h:504: parse error before "fread_unlocked"^M
/usr/include/stdio.h:504: parse error before "size_t"^M
/usr/include/stdio.h:506: parse error before "fwrite_unlocked"^M
/usr/include/stdio.h:506: parse error before "size_t"^M
In file included from libsandbox.c:55:^M
/usr/include/stdio.h:644: parse error before "__gnuc_va_list"^M
In file included from /usr/include/stdio.h:674,^M
from libsandbox.c:55:^M
/usr/include/bits/stdio.h:34: parse error before "__gnuc_va_list"^M
/usr/include/bits/stdio.h: In function `vprintf':^M
/usr/include/bits/stdio.h:36: `__fmt' undeclared (first use in this
function)^M
/usr/include/bits/stdio.h:36: (Each undeclared identifier is reported only
once^M
/usr/include/bits/stdio.h:36: for each function it appears in.)^M
/usr/include/bits/stdio.h:36: `__arg' undeclared (first use in this
function)^M
<snip>
{standard input}:343: Error: symbol `__result' is already defined^M
{standard input}:343: Warning: rest of line ignored; first ignored character
is `,'^M
{standard input}:345: Error: symbol `__result' is already defined^M
{standard input}:345: Warning: rest of line ignored; first ignored character
is `,'^M
{standard input}:346: Error: symbol `__result' is already defined^M
{standard input}:346: Warning: rest of line ignored; first ignored character
is `,'^M
make: *** [libsandbox.o] Error 1^M
^M
!!! ERROR: sys-apps/portage-2.0.46-r12 failed.^M
!!! Function src_compile, Line 4
Sincerely, and with thanks,
Eugene T.S. Wong
_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-02-10 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 22:07 Eugene Wong [this message]
2003-02-10 23:13 ` [gentoo-dev] How to upgrade to portage-2.0.46-r12? Aron Griffis
-- strict thread matches above, loose matches on Subject: below --
2003-02-11 21:40 Eugene Wong
2003-02-12 7:07 ` Martin Holzer
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=F20W1WaeAQyR1y5Qogr000061ee@hotmail.com \
--to=disposable_eugene@hotmail.com \
--cc=gentoo-dev@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