OESF Portables Forum

Everything Else => Zaurus - Everything Development => Distros, Development, and Model Specific Forums => Archived Forums => Open Embedded => Topic started by: nhorlock on May 07, 2005, 05:08:17 pm

Title: Bitbake Fails With Gnu Gcc
Post by: nhorlock on May 07, 2005, 05:08:17 pm

I'm trying to build something (anything right now would be a start!) on OE but bitbake is unable to retrieve some or all of the gcc pavkage becuase the anonymous CVS @ savannah.gnu.org just timesout. How can I get around this?

Neil

Title: Bitbake Fails With Gnu Gcc
Post by: lardman on May 07, 2005, 05:41:47 pm

Is savannah.gnu.org down atm?

If so, this is a problem, but not a permanent one.


Si

Title: Bitbake Fails With Gnu Gcc
Post by: nhorlock on May 08, 2005, 04:39:14 pm

Savannah didn't seem to be broken, insofar that webcvs was fine. I tried gcc.gnu.org as well and that also failed. In the end I tried to pull it manually (despite not having the slightest clue where to move it to after I'd got it. That worked. I then tried bitbake again and it also started to pull down gcc.

The question is was this pure coincidence that savannah came back just when I tried the manual pull or (more likely) is the fact that I exported CVS_RSH=ssh and set my CVSROOT manually prior to the last attempt anything to do with this? I thought bitbake controlled all the environmental settings but this would suggest I am wrong.

I've moved on to the next problem now (still in gcc) it is failing to build libiberty due to an undefined function __builtin_expect which is supposedly a gcc builtin for branch prediction hinting.

Ho hum, I'll get there in the end.

Neil

Title: Bitbake Fails With Gnu Gcc
Post by: nhorlock on May 09, 2005, 05:50:29 am

Quote

I've moved on to the next problem now (still in gcc) it is failing to build libiberty due to an undefined function __builtin_expect which is supposedly a gcc builtin for branch prediction hinting.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=78811\"][{POST_SNAPBACK}][/a][/div]

Thanks to help from #oe (PB__ in particular for his suggestion) I've found that this one was because I was using a shell that had previously been used to build an old Sharp/Opie and thus was finding an old gcc  from the embeddix toolchain.

So a tip for you all. Start with a clean shell and check your gcc before you start. I wasted a lot of time trying to figure out what was wrong.

Neil