From: <ast...@el...> - 2007-03-16 09:08:36
|
On 3/15/07, Kristian Kielhofner <kri...@gm...> wrote: > On 3/12/07, ast...@el... <ast...@el...> wrote: > > Got a bit of a surprise shock when I decided to go a little bleeding edge > > with a trunk compile. Seems bash has a minor issue, though I hadn't seen > > it before when I either was able to complete a compile, or at least get > > much farther along. > > > > This is trunk 757 with gcc 4.2 snapshot 20070307 , compile with ObjC, > > shared libraries, and libtool. This is on an older svn checkout where I > > had wiped out toolchain, toolchain_buildi586, and build_i586 and did a svn > > update to rebuild those parts cleanly while retaining the dl directory. > > > > asterisk, > > Wow, that is bleeding edge! > > Anyways, I can't really make much sense out of that error. Can you > turn the number of parallel builds down and run make after script? > > -- > Kristian Kielhofner But the concurrent jobs setting was at the default 2... I've reinstalled a fair amount of stuff, and ran with only 1 concurrent job and that seemed to make it go away, I think. Using gcc 4.2 20070307, binutils 2.16.91.0.7 , and a hand fix in the makefile for syslinux so it doesn't call the windows stuff (changing the $(BOBJECTS) to $(BTARGET), I got a compile to finish properly. Too bad I don't have an easy way to test the image itself. I'm really tempted to make a proper VMware development environment so I can say definitively that my environment isn't at fault. Maybe stick that into the SVN repository as well? |