Dave McGuire wrote: >>> I'm working with 2.9.7, one of the source snapshots from a few >>> days ago, 20100313-5734. >>> >>> The first thing that breaks is the automatic inclusion of -Wall >>> (which is GCC-specific) in CFLAGS. >>> >>> Next comes this line in src/pic/ralloc.c: >>> >>> #define FENTRY2 1 ? (void)0 : printf >>> >>> I removed the void cast; that allowed it to compile. >>> >> This should not be a problem. I'll try it on gcc without the cast. We >> can still use #ifdef SOLARIS or something. Can you tell me which is >> the >> most appropriate preprocessor symbol defined by the Sun Studio 12 >> compiler? >> > > Yes, I usually check for "defined(sun) && defined(__SVR4)". > >
This defines the OS. Probably this symbols are defined for gcc too. I think we need something the defines the compiler. >>> The last one is a weird problem that I've not really dug into yet; >>> I think it probably has to do with -E handling. The Makefile.dep >>> files end up being huge (several megabytes) and contain lots of C >>> source code fragments. I ended up just turning that into "touch >>> Makefile.dep" in the Makefiles and being careful about doing a "make >>> clean" between builds, which is obviously not the correct solution. >>> >> Tis is the hardest one: the gcc preprocessor understands -M command >> line >> option, which generates the makefile dependencies. I don't know if >> Solaris cc can do this. If not, an external toll should be found >> and used. >> > > It can; the option for thisis "-xM". > > So -MM should be replaced with -xM in case of Sun Studio 12 compiler. > >> If we'll solve all the problems, can your machine be used for nightly >> snapshot builds? >> > > Yes. We actually talked about this a couple of years ago, then I > got busy and couldn't do it on my end. Maybe we can do it now. > > Yes, I remember, that's why I'm asking ;-) >> I'm very unsatisfied with the current situation, since we have only >> Linux on amd64 and Mac OS X on PPC. >> > > I understand. I can probably help with this; I've just set up a > large VMware host machine here since I now need to support some > consulting clients running VMware. It runs full-time, and it is WAY > overpowered for my immediate needs (two SCO virtual machines). I can > easily spin up a few more VMs on it and get you Solaris/x86, NetBSD/ > i386 and possibly FreeBSD, if it runs nicely under VMware (which it > probably does). > > I suppose now you are talking about VMs on x86 host? > Do you have a shell script or something set up to pull from svn > and do a build? If so, and if it were self-contained and relatively > portable, it'd make this very easy to set up. > > Everything is in the svn, see directories sdcc-build (build scripts) and sdcc-cf (distributed compile farm scripts). The setup is not trivial. The easiest way is to create an sdcc-builder account and give me ssh access, so that configure the build process. This is how we have done it on cf-x86 (Linux amd64) and mirror-doors (Mac OS X ppc) snapshot build machines. We can discuss abut this on a private channel... >> Is Solaris on sparc or x86? >> > > This is on UltraSPARC, as that's my primary platform here, as well > as that of my employer, so I have plenty of capacity available. > > Great, since UltraSPARC is a big-endian machine! Borut ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
