Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Portage & Programming
  • Search

Changing CHOST and upgrading gcc problems

Problems with emerge or ebuilds? Have a basic programming question about C, PHP, Perl, BASH or something else?
Post Reply
Advanced search
12 posts • Page 1 of 1
Author
Message
Skullbot
n00b
n00b
Posts: 7
Joined: Thu Mar 22, 2007 6:24 am
Contact:
Contact Skullbot
Website

Changing CHOST and upgrading gcc problems

  • Quote

Post by Skullbot » Thu Mar 22, 2007 6:47 am

I recently changed my chost variable from i386 to i686. I then followed the tutorial to upgrade gcc from 3.6 to 4.1. I thought everything was going well until I tried to update.

When I issue: emerge --update --deep --newuse world

I get the following:

Code: Select all

Calculating world dependencies... done!

>>> Emerging (1 of 62) dev-libs/apr-util-0.9.12 to /
 * apr-util-0.9.12.tar.gz RMD160 ;-) ...                                                         [ ok ]
 * apr-util-0.9.12.tar.gz SHA1 ;-) ...                                                           [ ok ]
 * apr-util-0.9.12.tar.gz SHA256 ;-) ...                                                         [ ok ]
 * apr-util-0.9.12.tar.gz size ;-) ...                                                           [ ok ]
 * checking ebuild checksums ;-) ...                                                             [ ok ]
 * checking auxfile checksums ;-) ...                                                            [ ok ]
 * checking miscfile checksums ;-) ...                                                           [ ok ]
 * checking apr-util-0.9.12.tar.gz ;-) ...                                                       [ ok ]
>>> Unpacking source...
>>> Unpacking apr-util-0.9.12.tar.gz to /var/tmp/portage/dev-libs/apr-util-0.9.12/work
 * Applying apr-util-0.9.12-linking.patch ...                                                    [ ok ]
 * Running elibtoolize in: apr-util-0.9.12/xml/expat/conftools
 *   Applying portage-1.5.10.patch ...
 *   Applying max_cmd_len-1.5.20.patch ...
 *   Applying sed-1.5.6.patch ...
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-libs/apr-util-0.9.12/work/apr-util-0.9.12 ...
 * Found db version 4.2
 * Found db version 4.2
include version 4.2
 * econf: updating apr-util-0.9.12/xml/expat/conftools/config.guess with /usr/share/gnuconfig/config.gu
ess
 * econf: updating apr-util-0.9.12/xml/expat/conftools/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating apr-util-0.9.12/build/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating apr-util-0.9.12/build/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --
datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datadir=/usr/share/apr-util-0 --with-ap
r=/usr --with-expat=/usr --with-ldap --with-gdbm --with-dbm=db42 --with-berkeley-db=/usr/include/db4.2:
/usr/lib --build=i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for working mkdir -p... yes
APR-util Version: 0.9.12
checking for chosen layout... apr-util
Applying apr-util hints file rules for i686-pc-linux-gnu
checking for APR... yes
  setting CC to "i386-pc-linux-gnu-gcc"
  setting CPP to "i386-pc-linux-gnu-gcc -E"
  adding "-pthread" to CFLAGS
  setting CPPFLAGS to " -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE"
checking for i686-pc-linux-gnu-gcc... i386-pc-linux-gnu-gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executab                                                                    les
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/dev-libs/apr-util-0.9.12/work/apr-util-0.9.12/config.log

!!! ERROR: dev-libs/apr-util-0.9.12 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 3894:   Called src_compile
  apr-util-0.9.12.ebuild, line 50:   Called econf '--datadir=/usr/share/apr-util-0' '--with-apr=/usr' '                                                                    --with-expat=/usr' '--with-ldap' '--with-gdbm' '--with-dbm=db42' '--with-berkeley-db=/usr/include/db4.2                                                                    :/usr/lib'
  ebuild.sh, line 577:   Called die

!!! econf failed
!!! 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/dev-libs/apr-util-0.9.12/temp/build.log'.

The package apr-util-0.9.12 won't install and I can only assume this is an issue with upgrading gcc and or changing chost.
Any suggestions would be appreciated.
Top
darken
n00b
n00b
User avatar
Posts: 52
Joined: Wed Jan 04, 2006 9:31 am

  • Quote

Post by darken » Thu Mar 22, 2007 7:41 am

Execute

Code: Select all

gcc-config -l
.
If you still have the old gcc around, it should print a list containing the old version and the new version you compiled, and if you have a star beside the old version, that one is still in use. If that is the case, do

Code: Select all

