Re: Problem Autotesting executables

2006-01-10 Thread Ralf Wildenhues
Hi Nathaniel, * Nathaniel D. Sizemore wrote on Tue, Jan 10, 2006 at 01:34:28AM CET: > I've a project using Autotest to, well, test executables. :-) My > testsuite.at file looks like the following: > > m4_define([AT_CHECK_FOO], [ > AT_SETUP() > AT_CHECK([foo], [], [stdout]) > AT_CLEANUP() > ])

Re: double underscores in autoconf-defined symbol names

2006-01-10 Thread Keith MARSHALL
Vadim Zeitlin wrote: > I'd like to know if there is any standard way of dealing with a > problem which arises when you use AC_CHECK_FUNCS with a function > whose name begins with an underscore (e.g. _snprintf) and then use > the result of the test in C++ code. To be precise, the problem is > that A

Re[2]: double underscores in autoconf-defined symbol names

2006-01-10 Thread Vadim Zeitlin
On Tue, 10 Jan 2006 10:02:47 + Keith MARSHALL <[EMAIL PROTECTED]> wrote: KM> From your example, it appears that you are searching for functions KM> using their "uglified" Microsoft names. It's not really uglified. Microsoft CRT is pretty consistent in prepending underscores to POSIX/Unix98/a

Re[2]: double underscores in autoconf-defined symbol names

2006-01-10 Thread Vadim Zeitlin
On Mon, 09 Jan 2006 14:14:11 -0800 Paul Eggert <[EMAIL PROTECTED]> wrote: PE> Vadim Zeitlin <[EMAIL PROTECTED]> writes: PE> PE> > 1. What do the others do? Just ignore this problem (hoping that HAVE__XXX PE> >is not really reserved) or is there something better? PE> PE> Yes, I think that's w

Re: double underscores in autoconf-defined symbol names

2006-01-10 Thread Thomas Dickey
On Tue, 10 Jan 2006, Keith MARSHALL wrote: Vadim Zeitlin wrote: From your example, it appears that you are searching for functions using their "uglified" Microsoft names. That may be true, but other platforms (including Linux) deal in ugly header file internals. The reason for it with Micro

Re: double underscores in autoconf-defined symbol names

2006-01-10 Thread Keith MARSHALL
Thomas Dickey wrote: > That may be true, but other platforms (including Linux) deal in ugly > header file internals. The reason for it with Microsoft is that the > names beginning with underscores don't match the behavior of the > similarly-named POSIX names. That may have been true, at one time

Re[2]: double underscores in autoconf-defined symbol names

2006-01-10 Thread Vadim Zeitlin
On Tue, 10 Jan 2006 15:44:41 + Keith MARSHALL <[EMAIL PROTECTED]> wrote: KM> Hmm. This trivial configure.ac: KM> KM> AC_INIT KM> AC_CHECK_FUNCS([snprintf _snprintf]) KM> AC_CONFIG_HEADERS([config.h]) KM> AC_OUTPUT KM> KM> results in a configure script which says "yes" for both snpri

Re: double underscores in autoconf-defined symbol names

2006-01-10 Thread Thomas Dickey
On Tue, 10 Jan 2006, Keith MARSHALL wrote: ...and unlike Microsoft's headers, MinGW's are not designed to be maintainable or readable - just random cut/paste excerpts from other headers. You are certainly entitled to this opinion, and I respect that, but I would also respectfully beg to differ

Re: double underscores in autoconf-defined symbol names

2006-01-10 Thread Keith MARSHALL
Vadim Zeitlin wrote: > I want configure to work with both mingw32 and cygwin and one of > them (I think it was cygwin but I'm not 100% sure; I can recheck > it though) has only _snprintf but not snprintf. Hmm. This trivial configure.ac: AC_INIT AC_CHECK_FUNCS([snprintf _snprintf]) AC_CONFI

Re: double underscores in autoconf-defined symbol names

2006-01-10 Thread Ralf Wildenhues
* Vadim Zeitlin In any case, I'd also like to be able to use MSVC cl.exe eventually (I > think it should be ok at autoconf level although it promises to be much > more interesting with libtool) FYI: Work underway in CVS HEAD Libtool: http://article.gmane.org/gmane.comp.gnu.libtool.patches/6489

Re: Problem Autotesting executables

2006-01-10 Thread Ralf Wildenhues
[ Cc:ed the list again ] Hi Nathaniel, * Nathaniel D. Sizemore wrote on Tue, Jan 10, 2006 at 06:48:16PM CET: > On Jan 10, 2006, at 2:07 AM, Ralf Wildenhues wrote: > > > >Show testsuite.log. Something else must be going on. > > See below. The executable formally known as 'foo' is vorpal -- >

Re: double underscores in autoconf-defined symbol names

2006-01-10 Thread Paul Eggert
Vadim Zeitlin <[EMAIL PROTECTED]> writes: > fact it's detected by an automatic precommit check in the project I'm > working on Well, to solve your immediate problem, it ought to be easy enough to exempt HAVE__* names from the precommit check. The precommit check ought to be your servant, not you

Do not name your AC_CONFIG_AUX_DIR `aux'

2006-01-10 Thread Brian
As I found out the hard way, `aux' is not portable to Cygwin, as it is a reserved folder name in Windows. You will not receive an explicit error. Instead your folder will simply be corrupted. The reason is that Windows won't let you directly create a folder named `aux', it will just revert immediat

hello world demo with gtk condition

2006-01-10 Thread Matt Hull
i am going to take a break from this i think. i have been reading examples manuals for at least 2 weeks on this. too much time. and i still can not get it to work. i put the lastest try at icarus.cc.uic.edu/~mhull1/mine-0.0.9.tar.gz i have automake version 1.4 - 1.9 installed. i was at first

Re: Do not name your AC_CONFIG_AUX_DIR `aux'

2006-01-10 Thread Ralf Wildenhues
Hi Brian, * Brian wrote on Wed, Jan 11, 2006 at 02:08:09AM CET: > As I found out the hard way, `aux' is not portable to Cygwin, as it is a > reserved folder name in Windows. You will not receive an explicit error. > Instead your folder will simply be corrupted. The reason is that Windows > won't l