RE: [gentoo-user] C compiler cannot create executables

2005-03-31 Thread Dave Nebinger
 The advice was:
 rm -f /usr/lib32
 ln -s ../../emul/linux/x86/usr/lib /usr/lib32
 FEATURES=-sandbox emerge gcc
 
 This fix the update off gcc problem. (but i am wondering it may break
 somting else?)

Well probably you lost your /usr/lib32's file crt1.o file.  Bummer.

If you remember what the old /usr/lib32 link was you might be able to copy
it back to /usr/lib32.

To properly repair your system you should probably re-emerge glibc now that
gcc is functioning again, but you'll need to get by the missing crt1.o file
before you'll be able to do that.


--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] C compiler cannot create executables

2005-03-31 Thread Ivan Yosifov
http://forums.gentoo.org/viewtopic-t-294109.html
This may help.

On Thu, 2005-03-31 at 20:09 +0200, [EMAIL PROTECTED] wrote:
 First excuse my english. But nobody on the Scandinavian forum know what is 
 wrong. 
 (norwegian version at http://forums.gentoo.org/viewtopic-t-316515.html)
 
 I get the error after updating the system to 2005.0 using this guide 
 http://www.gentoo.org/proj/en/base/amd64/2005.0-upgrade-amd64.xml#doc_chap2 
 (The scripted way) I received no error under the install of 2005.0. 
 
 [maybe important or maybe not important at all]
 The day before the upgrade i fix a bug I had with gcc. I was unable to 
 oppgrade (or downgrade) gcc. but this bug report fixed it. 
 http://bugs.gentoo.org/show_bug.cgi?id=86123
 
 The advice was:
 rm -f /usr/lib32 
 ln -s ../../emul/linux/x86/usr/lib /usr/lib32 
 FEATURES=-sandbox emerge gcc
 
 This fix the update off gcc problem. (but i am wondering it may break somting 
 else?)
 
 Tings I have tested:
 1) fix_libtool_files.sh 3.4.2 
 2) gcc-config 1 
 3) Edit /etc/ld.so.conf all gcc paths point to 3.4.3-20050110 and not 3.4.2
 4) Dubble checked make.conf for errors/typos
 5) Compile with out any CFLAGS and CXXFLAGS
 
 I am aware of Bug 73435 ( http://bugs.gentoo.org/show_bug.cgi?id=73435 ) But 
 I can't see how to fix my system with the answers given in this bug-report. 
 
 ikaro point out 20050110/../../../../x86_64-pc-linux-gnu/bin/ld: crt1.o: No 
 such file: No such file or directory as the error line but I don't now how 
 to use this info :-( 
 
 System info:
 
 [EMAIL PROTECTED] ~ $ gcc-config -l 
 [1] x86_64-pc-linux-gnu-3.4.2 
 [2] x86_64-pc-linux-gnu-3.4.2-hardened 
 [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp 
 [4] x86_64-pc-linux-gnu-3.4.3-20050110 * 
 [5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened 
 [6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie 
 [7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp
 
 [EMAIL PROTECTED] ~ $ emerge --info 
 Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3-20050110, 
 glibc-2.3.4.2 0050125-r1, 2.6.11-gentoo-r4 x86_64) 
 = 
 System uname: 2.6.11-gentoo-r4 x86_64 AMD Athlon(tm) 64 Processor 3000+ 
 Gentoo Base System version 1.6.10 
 Python: dev-lang/python-2.3.5 [2.3.5 (#1, Mar 29 2005, 02:30:26)] 
 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) 
 [disab led] 
 dev-lang/python: 2.3.5 
 sys-devel/autoconf: 2.13, 2.59-r6 
 sys-devel/automake: 1.9.5, 1.5, 1.6.3, 1.7.9-r1, 1.4_p6, 1.8.5-r3 
 sys-devel/binutils: 2.15.92.0.2-r7 
 sys-devel/libtool: 1.5.14 
 virtual/os-headers: 2.6.8.1-r4 
 ACCEPT_KEYWORDS=amd64 ~amd64 
 AUTOCLEAN=yes 
 CFLAGS=-march=k8 -O3 -pipe -frename-registers -fweb 
 CHOST=x86_64-pc-linux-gnu 
 CONFIG_PROTECT=/etc /usr/kde/2/share/config /usr/kde/3.4/env 
 /usr/kde/3.4/share /config /usr/kde/3.4/shutdown /usr/kde/3/share/config 
 /usr/lib/X11/xkb /usr/shar e/config /var/qmail/control 
 CONFIG_PROTECT_MASK=/etc/gconf /etc/terminfo /etc/env.d 
 CXXFLAGS=-march=k8 -O3 -pipe -frename-registers -fweb 
 DISTDIR=/usr/portage/distfiles 
 FEATURES=autoaddcvs autoconfig ccache distlocks sandbox 
 GENTOO_MIRRORS=ftp://ftp.linux.ee/pub/gentoo/distfiles/ 
 ftp://mirror.pudas.net/ gentoo ftp://trumpetti.atm.tut.fi/gentoo/; 
 MAKEOPTS=-j2 
 PKGDIR=/usr/portage/packages 
 PORTAGE_TMPDIR=/var/tmp 
 PORTDIR=/usr/portage 
 PORTDIR_OVERLAY=/usr/local/portage 
 SYNC=rsync://rsync.gentoo.org/gentoo-portage 
 USE=X acpi alsa amd64 avi berkdb bidi bitmap-fonts cdr crypt dba directfb 
 dvd d vdr dvdread encode fam fbcon ffmpeg flac font-server fortran freetype 
 gd ggi gif gimp gpm gtk gtk2 imlib ipv6 jp2 jpeg kde libcaca lzw lzw-tiff mad 
 motif mp3 mp eg mysql ncurses nls ogg oggvorbis opengl oss pam perl png 
 python qt readline sd l spell ssl svg tcltk tcpd tiff truetype truetype-fonts 
 type1-fonts usb userloca les wxwindows xml2 xmms xpm xrandr xv xvid zlib 
 Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
 
 Error report:
 I get this type of error for anyting i try to emerge. irssi as an exampel
 
  Source unpacked. 
 * econf: updating irssi-0.8.10-rc5/config.guess with 
 /usr/share/gnuconfig/config.guess 
 * econf: updating irssi-0.8.10-rc5/config.sub with 
 /usr/share/gnuconfig/config.sub 
 ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man 
 --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc 
 --localstatedir=/var/lib --libdir=/usr/lib64 --with-glib2 
 --without-servertest --with-proxy --with-ncurses --enable-nls --with-perl 
 --enable-ipv6 --without-socks --with-openssl-include=/usr 
 --with-openssl-libs=/usr 
 configure: WARNING: If you wanted to set the --build type, don't use --host. 
 If a cross compiler is detected then cross compile mode will be used. 
 checking for a BSD-compatible install... /bin/install -c 
 checking whether build environment is sane... yes 
 checking whether make sets $(MAKE)... yes 
 checking for working aclocal-1.4... found 
 

Re: [gentoo-user] C compiler cannot create executables

2005-03-31 Thread spetznaz
On Thu, 31 Mar 2005 13:31:19 -0500
Dave Nebinger [EMAIL PROTECTED] wrote:

  The advice was:
  rm -f /usr/lib32
  ln -s ../../emul/linux/x86/usr/lib /usr/lib32
  FEATURES=-sandbox emerge gcc
  
  This fix the update off gcc problem. (but i am wondering it may break
  somting else?)
 
 Well probably you lost your /usr/lib32's file crt1.o file.  Bummer.
 
 If you remember what the old /usr/lib32 link was you might be able to copy
 it back to /usr/lib32.
 
 To properly repair your system you should probably re-emerge glibc now that
 gcc is functioning again, but you'll need to get by the missing crt1.o file
 before you'll be able to do that.
 
 
 --
 gentoo-user@gentoo.org mailing list
 

Well after I updated gcc I run the updatescript and this script merges some 
pacage (portage gcc-config distcc linux-headers etc..) so gcc was working when 
i updated the system to 2005.0 else I will received an error.. (at least i 
suppose so :-)

locate output this:
Mjolne spetznaz # locate crt1.o 
/usr/lib32/Mcrt1.o
/usr/lib32/Scrt1.o
/usr/lib32/crt1.o
/usr/lib32/gcrt1.o
/usr/lib64/crt1.o
/usr/lib64/gcrt1.o
/usr/lib64/Mcrt1.o
/usr/lib64/Scrt1.o

so i don't think crt1.o is the issue.

When it fail to compile with no flags at all i can't see how my CFLAGS can be 
the issue.
--
gentoo-user@gentoo.org mailing list



RE: [gentoo-user] C compiler cannot create executables

2005-03-31 Thread Dave Nebinger
 Well after I updated gcc I run the updatescript and this script merges
 some pacage (portage gcc-config distcc linux-headers etc..) so gcc was
 working when i updated the system to 2005.0 else I will received an
 error.. (at least i suppose so :-)
 
 locate output this:
 Mjolne spetznaz # locate crt1.o
 /usr/lib32/Mcrt1.o
 /usr/lib32/Scrt1.o
 /usr/lib32/crt1.o
 /usr/lib32/gcrt1.o
 /usr/lib64/crt1.o
 /usr/lib64/gcrt1.o
 /usr/lib64/Mcrt1.o
 /usr/lib64/Scrt1.o
 
 so i don't think crt1.o is the issue.

Well, ld is the one complaining, perhaps it's the issue...


--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] C compiler cannot create executables

2005-03-31 Thread Scott Taylor
On Thu, 2005-03-31 at 20:09 +0200, [EMAIL PROTECTED] wrote:
 [EMAIL PROTECTED] ~ $ gcc-config -l 
 [1] x86_64-pc-linux-gnu-3.4.2 
 [2] x86_64-pc-linux-gnu-3.4.2-hardened 
 [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp 
 [4] x86_64-pc-linux-gnu-3.4.3-20050110 * 
 [5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened 
 [6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie 
 [7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp
Whenever I get the cannot create executables message, it is usually
related to the following two files, which if they exist should be
deleted as they are messing with (due to being applied after) the proper
ones that do not end with a hyphen:
/etc/env.d/05gcc-
/etc/env.d/gcc/config-
Delete those two, run env-update and source /etc/profile, then try the
emerge again. Something else that happens to me around the same time is
a complaint about a lib(something).la which cannot be found because its
looking for it in a path without the datestamp. Adding the two symlinks
below helped me with that:

Green# ll /usr/lib/gcc/i686-pc-linux-gnu/
lrwxrwxrwx  1 root root   14 Feb 21 14:03 3.3.5 - 3.3.5-20050130
drwxr-xr-x  4 root root 4096 Mar 30 00:44 3.3.5-20050130
lrwxrwxrwx  1 root root   14 Feb 21 14:02 3.4.3 - 3.4.3-20050110
drwxr-xr-x  4 root root 4096 Mar 31 09:14 3.4.3-20050110

--
Scott Taylor - [EMAIL PROTECTED] 

BOFH Excuse #216:

What office are you in? Oh, that one.  Did you know that your building
was built over the universities first nuclear research site? And wow,
aren't you the lucky one, your office is right over where the core is
buried!



--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] C compiler cannot create executables

2005-03-31 Thread Eric Thompson
On Thu, 31 Mar 2005 16:07:10 -0700, Scott Taylor
[EMAIL PROTECTED] wrote:
 On Thu, 2005-03-31 at 20:09 +0200, [EMAIL PROTECTED] wrote:
  [EMAIL PROTECTED] ~ $ gcc-config -l
  [1] x86_64-pc-linux-gnu-3.4.2
  [2] x86_64-pc-linux-gnu-3.4.2-hardened
  [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp
  [4] x86_64-pc-linux-gnu-3.4.3-20050110 *
  [5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened
  [6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie
  [7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp
 Whenever I get the cannot create executables message, it is usually
 related to the following two files, which if they exist should be
 deleted as they are messing with (due to being applied after) the proper
 ones that do not end with a hyphen:
 /etc/env.d/05gcc-
 /etc/env.d/gcc/config-
 Delete those two, run env-update and source /etc/profile, then try the
 emerge again. Something else that happens to me around the same time is
 a complaint about a lib(something).la which cannot be found because its
 looking for it in a path without the datestamp. Adding the two symlinks
 below helped me with that:
 
 Green# ll /usr/lib/gcc/i686-pc-linux-gnu/
 lrwxrwxrwx  1 root root   14 Feb 21 14:03 3.3.5 - 3.3.5-20050130
 drwxr-xr-x  4 root root 4096 Mar 30 00:44 3.3.5-20050130
 lrwxrwxrwx  1 root root   14 Feb 21 14:02 3.4.3 - 3.4.3-20050110
 drwxr-xr-x  4 root root 4096 Mar 31 09:14 3.4.3-20050110
 
 --
 Scott Taylor - [EMAIL PROTECTED]
 
 BOFH Excuse #216:
 
 What office are you in? Oh, that one.  Did you know that your building
 was built over the universities first nuclear research site? And wow,
 aren't you the lucky one, your office is right over where the core is
 buried!
 
 
 --
 gentoo-user@gentoo.org mailing list
 
 

Every time I get the cannot create executables error, it has been a
bad binutils.  I noticed in you emerge info that you are using
binutils-2.15.92.0.2-r7 and every version above -r2 has been bad for
me, so I just masked the versions above -r4, and used -r2.  There are
binary packages at http://dev.gentoo.org/~avenj/bins/ if you need them
to get your system back up and running.

Hope this helps

-- 
Eric Thompson
[EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] C compiler cannot create executables

2003-06-12 Thread Ryan
I got this error message when my CFLAGS were messed up. It looks like
you've got a problem in yours. I think you meant -march instead of
-match

your:
CFLAGS=-match=pentium-mmx -O3 -pipe -fomit-frame-pointer

should be:
CFLAGS=-march=pentium-mmx -O3 -pipe -fomit-frame-pointer

Hope that helps.

Ryan
[EMAIL PROTECTED]

  so im trying to do a stage 3 install on an old pentium 233mmx box and i
 get
 this errior whenever i try to emerge some thing. ive cheaked if my
 make.conf
 has any line break's in it but, no.

 any one know what im goign wrong?


 my make.conf is appended to the end of this message.


 thanx all (did any of this message amke sence?)

 

 emerge gzip_x86
 Calculating dependencies ...done!
 emerge (1 of 1) sys-apps/gzip_x86-0.90 to /
 Downloading http://gentoo.oregonstate.edu//distfiles/gzip_x86-0.90.tgz
 --11:48:33--  http://gentoo.oregonstate.edu//distfiles/gzip_x86-0.90.tgz
= `/usr/portage/distfiles/gzip_x86-0.90.tgz'
 Resolving gentoo.oregonstate.edu... done.
 Connecting to gentoo.oregonstate.edu[128.193.0.3]:80... connected.
 HTTP request sent, awaiting response... 200 OK
 Length: 333,860 [application/x-tar]

 100%[===
 ===] 333,8604.25K/sETA 00:00

 11:49:52 (4.25 KB/s) - `/usr/portage/distfiles/gzip_x86-0.90.tgz' saved
 [333860/333860]

 md5 ;-) gzip_x86-0.90.tgz
 Unpacking source...
 Unpacking gzip_x86-0.90.tgz to /var/tmp/portage/gzip_x86-0.90/work
 Source unpacked.
 configure: WARNING: If you wanted to set the --build type, don't use
 --host.
 If a cross compiler is detected then cross compile mode will be used.
 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 i586-pc-linux-gnu-strip... no
 checking for strip... strip
 checking for i586-pc-linux-gnu-gcc... gcc
 checking for C compiler default output... configure: error: C compiler
 cannot create executables

 !!! ERROR: sys-apps/gzip_x86-0.90 failed.
 !!! Function src_compile, Line 20, Exitcode 77
 !!! ./configure failed


 =




 # Copyright 2000-2002 Daniel Robbins, Gentoo Technologies, Inc.
 # Contains local system settings for Portage system
 # Please review 'man make.conf' for more information.

 # Build-time functionality
 # 
 #
 # The USE variable is used to enable optional build-time functionality.
 For
 # example, quite a few packages have optional X, gtk or GNOME
 functionality
 # that can only be enabled or disabled at compile-time. Gentoo Linux has a
 # very extensive set of USE variables described in our USE variable HOWTO
 at
 # http://www.gentoo.org/doc/use-howto.html
 #
 # The available list of use flags with descriptions is in your portage
 tree.
 # Use 'less' to view them:  -- less /usr/portage/profiles/use.desc --
 #
 # Example:
 #USE=X gtk gnome -alsa

 # Host Setting
 # 
 #
 # If you are using a Pentium Pro or greater processor, leave this line
 as-is;
 # otherwise, change to i586, i486 or i386 as appropriate. All modern
 systems
 # (even Athlons) should use i686-pc-linux-gnu
 #
 CHOST=i586-pc-linux-gnu

 # Host and optimization settings
 # ==
 #
 # For optimal performance, enable a CFLAGS setting appropriate for your
 CPU
 #
 # -mcpu=cpu-type means optimize code for the particular type of CPU
 without
 # breaking compatibility with other CPUs.
 #
 # -march=cpu-type means to take full advantage of the ABI and
 instructions
 # for the particular CPU; this will break compatibility with older CPUs
 (for
 # example, -march=athlon-xp code will not run on a regular Athlon, and
 # -march=i686 code will not run on a Pentium Classic.
 #
 # CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
 athlon-4,
 # athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
 # (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron),
 pentium3,
 # and pentium4. Note that Gentoo Linux 1.4 and higher include at least
 gcc-3.2.
 #
 # CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
 # (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use
 gcc-2.95*
 #
 # Decent examples:
 #
 #CFLAGS=-mcpu=athlon-xp -O3 -pipe
 CFLAGS=-match=pentium-mmx -O3 -pipe -fomit-frame-pointer

 # If you set a CFLAGS above, then this line will set your default C++
 flags
 to
 # the same settings. If you don't set CFLAGS above, then comment this line
 out.
 CXXFLAGS=${CFLAGS}

 # Advanced Masking
 # 
 #
 # Gentoo is using a new masking system to allow for easier stability
 testing
 # on packages. KEYWORDS are used in ebuilds to mask and unmask packages
 based
 # on the platform they are set for. A special form has been added that
 # indicates packages and revisions that are expected to