Re: AC_F77_NAME_MANGLING question

On 3-Jul-2000, Akim Demaille <[EMAIL PROTECTED]> wrote: | Below we have a question regarding AC_F77_NAME_MANGLING, which, I | think, you wrote. I don't think I wrote that, or any of the other f77 support for autoconf, though I believe that the f77 support for autoconf is based on the macros tha

Re: making pre-build headers

On 31-Oct-2000, Bruce Korb <[EMAIL PROTECTED]> wrote: | It is ugly. Especially | when the automated dependencies come along and decide | that your objects depend on mumble.h and mumble.h depends | on your sources and you modified your sources, so it | must be time to regenerate the mumble.h and

Re: Portability of fopen (foo, "wb") (Was: bug in AC_COMPUTE_INT)

On 16-Nov-2000, Earnie Boyd <[EMAIL PROTECTED]> wrote: | --- Akim Demaille <[EMAIL PROTECTED]> wrote: | | > Does anybody know whether using fopen (foo, "wb") is portable? Gary | > uses a test for this, but I don't know if it's really needed. A grep | > on the packages I have at hand show this:

Re: macro doc inconsistencies

On 22-Apr-2001, Lars J. Aas <[EMAIL PROTECTED]> wrote: | I was thinking of using texinfo markup directly in the doc macro. HTML | and other formats should come from the texinfo output. I don't see this | part as an obstacle - the problem is more on the management-side - getting | the doc parts

Re: Fortran name-mangling scheme fails on HP-UX 11.11

On 28-Jun-2001, Steven G. Johnson <[EMAIL PROTECTED]> wrote: | On Thu, 28 Jun 2001, Denis Barbier wrote: | > But there is no reason for AC_F77_WRAPPERS to require | > AC_F77_LIBRARY_LDFLAGS; in _AC_F77_NAME_MANGLING one may simply (well, | > i have no idea whether this is simple or not) link agai

Re: GAFCOM CONCERNS

On 23-Jul-2001, Pavel Roskin <[EMAIL PROTECTED]> wrote: | > This virus crap is getting rather irritating. If you are going to use | > email with Win, get an antivirus program, or disconnect. | | Please don't copy your replies to the list. Nobody here wants except the | original "poster" deserve

Re: [f77] Disable C comments in config.h

On 5-Sep-2001, Akim Demaille <[EMAIL PROTECTED]> wrote: | > "Denis" == Denis Barbier <[EMAIL PROTECTED]> writes: | | Denis> On Mon, Sep 03, 2001 at 09:55:34AM +0200, Akim Demaille wrote: | Denis> [...] Hi, AIX Fortran compiler dislikes C comments in | Denis> config.h; it would be nice to h

Re: autoconf, Fortran, LAPACK, and AC_SEARCH_LIBS

On 24-Mar-2009, David A. Ventimiglia wrote: | I think I solved one of my problems. Evidently, there's an Autoconf | macro AC_LANG. By adding AC_LANG(Fortran) to my configure.ac file, it | ensures that test programs are written in Fortran rather than in C, and | that seems sufficient to find sget

autoconf in pure MSVC environment?

On 6-Sep-2004, Brandon J. Van Every <[EMAIL PROTECTED]> wrote: | How do I set up autoconf on Windows *without* any Cygwin or Mingw | compilers or header files? I only want a native MSVC environment, with | typical mainstream Windows SDKs. I don't want any UNIX environment at | all, except what

Re: autoconf in pure MSVC environment?

On 7-Sep-2004, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: | Installing Cygwin is similar in magnitude to installing another | operating system. The last time I installed it, I just did a point and click "Next -> Next -> Next -> Finish" kind of install. It took a while because I was downloading

Re: autoconf in pure MSVC environment?

On 7-Sep-2004, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: | Yet this DLL accesses a "root" filesystem containing /etc/passwd, | /etc/group, /etc/fstab, terminfo, etc.. Windows filesystems are | "mounted". This smells like an "OS" install to me, even if it is | subordinate to another. The ty

Re: autoconf in pure MSVC environment?

On 7-Sep-2004, Bob Friesenhahn <[EMAIL PROTECTED]> wrote: | Programs linked with | the Cygwin DLL "mount" the Windows filesystems using different paths | (e.g. "/cygdrive/c") My recollection is that an application can be written to mostly not care whether the filenames are specified with Wind

RE: autoconf in pure MSVC environment?

On 7-Sep-2004, Brandon J. Van Every <[EMAIL PROTECTED]> wrote: | In a UNIX universe, particularly a Linux universe, libraries are nicely | packaged up and play well together. These same UNIX libraries are never | packaged up well on Windows, so the build environment can almost never | be duplica

