Re: x11 cross-compile errors

2014-12-31 Thread John D. Baker
Following this commit by christos@: http://mail-index.netbsd.org/source-changes/2014/12/30/msg061920.html I can once-again build -current xorg Mesa for sparc, powerpc, and mips64el on my puny, consumer-grade, trash-heap-salvage PeeCee machines. Thanks. -- |/"\ John D. Baker, KN5UKS

Re: x11 cross-compile errors

2014-12-30 Thread John D. Baker
On Mon, 29 Dec 2014, John D. Baker wrote: > Meanwhile, I did a fresh build of -current/prep on a -6/amd64 host > WITHOUT the changes to "src/external/mit/xorg/lib/libmesa.mk" since the > nightly build machines seem to have no problems. I checked a sample output log and saw that the nightly build

Re: x11 cross-compile errors

2014-12-29 Thread John D. Baker
On Sun, 28 Dec 2014, John D. Baker wrote: > The end result is the compiler command line has "-O2" early on but has > "-O1" later, overriding the previous optimisation flag. With this change, > "format_utils.c" compiles and my build of macppc w/gcc48 is proceeding. > I will back up to sparc and ev

Re: x11 cross-compile errors

2014-12-28 Thread John D. Baker
On Sun, 28 Dec 2014, Dennis Ferguson wrote: > On 28 Dec, 2014, at 09:08 , John D. Baker wrote: > > There seemed to be a "CFLAGS." construct to permit per-source > > setting of CFLAGS contents, but it had no effect when I tried it. Perhaps > > I put it in the wrong place? > > I always have troub

Re: x11 cross-compile errors

2014-12-28 Thread Christos Zoulas
In article , John D. Baker wrote: >On Sat, 27 Dec 2014, John D. Baker wrote: > >> Then I'll build with the now-default gcc48. Unlike all the other builds, >> this will be a non-update build with empty target directories (at least >> as far as the macppc objects/tools are concerned). > >No dice.

Re: x11 cross-compile errors

2014-12-28 Thread Dennis Ferguson
On 28 Dec, 2014, at 09:08 , John D. Baker wrote: > There seemed to be a "CFLAGS." construct to permit per-source > setting of CFLAGS contents, but it had no effect when I tried it. Perhaps > I put it in the wrong place? > > Hints? I always have trouble figuring this out on the rare occasions I

Re: x11 cross-compile errors

2014-12-28 Thread John D. Baker
On Sat, 27 Dec 2014, John D. Baker wrote: > Then I'll build with the now-default gcc48. Unlike all the other builds, > this will be a non-update build with empty target directories (at least > as far as the macppc objects/tools are concerned). No dice. Even a clean build of tools, etc. won't w

Re: x11 cross-compile errors

2014-12-27 Thread John D. Baker
On Sat, 27 Dec 2014, John D. Baker wrote: > I hadn't built any ppc ports since they were switched to gcc48. As a bit > of a test, I'm now building macppc with "-V HAVE_GCC=45" to leverage my > existing ${TOOL,OBJ,DEST}DIRs and see if it misbehaves. Cross-building -current/macppc on -7/i386 using

Re: x11 cross-compile errors

2014-12-27 Thread John D. Baker
On Wed, 24 Dec 2014, John D. Baker wrote: > I usually also compile -current for i386, amd64, macppc, prep, mvme68k, > mac68k, sparc64, and evbmips-mips64el, but have only attempted the i386 Cross-building -current/m{vme,ac}68k on -7/i386 succeeded, although these are still using gcc45 by default.

Re: x11 cross-compile errors

2014-12-26 Thread John D. Baker
On Wed, 24 Dec 2014, John D. Baker wrote: > I usually also compile -current for i386, amd64, macppc, prep, mvme68k, > mac68k, sparc64, and evbmips-mips64el, but have only attempted the i386 Cross-compile of -current/sparc64 on -7/i386 host completed successfully. -- |/"\ John D. Baker, KN5UKS

Re: x11 cross-compile errors

2014-12-26 Thread John D. Baker
On Wed, 24 Dec 2014, John D. Baker wrote: > I usually also compile -current for i386, amd64, macppc, prep, mvme68k, > mac68k, sparc64, and evbmips-mips64el, but have only attempted the i386 Cross-building for evbmips-mips64el fails in the same fashion: [...] --- format_utils.o --- cc1: out of m

Re: x11 cross-compile errors

2014-12-24 Thread John D. Baker
On Wed, 24 Dec 2014 13:39:50 -0500, scole_mail wrote: >>> cc1: out of memory allocating 1081140 bytes after a total of 896122880 bytes >>> *** [format_utils.pico] Error code 1 > For format_utils.pico, the -02 flag seems to be causing the out of > memory error. When I removed that flag it compil

Re: x11 cross-compile errors

2014-12-24 Thread scole_mail
I tried rebuilding tools and release after updating with compat_defs.h fix and still got the same error about __UNVOLATILE. It compiles if I add #define __UNVOLATILE(a) ((void *)(unsigned long)(volatile void *)(a)) directly to fccache.c >> cc1: out of memory allocating 1081140 bytes after a to

Re: x11 cross-compile errors

2014-12-24 Thread Christos Zoulas
In article <20141224153913.GA13898@debian.domain.actdsltmp>, scole_mail wrote: >I've been cross-compiling current/macppc/release on a linux system for >awhile and x11 recently stopped compiling. > >One problems is that it seems like >xsrc/external/mit/fontconfig/dist/src/fccache.c is missing it

x11 cross-compile errors

2014-12-24 Thread scole_mail
I've been cross-compiling current/macppc/release on a linux system for awhile and x11 recently stopped compiling. One problems is that it seems like xsrc/external/mit/fontconfig/dist/src/fccache.c is missing its reference to __UNVOLATILE . I tried adding '#include ' where I thought it was defin