gcc-config i686-pc-linux-gnu-<your version>
to select your new compiled gcc.
Top
Skullbot
n00b
n00b
Posts: 7
Joined: Thu Mar 22, 2007 6:24 am
Contact:
Contact Skullbot
Website

  • Quote

Post by Skullbot » Thu Mar 22, 2007 7:56 am

darken wrote:Execute

Code: Select all

gcc-config -l
.
If you still have the old gcc around, it should print a list containing the old version and the new version you compiled, and if you have a star beside the old version, that one is still in use. If that is the case, do

Code: Select all

gcc-config i686-pc-linux-gnu-<your version>
to select your new compiled gcc.
gcc-config -l reports as I believe it should:

Code: Select all

 [1] i686-pc-linux-gnu-3.4.6
 [2] i686-pc-linux-gnu-3.4.6-hardened
 [3] i686-pc-linux-gnu-3.4.6-hardenednopie
 [4] i686-pc-linux-gnu-3.4.6-hardenednopiessp
 [5] i686-pc-linux-gnu-3.4.6-hardenednossp
 [6] i686-pc-linux-gnu-4.1.1 *
Top
darken
n00b
n00b
User avatar
Posts: 52
Joined: Wed Jan 04, 2006 9:31 am

  • Quote

Post by darken » Thu Mar 22, 2007 8:07 am

There is something more to try:

Code: Select all

fix_libtool_files.sh  3.4.6 --oldarch i386-pc-linux-gnu
Top
Skullbot
n00b
n00b
Posts: 7
Joined: Thu Mar 22, 2007 6:24 am
Contact:
Contact Skullbot
Website

  • Quote

Post by Skullbot » Thu Mar 22, 2007 3:12 pm

darken wrote:There is something more to try:

Code: Select all

fix_libtool_files.sh  3.4.6 --oldarch i386-pc-linux-gnu
I've tried that. It runs fine but I still get the same error with the apr-util-0.9.12 package. If I issue the emerge --resume --skipfirst command the rest of the packages seem to be updating fine. I'm just having a problem with apr-util-0.9.12 and of course, the packages which depend on it.
Top
amne
Bodhisattva
Bodhisattva
User avatar
Posts: 6378
Joined: Sun Nov 17, 2002 6:00 pm
Location: Graz / EU

  • Quote

Post by amne » Thu Mar 22, 2007 3:28 pm

Try

Code: Select all

emerge -av1 apr
Iirc this is fixed once you use the latest stable version of it.
Dinosaur week! (Ok, this thread is so last week)
Top
hielvc
Advocate
Advocate
Posts: 2805
Joined: Fri Apr 19, 2002 5:55 pm
Location: Oceanside, Ca

  • Quote

Post by hielvc » Thu Mar 22, 2007 3:31 pm

This could help Gentoo GCC Upgrade Guide and look at the and look at the foruth sticky thread down emerge glibc-2.5 failed (or how to change your CHOST)
An A-Z Index of the Linux BASH command line
Top
Skullbot
n00b
n00b
Posts: 7
Joined: Thu Mar 22, 2007 6:24 am
Contact:
Contact Skullbot
Website

  • Quote

Post by Skullbot » Thu Mar 22, 2007 7:34 pm

amne wrote:Try

Code: Select all

emerge -av1 apr
Iirc this is fixed once you use the latest stable version of it.
The package emerges fine with the emerge -av1 apr command. The thing is, when I do an emerge --update --newuse --world this ads the ldap use flag to the apr-util package and I think this is what is causing the problem.
Top
Skullbot
n00b
n00b
Posts: 7
Joined: Thu Mar 22, 2007 6:24 am
Contact:
Contact Skullbot
Website

Still having the problem

  • Quote

Post by Skullbot » Mon Mar 26, 2007 10:09 pm

This is my build.log for apr-util. Can anyone tell me if I'm still having problems because I updated from i386 to i686 and changed gcc to 4.1?

Code: Select all