RE: autoconf in pure MSVC environment?

On 7-Sep-2004, Brandon J. Van Every <[EMAIL PROTECTED]> wrote: | I love it when open source guys throw the 'volunteering' word around. | It's very macho, like volunteerism is the only determinant of project | success. At the start of his message, Bruce Korb also wrote | > Please explain to me c

warning from AC_LANG_PROGRAM(Fortran 77)

I'm using Autoconf 2.59: devzero:450> autoconf --version autoconf (GNU Autoconf) 2.59 Written by David J. MacKenzie and Akim Demaille. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILIT

dispatching

On 14-Feb-2005, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: | I'd like to know whether the following scenario is possible with | Autoconf: | | Somewhere early during ./configure, the host type is checked. If it is | GNU (Hurd), an ordinary build is prepared. (Checking libs, using | automake-gene

warning from AC_LANG_PROGRAM(Fortran 77)

es my head spin. Can someone who knows more about m4 and autoconf please take a look and see if there is a better solution? Thanks, jwe ChangeLog: 2005-03-02 John W. Eaton <[EMAIL PROTECTED]> * lib/autoconf/fortran.m4 (AC_LANG_PROGRAM(Fortran 77)): Don&#x

Re: RFE: configure -> dependency list on exit.

On 4-Mar-2005, Stepan Kasal <[EMAIL PROTECTED]> wrote: | My idea was to have AC_MSG_NEED with args |(@var{dependency-name}, @var{dependency-text}, @ovar{priority}) | used like | | AC_MSG_NEED([flex], | [Get the latest version of lex from ftp://ftp.gnu.org/gnu/flex/.]) | | Which would disp

Re: warning from AC_LANG_PROGRAM(Fortran 77)

On 2-Mar-2005, Stepan Kasal <[EMAIL PROTECTED]> wrote: | The root of all evil is the obsolete AC_TRY_LINK macro. | Use the newer macros, which don't double-quote: | | AC_LINK_IFELSE([AC_LANG_PROGRAM([], [])], | [ACTION-IF-TRUE], [ACTION-IF-FALSE]) Yes, this works. But in the docum

Re: RFE: configure -> dependency list on exit.

On 4-Mar-2005, Hugh Sasse Staff Elec Eng <[EMAIL PROTECTED]> wrote: | > it from their package system) or you have to embed this knowledge in | > autoconf, which seems bad and would only work for a few tools in | | So where does it go, then? People have said not to put it in a text | file, becau

Re: warning from AC_LANG_PROGRAM(Fortran 77)

On 7-Mar-2005, Stepan Kasal <[EMAIL PROTECTED]> wrote: | On Fri, Mar 04, 2005 at 11:24:45AM -0500, John W. Eaton wrote: | > Same as `AC_LINK_IFELSE([AC_LANG_PROGRAM([[INCLUDES]], | > [[FUNCTION-BODY]])], [ACTION-IF-TRUE], [ACTION-IF-FALSE])' (*note | >

question about whether to set CFLAGS in configure.ac

On 29-Nov-2005, Ed Hartnett wrote: | I believe the common consensus is that one should not set CFLAGS in | configure.ac. | | However, I have a problem that seems to call for it. Is there a better | way to get this working then messing with CFLAGS? | | My configure allows the user to specify a lo

unexpected editing of argument to AH_BOTTOM

I'm using autoconf 2.60a. Given the following configure script, AC_INIT AC_CONFIG_HEADER(config.h) AH_BOTTOM([ #define FOO #if defined (__LOSER_SYSTEM__) #undef FOO #endif ]) AC_OUTPUT running autoheader autoconf ./configure produces the following config.h file: /* c

Re: unexpected editing of argument to AH_BOTTOM

On 13-Oct-2006, Stepan Kasal wrote: | +Please note that @var{text} gets included ``verbatim'' to the template file, | +not to the resulting config header, so it can easily get mangled when the | +template is processed. There is rarely a need for something else than | + | [EMAIL PROTECTED] | +AH_B

Re: Binary Version for Mac OS X?

On 21-Jun-2007, Bob Friesenhahn wrote: | You are correct that a strict interpretation of GPL v2 does not allow | GPLed software to be installed using anything other than an an | open-sourced installation program which is itself licenced for | re-distribution under a no more restrictive license

probing for compiler attributes?

On 7-Aug-2007, Joshua Hoblitt wrote: | Is there a pre-canned AC macro or other reliable means of testing for | compiler attributes? | | I have an awful lot of code that looks something like this: | | void *myfunc(char *myvar | #ifdef __GNUC__ | ) __attribute__((malloc)); |

Re: pthreads

On 30-Jan-2008, Stefan Bienert wrote: | now I got a last question to put the whole licensing-issue to an end. | If we use the autoconf stuff, with macros and all, internaly for the | development process (access to this resource only via private accounts) | but only include the configure script a

Re: Checking g77 or gfortan calling convention for c++

On 11-Mar-2008, Ralf Wildenhues wrote: | I see two possibilities: First, try matching declarations: compile a | code snippet that includes the library header, then re-declare the | function using each way in turn. The matching one will not trigger a | conflicting declaration error. Typically the

Re: just one of a million reasons why autoconf is a worthless piece of shit (2)

On 17-Mar-2008, Keith Marshall wrote: | I've recently ported Andries Brouwer's, (now Federico Lucifredi's), | variant of John Eaton's man program, for use with MSYS, under | MS-Windows. That package came with a hand crafted configure script, | which "wasn't worth the effort of autoconfiscating

Re: Re: configure.ac, Makefile.am question

On 21-Aug-2008, [EMAIL PROTECTED] wrote: | >From the very beginning, lies my intention in this point: As there are | features to correct and implement, I do not want to have any extra | headaches from the svn users like "Oh, i can't `make install` it here" | and then i have to troubleshoot that al

Re: 'fc' program and autoconf

On 17-Aug-2002, Paul Eggert <[EMAIL PROTECTED]> wrote: | > Date: Sat, 17 Aug 2002 21:12:33 -0400 (EDT) | > From: "Steven G. Johnson" <[EMAIL PROTECTED]> | | > > Thanks for the suggestion. I think the fc Fortran compiler is long | > > dead, so I installed this patch. | > | > Perhaps I spoke too

cross compiling -- building programs to run on build system

What is the right way to use autoconf to determine the compiler and system characteristics for tools that are written in C and must be run as part of a larger build that is cross compiled? For example, Octave has some programs that are written in C++ that are compiled and run during the build pro

Re: Fortran 9x: time for a decision

On 28-Oct-2002, Kate Hedstrom <[EMAIL PROTECTED]> wrote: | I would imagine that the people who refuse to update their | Fortran to compile under f90 are the ones who will never take up | autotools anyway. Some of us are using autoconf with mixed-language projects that include Fortran code that we

Re: 1,000 year backward compatability of tools

On 19-Feb-2003, Bruce Korb <[EMAIL PROTECTED]> wrote: | Paul Eggert wrote: | > | > Personally I'm becoming more inclined to start using shell functions. | > Perhaps in Autoconf 3. | | If my memory serves, GCC has finally said, "Enough with K&R already!" | but everyone is still saying, "You first

Re: Using AC_C_INLINE blows up C++ tests

On Tue, Jul 01, 2003 at 09:56:59AM -0700, Paul Eggert wrote: > That patch (archived in > ) > assumes that 'inline' always works with every C++ compiler. Is this > assumption correct? I think it should be. I don't have my copy of t

Fortran vs. OS X

tion of start in section (__TEXT,__text) /usr/lib/crt1.o definition of start in section (__TEXT,__text) configure:5929: $? = 1 The problem seems to be that gcc adds -lcrt1.o to the link command and listing it a second time causes the above errors. The following patch avoids the problem: 2003-07-25

Re: Autoconf on new platforms

On 19-Jul-2003, Paul Eggert <[EMAIL PROTECTED]> wrote: | The easiest way for you to get this to work, is to tell users to | create a POSIX-like environment where programs can create executables | in the traditional way. I suppose you could port Autoconf to the | non-POSIX environment you're talki

Re: Get rid of `-g' in CXXFLAGS

On 1-Aug-2003, Frank A. Uepping <[EMAIL PROTECTED]> wrote: | I want CXXFLAGS without the -g flag BY DEFAULT! | Because the normal user doesn't want a bloat bin with debug information. Perhaps not, but as the maintainer of a package with the occasional bug, it is annoying when someone reports a p

Re: GNU ftp crack and config.{sub,guess}

EMAIL PROTECTED]> (reason: 550 Message contains Sobig.F. Denied.) ... From: "John W. Eaton" <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Date: Sat, 23 Aug 2003 09:28:26 -0500 To: [EMAIL PROTECTED] Cc: Ben Elliston <[EMAIL PROTECTED]>, [EMAIL PRO

Re: GNU ftp crack and config.{sub,guess}

On 4-Sep-2003, Paul Smith <[EMAIL PROTECTED]> wrote: | It's not so clear how to wget their contents from Savannah. Try wget --output-file config.guess 'http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess?rev=HEAD&content-type=text/plain' wget --output-file config