In message <[email protected]> Frank de Bruijn <[email protected]> wrote:
> In article <[email protected]>, > John Tytgat <[email protected]> wrote: > > In message <[email protected]> > > Frank de Bruijn <[email protected]> wrote: > > > The first problem was rman failing on building libx11. I created a > > > symlink called rman pointing to /bin/true to hack that out of the > > > way (cf. list message <[email protected]>). > > > Or either install rman on your build machine. > > It *is* installed, but it fails. See the message I was referring to (by > Chris, dated 5-5-2012, in the thread 'Autobuilder and Scummvm'). I see. > > We're checking on a minimal set of buildtools in 'build' but I don't > > think 'build-libs' is using 'build'. And that's probably also the > > cause of the dependencies issues you're reporting here. > > As far as I can tell, build-libs does use build. The last couple of > lines of build-libs are: > > lib=$(getnext) > > while [ -n "$lib" ] ; do > > $base/build -v $lib > > lib=$(getnext) > done > > echo "All libraries built" > > > Again, 'build-libs' should be able to sort out dependencies by using > > 'build'. > > Well, it seems that doesn't always work. Not so good news then. I hope someone can look & fix autobuiler. > > > The failing #include is for .../bits/socket2.h and this actually > > > does not exist. I found a socket2.h file -which does indeed define > > > macros- on my host system in /usr/include/i386-linux-gnu/bits, but > > > I'm not sure if I can copy that to the cross compiler's .../bits > > > unchanged. > > > This was a couple of months ago fixed in UnixLib @ trunk. Are you > > using the cross-compiler (recently ?) built from trunk/gcc4 or > > branches/release_4_1_2 ? > > I'm using branches/release_4_1_2. I wanted the 'stable' version... Unfortunately both problems (byteswap.h and socket2.h) were also present in release_4_1_2 branch. The good news is that I've fixed both problems in that branch a couple of hours ago. John. -- John Tytgat, in his comfy chair at home [email protected] _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
