Re: [gentoo-user] GCC/Build Problems

[Christopher Lemire]

Every time I take the time to think through and write something like
this up, I solve it pretty quickly afterwards. I'll tell you how I
solved it. GCC wasn't the problem, and gcc-config -l wouldn't of done
any good because I only had one gcc. So I created a simple hello.c
that fprint("Hello Working GCC\n"); Then I tried to compile it. I
noticed in the error message (btw, it did not compile) about a library
and binutils. So I already had my emerge setup that if I wanted to
install a bin-package, I could, so I grabbed a bin package of
binutils. hello.c compiled, but I didn't want to get excited too soon.
I had to see if emerge would work without error, and it did. I
compiled a newer kernel and now I need to recompile libtools because
you're supposed to do that everytime you upgrade your gcc. I will
recompile binutils also so it will have optimizations for my hardware.

Christopher Lemire 
Ubuntu 64 bit Linux Raid Level 0

Gnu Privacy Guard Key Fingerprint = 3E1A 9103 EF3D 4885 6866  E9DE
C69F 18B3 E13B 0909

Web: http://linuxinnovations.blogspot.com
Jabber: recursivequicks...@jabber.org


On Mon, Jul 16, 2012 at 8:15 AM, Todd Goodman  wrote:
> * Christopher Lemire  [120716 08:08]:
> [..]
>> Making a simple Hello World and attempting to compile:
>>
>> bullshark@beastlinux ~ % cat hello.c
>> #include 
>>
>> main() {
>>   printf("Hello Working GCC\n.");
>> }
>> bullshark@beastlinux ~ % gcc hello.c -o hello
>> /usr/lib/gcc/i686-pc-linux-gnu/4.5.3/../../../../i686-pc-linux-gnu/bin/as:
>> symbol lookup error:
>> /usr/lib/binutils/i686-pc-linux-gnu/2.21.1/libopcodes-2.21.1.so:
>> undefined symbol: buffer_read_memory
>> bullshark@beastlinux ~ %
>
> You might need to run gcc-config.
>
> Try gcc-config -l and make sure one of the selections has an * next to
> it.
>
> If not, run gcc-config 
> where  is the name you see in the gcc-config -l output (like
> i686-pc-linux-gnu-4.5.3, for example)
>
> Todd
>

Re: [gentoo-user] GCC/Build Problems

[Todd Goodman]

* Christopher Lemire  [120716 08:08]:
[..]
> Making a simple Hello World and attempting to compile:
> 
> bullshark@beastlinux ~ % cat hello.c
> #include 
> 
> main() {
>   printf("Hello Working GCC\n.");
> }
> bullshark@beastlinux ~ % gcc hello.c -o hello
> /usr/lib/gcc/i686-pc-linux-gnu/4.5.3/../../../../i686-pc-linux-gnu/bin/as:
> symbol lookup error:
> /usr/lib/binutils/i686-pc-linux-gnu/2.21.1/libopcodes-2.21.1.so:
> undefined symbol: buffer_read_memory
> bullshark@beastlinux ~ %

You might need to run gcc-config.

Try gcc-config -l and make sure one of the selections has an * next to
it.

If not, run gcc-config 
where  is the name you see in the gcc-config -l output (like
i686-pc-linux-gnu-4.5.3, for example)

Todd

[gentoo-user] GCC/Build Problems

[Christopher Lemire]

I was doing a system upgrade. Following the instructions from

http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2&chap=1

emerge  --sync
emerge --update --deep world

So after that, everything was updated except build dependencies and
packages that had a use flag change on them, so I believe building one
of the build dependencies failed causing all the problems I am having.
I did:

emerge --update --deep --with-bdeps=y --newuse world




So I would often get the message

configure: error: C compiler cannot create executables
See `config.log' for more details




So, what I did is get another gcc compiler as a bin package, and set
it as my default with gcc-config.

I then tried to rebuild libtool. Again, I got the same message (in the
bold part):

bullshark@beastlinux ~ % sudo emerge -av --oneshot libtool
Password:

 * IMPORTANT: 3 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R] sys-devel/libtool-2.4-r1  USE="-test -vanilla*" 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB

Would you like to merge these packages? [Yes/No] y

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) sys-devel/libtool-2.4-r1
 * libtool-2.4.tar.xz RMD160 SHA1 SHA256 size ;-) ...  [ ok ]
>>> Unpacking source...
>>> Unpacking ./libtool-2.4.tar to 
>>> /var/tmp/portage/sys-devel/libtool-2.4-r1/work
>>> Source unpacked in /var/tmp/portage/sys-devel/libtool-2.4-r1/work
>>> Preparing source in 
>>> /var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4 ...
 * Applying libtool-1.5.20-use-linux-version-in-fbsd.patch ... [ ok ]
 * Running eautoreconf in
'/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4/libltdl'
...
 * Running true --install --copy --force --automake ...[ ok ]
 * Running aclocal -I m4 ...   [ ok ]
 * Running autoconf ...[ ok ]
 * Running autoheader ...  [ ok ]
 * Running automake --add-missing --copy --foreign ... [ ok ]
 * Running eautoreconf in
'/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4' ...
 * Running true --install --copy --force --automake ...[ ok ]
 * Running aclocal -I libltdl/m4 ...   [ ok ]
 * Running autoconf ...[ ok ]
 * Running autoheader ...  [ ok ]
 * Running automake --add-missing --copy ...   [ ok ]
>>> Source prepared.
>>> Configuring source in 
>>> /var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4 ...
 * econf: updating libtool-2.4/libltdl/config/config.sub with
/usr/share/gnuconfig/config.sub
 * econf: updating libtool-2.4/libltdl/config/config.guess with
/usr/share/gnuconfig/config.guess
./configure --prefix=/usr --build=i686-pc-linux-gnu
--host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --dat
adir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib
## --- ##
## Configuring libtool 2.4 ##
## --- ##

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
configure: autobuild project... GNU Libtool
configure: autobuild revision... 2.4 ()
configure: autobuild hostname... beastlinux
configure: autobuild mode... default
configure: autobuild timestamp... 20120715T164750Z
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
[b]checking whether the C compiler works... no
configure: error: in
`/var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4':
configure: error: C compiler cannot create executables
See `config.log' for more details[/b]

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sys-devel/libtool-2.4-r1/work/libtool-2.4/config.log
 * ERROR: sys-devel/libtool-2.4-r1 failed (configure phase):
 *   econf failed
 *
 * Call stack:
 *ebuild.sh, line   85:  Called src_configure
 *  environment, line 2807:  Called default
 *   phase-functions.sh, line  798:  Called _eapi2_src_configure
 * phase-helpers.sh, line  567:  Called econf
 * phase-helpers.sh, line  467:  Called die
 * The specific snippet of code:
 *  die "econf failed"
*
 * If you need support, post the output of `emerge --info
'=sys-devel/libtool-2.4-r1'`,
 * the complete build log and the output of `emerge -pqv
'=sys-devel/libtool-2.4-r1'`.
/usr/lib/portage/bin/isolated-functions.sh: line 214: wait: `econf
failed': not a pid or valid job spec
 * The complete build log i