| To work around intractable problems like that, perhaps you could use
| code that looks like this:
|
|ifdef([m4_ifdef], [
| echo autoconf 2.50 or newer
|], [
| echo autoconf 2.13 or older
|])
|
| (I was a bit surprised that this worked -- isn't 2.5x supposed to
| rename `
> Date: Wed, 25 Jul 2001 02:10:19 +0200
> From: Ralf Corsepius <[EMAIL PROTECTED]>
>
> For me, it is subdir handling in autoconf-2.5x.
I don't use that, so I had no problem. :-)
> A further problem is some of the new autoconf-features apparently
> being immature and autoconf-2.5x (in most case
Paul Eggert wrote:
>
> > From: Lars Hecking <[EMAIL PROTECTED]>
> > Date: Tue, 24 Jul 2001 19:36:00 +0100
> >
> > Some hints on how to have configure.in compatible with both versions
> > would be more than welcome.
>
> The most important bit of advice is to stick only to 2.13-style
> features,
> From: Lars Hecking <[EMAIL PROTECTED]>
> Date: Tue, 24 Jul 2001 19:36:00 +0100
>
> Some hints on how to have configure.in compatible with both versions
> would be more than welcome.
The most important bit of advice is to stick only to 2.13-style
features, and to avoid 2.13's bugs. (That la
Akim Demaille wrote:
> >> We are very happy to announce yet another release of
> >> Autoconf,
> Martin> I have a little problem with this new autoconf. A few
...
> Martin> The big problem is that autoconf 2.52 and 2.1x are not
> Martin> compatible.
> I can understand they fear the amount of work,
> Could you please be more specific here? Perhaps we can suggest ways
> for you to make the changes so that they'll work with both 2.13 and 2.52.
Some hints on how to have configure.in compatible with both versions
would be more than welcome.
One problem now is that 2.5x creates configure
> > "Martin" == Martin Baulig <[EMAIL PROTECTED]> writes:
>
> Martin> Everything works just fine there except that I
> Martin> needed to make changes which won't work with autoconf 2.1x
> Martin> anymore.
Could you please be more specific here? Perhaps we can suggest ways
for you to make the
ScanMail for Microsoft Exchange has detected virus-infected attachment(s).
Sender = [EMAIL PROTECTED]
Recipient(s) = [EMAIL PROTECTED]
Subject = Soumission comparative 12 postes
Scanning Time = 07/24/2001 17:00:28
Action on virus found:
The attachment Soumission comparative 12 postes.xls.pif mat
This is an automated message sent from the Antigen Virus Protection for
Microsoft Exchange Mail @ The School of Business - University of Otago
=
An email intended for you had an attached file, Soumission comparative 12
postes.xls.pif and the
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> I've searched for a macro that simply dumps a message to
Lars> config.log without dumping anything to the console, but I
Lars> couldn't find any. I could of course use AS_CONFIG_LOG_FD and
Lars> echo, but a standard macro would be bett
Guido:
This is an Autoconf problem with a macro called by libtool.
Try getting today's CVS versions of Autoconf, Automake and Libtool
to see if it is resolved.
Robert
Guido Draheim wrote:
>
> [autoconf-2.52,automake-1.4f,libtool-1.4b]
>
> checking build system type... sparc-sun-solaris2.6
> c
I've searched for a macro that simply dumps a message to config.log
without dumping anything to the console, but I couldn't find any.
I could of course use AS_CONFIG_LOG_FD and echo, but a standard macro
would be better. config.log doesn't always automatically contain all
the essential informatio
> "Andreas" == Andreas Buening <[EMAIL PROTECTED]> writes:
Andreas> Hello!
Hi!
Please, don't write to people personally (but I understand why you did).
Andreas> I've seen that you've updated autoconf. I'd like to know why
Andreas> you haven't applied the two patches I've suggested to get
> "Martin" == Martin Baulig <[EMAIL PROTECTED]> writes:
Please, don't write to individuals.
Martin> Akim Demaille <[EMAIL PROTECTED]> writes:
>> We are very happy to announce yet another release of Autoconf,
Martin> Hi,
Martin> I have a little problem with this new autoconf. A few weeks
M
[autoconf-2.52,automake-1.4f,libtool-1.4b]
checking build system type... sparc-sun-solaris2.6
checking host system type... sparc-sun-solaris2.6
checking target system type... sparc-sun-solaris2.6
[...]
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C
Hello,
I recently found something that looks like a bug to me.
While checkin the functionality of the CC on Solaris the
script quits with an error:
checking whether the C++ compiler (CC -s) works... no
configure: error: installation or configuration problem: C++
compiler cannot create executable
16 matches
Mail list logo
