On Thu, 18 Oct 2012, Marcin Cieslak wrote:
> On Wed, 17 Oct 2012, je...@jellehermsen.nl wrote:
>
>> Sorry for breaking this one. It didn't strike me as an issue because
>> the va_copy macro is defined in C99 and has been supported by GCC for
>> quite a while, so I thought we could easily rely on that one instead
>> of using the GNU extension __va_copy. We could also add an #ifdef for
>> __va_copy as a more granular solution.
>
> I think we should go for some HaveVaCopy solution - GCC 4.2.1
> for FreeBSD has va_copy for amd64, but not for i386 in the
> FreeBSD release series < 10.x
>
Possibly...
Actually, I'm thinking maybe we use an autoconf (configure) run as
part of the make includes phase. It's sole job would be to detect
various things about the system (like availablility of va_copy, tirpc,
sys_errlist/errno, installed locales, etc) and create a
cdehostconfig.h file (and maybe a makefile that could be included in
other makefiles).
I am not proposing converting to autoconf completely, but rather
having one run as part of the make includes phase (in config/) that
could determine stuff like this at build time. I did this for an
imake based project once before (NAS) and it worked well for figuring
out stuff like this.
Could solve a lot of these types of problems...
--
Jon Trulson
"Oh the land of the free, and the home of the brave.
Are you heaven on Earth, or the gloom of the grave."
-- Iron Sky
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
