public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Dean <linux@acme-solutions.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rebuild gcc-3.4.6-r2 error
Date: Sat, 10 Mar 2007 15:00:53 +0000	[thread overview]
Message-ID: <45F2C825.5090307@acme-solutions.co.uk> (raw)
In-Reply-To: <d5d1857a0703100609g6444fa5by1a331fe38963c015@mail.gmail.com>

Stuart Howard wrote:
> On 10/03/07, Bjarke Bondo Andersen <nissemand@gmail.com> wrote:
>> Hi. When I try to update the world emerge tells me to rebuild gcc due 
>> to the
>> "-d%" flag. When I try to do so, it fails. Try to take a look at the 
>> output
>> here:
>>
>> # emerge -uDNav world
>>
>> These are the packages that would be merged, in order:
>>
>> Calculating world dependencies... done!
>> [ebuild   R   ] sys-devel/gcc-3.4.6-r2  USE="doc hardened nls (-altivec)
>> -bootstrap -boundschecking -build -d% -fortran -gcj -gtk -ip28 -ip32r10k
>> -multilib -multislot (-n32) (-n64) -nocxx -nopie -nossp -objc -test
>> -vanilla" 0 kB
>>
>> ...
>>
>> >>> Unpacking source...
>> >>> Unpacking gcc-3.4.6.tar.bz2 to
>> /var/tmp/portage/sys-devel/gcc-3.4.6-r2/work
>> >>> Unpacking gdc-0.23-src.tar.bz2 to /var/tmp/portage/sys-devel/gcc-
>> 3.4.6-r2/work/gcc-3.4.6/gcc
>>
>> !!! ERROR: sys-devel/gcc-3.4.6-r2 failed.
>> Call stack:
>>   ebuild.sh, line 1614:   Called dyn_unpack
>>   ebuild.sh, line 751:   Called qa_call 'src_unpack'
>>   environment, line 5309:   Called src_unpack
>>   gcc-3.4.6-r2.ebuild, line 81:   Called gcc_src_unpack
>>   toolchain.eclass, line 1018:   Called gcc_quick_unpack
>>   toolchain.eclass, line 1870:   Called unpack 'gdc-0.23-src.tar.bz2'
>>   ebuild.sh, line 404:   Called die
>>
>> !!! gdc-0.23-src.tar.bz2 does not exist
>> !!! 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-devel
>>  /gcc-3.4.6-r2 /temp/build.log'.
>> #
>>
>> And I can't seem to find anything called gdc in portage...
>> I hope someone of you can help me out (without me having to change 
>> profile)
>> or at least say that it doesn't matter.
>>
>> And btw. here's the output og emerge --info:
>> Portage 2.1.2.2 (hardened/x86/2.6, gcc-3.4.6, glibc-2.3.6-r5,
>> 2.6.19-gentoo-r5 i
>> 686)
>> =================================================================
>> System uname: 2.6.19-gentoo-r5 i686 Celeron (Coppermine)
>> Gentoo Base System release 1.12.9
>> Timestamp of tree: Sat, 10 Mar 2007 10:30:01 +0000
>> dev-lang/python:     2.4.3-r4
>> dev-python/pycrypto: 2.0.1-r5
>>  sys-apps/sandbox:    1.2.17
>> sys-devel/autoconf:  2.13, 2.60
>> sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 
>> 1.9.6-r2, 1.10
>> sys-devel/binutils:  2.16.1-r3
>> sys-devel/gcc-config: 1.3.14
>> sys-devel/libtool:   1.5.22
>> virtual/os-headers:  2.6.17-r2
>> ACCEPT_KEYWORDS="x86"
>> AUTOCLEAN="yes"
>> CBUILD="i386-pc-linux-gnu"
>> CFLAGS="-O2 -pipe -march=pentium"
>> CHOST="i386-pc-linux-gnu"
>> CONFIG_PROTECT="/etc"
>> CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf
>> /etc/php/apache1-php5/ext-active/ /et
>> c/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/
>> /etc/php/cli-php5/e
>> xt-active/ /etc/revdep-rebuild /etc/terminfo"
>> CXXFLAGS="-O2 -pipe -march=pentium"
>> DISTDIR="/usr/portage/distfiles"
>> FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
>> GENTOO_MIRRORS=" http://mirror.uni-c.dk/pub/gentoo/"
>> MAKEOPTS="-j2"
>> PKGDIR="/usr/portage/packages"
>> PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
>> --compress
>> --force --whole-file --delete --delete-after --stats --timeout=180
>> --exclude=/di
>> stfiles --exclude=/local --exclude=/packages 
>> --filter=H_**/files/digest-*"
>> PORTAGE_TMPDIR="/var/tmp"
>> PORTDIR="/usr/portage"
>> SYNC="rsync://rsync.gentoo.org/gentoo-portage"
>>  USE="apache2 berkdb crypt doc hardened hardenedphp imagemagick ipv6 
>> latin1
>> midi
>> mysql mysqli nls pam perl php pic readline ssl tcpd x86 xorg zlib"
>> ALSA_PCM_PLUG
>> INS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks 
>> iec958
>> iop
>> lug ladspa lfloat linear meter mulaw multi null plug rate route share 
>> shm
>> softvo
>> l" ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux"
>> LCD_DEVICES="bayr
>> ad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text"
>> USERLAND="GNU
>> "
>> Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, 
>> LDFLAGS,
>> LINGU
>> AS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
>
>
>
>
> I have the same error.
>
> As you said gdc does not seem to exist anywhere within the sources or
> the ebuild, I would say that we have been caught with a typo but it is
> strange that there have been only two reports on the list so far.
Hi,

I have have encountered this problem this morning on both of my 
computers which are using the hardened profile (I am not sure whether 
this this could be part of the problem?). I have managed to get around 
this problem by downloading the gdc-0.23-src.tar.bz2 file from my local 
mirror (e.g. http://gentoo.virginmedia.com/distfiles) to the 
/usr/portage/distfiles folder. When I then tried the update world the 
second time, everything worked properly! I know that this does not 
resolve the issue but it is the way that I managed to work around the 
problem.

Hope this helps.

Andrew
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-03-10 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-10 13:09 [gentoo-user] rebuild gcc-3.4.6-r2 error Bjarke Bondo Andersen
2007-03-10 14:09 ` Stuart Howard
2007-03-10 15:00   ` Andrew Dean [this message]
2007-03-10 15:18     ` Stuart Howard
2007-03-12  2:52     ` Walter Dnes
2007-03-12 19:03     ` Alan McKinnon
2007-03-13 20:45       ` Andrew Dean
  -- strict thread matches above, loose matches on Subject: below --
2007-03-10 13:01 Bjarke Bondo Andersen

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=45F2C825.5090307@acme-solutions.co.uk \
    --to=linux@acme-solutions.co.uk \
    --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