>> Unpacking source...
>>> Unpacking apr-util-0.9.12.tar.gz to /var/tmp/portage/dev-libs/apr-util-0.9.12/work
 ^[[32;01m*^[[0m Applying apr-util-0.9.12-linking.patch ...
^[[A^[[72C  ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m
 ^[[32;01m*^[[0m Running elibtoolize in: apr-util-0.9.12/xml/expat/conftools
 ^[[32;01m*^[[0m   Applying portage-1.5.10.patch ...
 ^[[32;01m*^[[0m   Applying max_cmd_len-1.5.20.patch ...
 ^[[32;01m*^[[0m   Applying sed-1.5.6.patch ...
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/dev-libs/apr-util-0.9.12/work/apr-util-0.9.12 ...
 ^[[32;01m*^[[0m Found db version 4.2
 ^[[32;01m*^[[0m Found db version 4.2
include version 4.2
 * econf: updating apr-util-0.9.12/xml/expat/conftools/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating apr-util-0.9.12/xml/expat/conftools/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating apr-util-0.9.12/build/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating apr-util-0.9.12/build/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datadir$
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for working mkdir -p... yes
APR-util Version: 0.9.12
checking for chosen layout... apr-util
Applying apr-util hints file rules for i686-pc-linux-gnu
checking for APR... yes
  setting CC to "i386-pc-linux-gnu-gcc"
  setting CPP to "i386-pc-linux-gnu-gcc -E"
  adding "-pthread" to CFLAGS
  setting CPPFLAGS to " -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE"
checking for i686-pc-linux-gnu-gcc... i386-pc-linux-gnu-gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/dev-libs/apr-util-0.9.12/work/apr-util-0.9.12/config.log

!!! ERROR: dev-libs/apr-util-0.9.12 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 3901:   Called src_compile
  apr-util-0.9.12.ebuild, line 50:   Called econf '--datadir=/usr/share/apr-util-0' '--with-apr=/usr' '--with-expat=/usr' '--with-ldap' '--with-gdbm' '--with-dbm=db42' '--wit$
  ebuild.sh, line 577:   Called die

!!! econf failed
!!! 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/dev-libs/apr-util-0.9.12/temp/build.log'.
Top
amne
Bodhisattva
Bodhisattva
User avatar
Posts: 6378
Joined: Sun Nov 17, 2002 6:00 pm
Location: Graz / EU

  • Quote

Post by amne » Mon Mar 26, 2007 10:14 pm

Seems like you still have the version of apr that is built for i386. I just noticed apr is slotted, so the command i gave you most likely (re-)build another, newer version. Try

Code: Select all

emerge -av1 =dev-libs/apr-0.9.12
, that should properly rebuild it.
Dinosaur week! (Ok, this thread is so last week)
Top
Skullbot
n00b
n00b
Posts: 7
Joined: Thu Mar 22, 2007 6:24 am
Contact:
Contact Skullbot
Website

  • Quote

Post by Skullbot » Mon Mar 26, 2007 10:23 pm

emerge -av1 =dev-libs/apr-0.9.12
Worked like a charm. I'm fairly new to gentoo so I'm not sure why it worked.

Now I'm getting this problem when I continue updating world:

Code: Select all

>>> Emerging (1 of 1) x11-misc/shared-mime-info-0.19 to /
 * shared-mime-info-0.19.tar.gz RMD160 ;-) ...                                                                                                                           [ ok ]
 * shared-mime-info-0.19.tar.gz SHA1 ;-) ...                                                                                                                             [ ok ]
 * shared-mime-info-0.19.tar.gz SHA256 ;-) ...                                                                                                                           [ ok ]
 * shared-mime-info-0.19.tar.gz size ;-) ...                                                                                                                             [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                                     [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                                    [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                                   [ ok ]
 * checking shared-mime-info-0.19.tar.gz ;-) ...                                                                                                                         [ ok ]
>>> Unpacking source...
>>> Unpacking shared-mime-info-0.19.tar.gz to /var/tmp/portage/x11-misc/shared-mime-info-0.19/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/x11-misc/shared-mime-info-0.19/work/shared-mime-info-0.19 ...
 * econf: updating shared-mime-info-0.19/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating shared-mime-info-0.19/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-update-mimedb --build=i686-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking for an ANSI C-conforming const... yes
checking for perl... /usr/bin/perl
checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/x11-misc/shared-mime-info-0.19/work/shared-mime-info-0.19/config.log

!!! ERROR: x11-misc/shared-mime-info-0.19 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 2997:   Called src_compile
  shared-mime-info-0.19.ebuild, line 25:   Called econf '--disable-update-mimedb'
  ebuild.sh, line 577:   Called die

!!! econf failed
!!! 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/x11-misc/shared-mime-info-0.19/temp/build.log'.
Does this mean I have a problem with perl?
Top
Skullbot
n00b
n00b
Posts: 7
Joined: Thu Mar 22, 2007 6:24 am
Contact:
Contact Skullbot
Website

  • Quote

Post by Skullbot » Mon Mar 26, 2007 10:42 pm

Nevermind that last. I ran

Code: Select all

perl-cleaner all
and the package emerges fine now.
Top
Post Reply

12 posts • Page 1 of 1

Return to “Portage & Programming”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic