1 |
Every time I take the time to think through and write something like |
2 |
this up, I solve it pretty quickly afterwards. I'll tell you how I |
3 |
solved it. GCC wasn't the problem, and gcc-config -l wouldn't of done |
4 |
any good because I only had one gcc. So I created a simple hello.c |
5 |
that fprint("Hello Working GCC\n"); Then I tried to compile it. I |
6 |
noticed in the error message (btw, it did not compile) about a library |
7 |
and binutils. So I already had my emerge setup that if I wanted to |
8 |
install a bin-package, I could, so I grabbed a bin package of |
9 |
binutils. hello.c compiled, but I didn't want to get excited too soon. |
10 |
I had to see if emerge would work without error, and it did. I |
11 |
compiled a newer kernel and now I need to recompile libtools because |
12 |
you're supposed to do that everytime you upgrade your gcc. I will |
13 |
recompile binutils also so it will have optimizations for my hardware. |
14 |
|
15 |
Christopher Lemire <christopher.lemire@×××××.com> |
16 |
Ubuntu 64 bit Linux Raid Level 0 |
17 |
|
18 |
Gnu Privacy Guard Key Fingerprint = 3E1A 9103 EF3D 4885 6866 E9DE |
19 |
C69F 18B3 E13B 0909 |
20 |
|
21 |
Web: http://linuxinnovations.blogspot.com |
22 |
Jabber: recursivequicksort@××××××.org |
23 |
|
24 |
|
25 |
On Mon, Jul 16, 2012 at 8:15 AM, Todd Goodman <tsg@×××××××××.net> wrote: |
26 |
> * Christopher Lemire <christopher.lemire@×××××.com> [120716 08:08]: |
27 |
> [..] |
28 |
>> Making a simple Hello World and attempting to compile: |
29 |
>> |
30 |
>> bullshark@beastlinux ~ % cat hello.c |
31 |
>> #include <stdio.h> |
32 |
>> |
33 |
>> main() { |
34 |
>> printf("Hello Working GCC\n."); |
35 |
>> } |
36 |
>> bullshark@beastlinux ~ % gcc hello.c -o hello |
37 |
>> /usr/lib/gcc/i686-pc-linux-gnu/4.5.3/../../../../i686-pc-linux-gnu/bin/as: |
38 |
>> symbol lookup error: |
39 |
>> /usr/lib/binutils/i686-pc-linux-gnu/2.21.1/libopcodes-2.21.1.so: |
40 |
>> undefined symbol: buffer_read_memory |
41 |
>> bullshark@beastlinux ~ % |
42 |
> |
43 |
> You might need to run gcc-config. |
44 |
> |
45 |
> Try gcc-config -l and make sure one of the selections has an * next to |
46 |
> it. |
47 |
> |
48 |
> If not, run gcc-config <cc profile> |
49 |
> where <cc profile> is the name you see in the gcc-config -l output (like |
50 |
> i686-pc-linux-gnu-4.5.3, for example) |
51 |
> |
52 |
> Todd |
53 |
> |