how to check type size

Hi, I need to check the size of some generic types, and if the size is unexpected, the configure script must raise a "configuration error". For example: if (sizeof(int) == 4) then [ok] else [error]; Is it possible to do that in autoconf 2.13 not writing a test? Thank you, Andrew Makhorin _

Re: how to check type size

Andrew Makhorin <[EMAIL PROTECTED]> writes: > I need to check the size of some generic types, and if the size is > unexpected, the configure script must raise a "configuration error". See AC_CHECK_SIZEOF. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfel

Re: how to check type size

>> I need to check the size of some generic types, and if the size is >> unexpected, the configure script must raise a "configuration error". > > See AC_CHECK_SIZEOF. Thank you for your response. However, AC_CHECK_SIZEOF does *not* that I need. It defines certain macros to be used later during c

why not check $PATH for m4?

Hi, I'm not subscribed, please reply-all. I installed m4-1.4.8 locally. However, in order for auto(re)conf find it, I have to do `export M4=$HOME/$MY_PREFIX/bin/m4' Otherwise, with an empty $M4, I get this error from /usr/bin/m4: /usr/bin/m4: `changeword' from frozen file not found in built

Re: why not check $PATH for m4?

Chris Pickett wrote: Hi, I'm not subscribed, please reply-all. I installed m4-1.4.8 locally. However, in order for auto(re)conf find it, I have to do `export M4=$HOME/$MY_PREFIX/bin/m4' Otherwise, with an empty $M4, I get this error from /usr/bin/m4: /usr/bin/m4: `changeword' from frozen f

Re: how to check type size

Andrew Makhorin <[EMAIL PROTECTED]> writes: > However, AC_CHECK_SIZEOF does *not* that I need. It defines certain > macros to be used later during compilation You can also use AC_COMPUTE_INT to set a shell variable. > while I want the configure script just to raise an error if some types > have

acincludedir -populating an m4/ subdirectory

It is great that aclocal/autoconf can now m4_include multiple files from a local m4/-subdirectory. Yet, I was missing a tool to populate it. A while back I just modified the standard aclocal to do that - i.e. instead of --ouput=FILE using an --output-dir=DIR. However, as far as I can see, the curre

macro_to_html + macro_to xml unix manpage

I have extracted some routines from the current AC-Archive website engine (implemented in Python) to work standalone on a single macro (or small number of macros if you like). Given a macro ax_example.m4 you can now say > ac_archive_macro_to_html ax_example.m4 which creates the output file ax_exam

Re: why not check $PATH for m4?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Chris Pickett on 2/2/2007 10:58 PM: > Hi, > > I'm not subscribed, please reply-all. > > I installed m4-1.4.8 locally. However, in order for auto(re)conf find > it, I have to do `export M4=$HOME/$MY_PREFIX/bin/m4' > > Otherwise, with an

Re: why not check $PATH for m4?

Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Chris Pickett on 2/2/2007 10:58 PM: Hi, I'm not subscribed, please reply-all. I installed m4-1.4.8 locally. However, in order for auto(re)conf find it, I have to do `export M4=$HOME/$MY_PREFIX/bin/m4' Otherwise, wi