רҵάÐÞ£º¸÷Àà
¼¤¹â´òÓ¡»ú¡¢ÅçÄ«´òÓ¡»ú¡¢¸´Ó¡»ú¡¢´«Õæ»ú¡¢µçÄԵȰ칫É豸
ÁªÏµµç»°£º021-62653715
ÁªÏµÈË£ºÌÆÏÈÉú
=
¸ÃÓʼþʹÓà ¿ÆÌØÓʼþȺ·¢Èí¼þ ·¢ËÍ,ÓʼþÄÚÈÝÓë¿ÆÌØÈí¼þÎÞ¹Ø
¿ÆÌØÈí¼þ http://www.caretop.com
===
Les bons plans d'
Alexia
Bonjour à tous,
Vous voulez connaître tous
les bons plans, des promos, les produits les plus innovants en matière d'
Internet et applicatifs périphériques? Croyez-moi
I guess this is probably somewhat off-topic, but I'm hoping someone here
can point me in the right direction. I apologize in advance if this is
too off-topic - feel free to take the conversation off the list if need
be.
I have a function:
LogTrace(char *format, ...);
that is used for tracin
I did send an e-mail directly, and posted an answer publically to
news:comp.lang.c.moderated - it is really off-topic. cheers, guido
Es schrieb Kenneth Pronovici:
>
> I guess this is probably somewhat off-topic, but I'm hoping someone here
> can point me in the right direction. I apologize in
I've been using autoconf 2.5x for some time. Today I suddenly got the
error
configure.in:212: error: m4_popdef: undefined macro: AC_Dest
when running autoconf.
Heh. Got bit by the ol' you-can't-use-filenames-containing-dnl
issue again!
The problem was triggered by adding a line to configure.
Hi.
Is there macros for testing the existing of perl and the version ?
Is there macros to test the existence of perl modules like the one for
testing libs ?
Are this macros standard of autoconf or are extensions that we should add
to our project.
TIA.
Sergio Ferreira
Hi all,
I use autoconf for a software package. make dist is great for creating a
source tar ball. But we would also like to release precompiled binaries. The
package contains a lot of support files so we would like a to be able to use
the make install feature the copy the files.
I've tried
Sergio <[EMAIL PROTECTED]> writes:
> Is there macros for testing the existing of perl and the version ?
> Is there macros to test the existence of perl modules like the one for
> testing libs ?
I don't believe there are macros for either in the mainline autoconf, but
various people have written
David Richard Larochelle writes:
> I use autoconf for a software package. make dist is great for creating a
> source tar ball.
Autoconf is not involved in that. That's Automake.
> But we would also like to release precompiled binaries. The package
> contains a lot of support files so we woul
