Issue with the Sun's C Compiler `cc'

Brian J. Tarricone bjt23 at cornell.edu
Mon Dec 5 02:39:13 CET 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Lecomte wrote:
> Greetings,
> I'm trying to get XFce 4.2 compiled on Sun Solaris 10, with the Sun's
> C Compiler.
> However, it seems that you use GCC-specific stuff in your source code.
> For example, the compiler refuses to handle this correctly:
> extern const char xfce_builtin_license_##name[];
> 
> It would be nice if you could use a more universal way to manage the
> licensing stuff, because I'm forced to use GCC for some modules, which
> is not as fast as the Sun CC. :-)
> 
> If you are ok to modify the way you handle licensing stuff, I'll be
> proud to help you and to test it.

Most of us use gcc to compile Xfce, and I'm not sure that any of us has
regular access to a Sun box, so sometimes it's very hard to avoid
letting gcc-isms creep into Xfce's code.  Sometimes they're not even
gcc-isms; sometimes the problem is that Sun's compiler supports only
older versions of the C spec.  So unfortunately we often have to rely on
others who have access to a Sun box to submit patches.

In this specific case, I believe the problem is that Sun's macro
preprocessor is a piece of crap.

So you have two options:  fix it yourself and send patches, or at least
provide full error messages so someone else has even the slightest
chance of fixing it.

My memory feels like this particular issue has come up before, so it's
possible there's already a fix in SVN.  You didn't mention what version
you're compiling, so there might even be a fix in a released version.

	-brian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDk5pA6XyW6VEeAnsRAkw2AJ9dCmhbBZ6Jop9BYYuQB3zvG8JpHQCgxxRC
etI01FhZk9iGNWv+GgJhkh4=
=22DD
-----END PGP SIGNATURE-----



More information about the Xfce4-dev mailing list