Building CLFS fails at glibc, whats wrong with my gcc?

Page 1 of 1 [ 6 posts ] 

dcj123
Veteran
Veteran

User avatar

Joined: 2 Sep 2009
Gender: Male
Posts: 10,796

02 May 2016, 4:01 pm

I am on chapter 5 of CLFS and I am having trouble with glibc. I am on the 32 bit part and when I configure it I get this,

Code:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... -gcc
checking for suffix of object files... configure: error: in `/mnt/clfs/sources/glibc-build':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details


Google reveals this is normally a problem with my GCC, I am building CLFS from an Arch Linux CD and my gcc version reads.

Code:
gcc version 5.3.0 (GCC)


I am open to suggestions, this is driving right up the wall and I am going to take a break before I put a hole in my monitor. I am using the git version of CLFS because 3.0 is quite old and uses a kernel that is like 2-3 years old.



mr_bigmouth_502
Veteran
Veteran

User avatar

Joined: 12 Dec 2013
Age: 31
Gender: Non-binary
Posts: 7,028
Location: Alberta, Canada

03 May 2016, 10:03 am

dcj123 wrote:
I am on chapter 5 of CLFS and I am having trouble with glibc. I am on the 32 bit part and when I configure it I get this,

Code:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for gcc... -gcc
checking for suffix of object files... configure: error: in `/mnt/clfs/sources/glibc-build':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details


Google reveals this is normally a problem with my GCC, I am building CLFS from an Arch Linux CD and my gcc version reads.

Code:
gcc version 5.3.0 (GCC)


I am open to suggestions, this is driving right up the wall and I am going to take a break before I put a hole in my monitor. I am using the git version of CLFS because 3.0 is quite old and uses a kernel that is like 2-3 years old.

Just an idea, but maybe you'd be better off starting out compiling a system from older, more stable sources, then upgrading to newer sources once you have things up and working. Newer =! better, especially with open source software where things are prone to change and break all the time.


_________________
Every day is exactly the same...


dcj123
Veteran
Veteran

User avatar

Joined: 2 Sep 2009
Gender: Male
Posts: 10,796

03 May 2016, 1:27 pm

mr_bigmouth_502 wrote:
Just an idea, but maybe you'd be better off starting out compiling a system from older, more stable sources, then upgrading to newer sources once you have things up and working. Newer =! better, especially with open source software where things are prone to change and break all the time.


Yeah I am actually thinking about compiling LFS instead of CLFS, I lose multilib support but it'll get me some experience compiling Linux from scratch. So my focus will be on that instead of the above, also worth noting, I've changed my host to Ubuntu. Arch is out because for one, it'll run out of disk space running off a live cd before you can get the needed dependencies.

However, this post is still valid and welcome to ideas. I have multiple computers and its not like that one is doing anything else. I am probably going to try LFS in a virtual machine because my FX processor will compile faster than any of my phenom processors. I have few computers from the Pentium and Athlon days and only use them for storage and samba and most don't even have GUIs. I also have computers I am going to sale cause I eliminated their use simply by putting their hard drive in my main Desktop.

I honestly have no idea how I got so many computers but its like the only thing I have really which is bizarre but I guess something within the realms of normal for an autistic person to do. I guess I dumpster drived a lot in my day, its just strange that people throw away a pretty nice computer simply cause one part is out. Still I am going to try and shrink my fleet.



mr_bigmouth_502
Veteran
Veteran

User avatar

Joined: 12 Dec 2013
Age: 31
Gender: Non-binary
Posts: 7,028
Location: Alberta, Canada

04 May 2016, 8:30 am

That sounds kind of like what I used to do when I was younger and had access to an e-waste recycle pile, as well as more storage space. Although in my case, I was more interested in setting machines up for multiplayer gaming. LAN parties were kind of my special interest for a long time, and looking back, while I learned a number of things, I kind of regret wasting so much time trying to get my friends on board with something I could barely get working half the time, that they were only mildly interested in. Well, OK, they were interested in playing games, but usually not the games I was interested in playing, and I definitely had more of an interest in getting older machines going and making them usable. They just wanted things that worked straight out.


_________________
Every day is exactly the same...


zazen
Butterfly
Butterfly

User avatar

Joined: 19 Aug 2015
Posts: 17

07 May 2016, 9:10 am

Could you post the contents of config.log?



dcj123
Veteran
Veteran

User avatar

Joined: 2 Sep 2009
Gender: Male
Posts: 10,796

09 May 2016, 2:40 pm

zazen wrote:
Could you post the contents of config.log?


um as a matter of fact I can't.

I shutdown the PC and when I rebooted and tried CLFS again I actually got pass this part. Everything so far has compiled ok but I went to sleep (left the PC on) so I haven't finished CLFS but I am a good ways into it.

I suspect the problem was an environmental variable cause when I setup the CLFS user, I logged out and back in and I think that messed some stuff up. Another reason I suspect an environmental variable is off is according to google this error can indicate two things. It could mean gcc is broken but I also found its kinda of a catch all error for just about anything. I suspect gcc was suppose to see something in the cross-tools directory and didn't cause stuff wasn't being installed where it needed to be.

Thats my theory, its impossible to know what was wrong cause the system was reset.