rl
5.33.3 (which included 0.2311).
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
to a lesser extent to --std=c99 or --std=c11.
--
Russ Allbery (ea...@eyrie.org) <http://www.eyrie.org/~eagle/>
Peter Rosin writes:
> On 2013-06-01 08:09, Russ Allbery wrote:
>> Peter Rosin writes:
>>> On 2013-06-01 00:06, Russ Allbery wrote:
>>>> Autoconf doesn't work with MSVC directly so far as I know. All of
>>>> the packages I have that are ported to
Peter Rosin writes:
> On 2013-06-01 00:06, Russ Allbery wrote:
>> Autoconf doesn't work with MSVC directly so far as I know. All of the
>> packages I have that are ported to MSVC have a separate hand-written
>> config.h that's used for MSVC builds, and in that fi
define it under those circumstances. Or
> have I misunderstood something?
Autoconf doesn't work with MSVC directly so far as I know. All of the
packages I have that are ported to MSVC have a separate hand-written
config.h that's used for MSVC builds, and in that file one simply doesn
e my concern.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
hat the standard Autoconf header probes do.
This behavior is not currently clearly documented, but I will point out
that the current documentation of AC_INCLUDES_DEFAULT shows use of the
HAVE_STRINGS_H define without any mention of any other required checks.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
actually enforce that and do not prototype
those functions in string.h. I'm quite sure there is code out there that
assumes that Autoconf will probe for strings.h as a side effect of other
probes and set HAVE_STRINGS_H, and therefore doesn't probe for it
explicitly. (I maintain some of
AFS) retrofitting shared
library support onto an old (20+ years in this case) code base with its
own extremely complex build system.
--
Russ Allbery (r...@stanford.edu) <http://www.eyrie.org/~eagle/>
rgument form to open a file with arbitrary weird
characters in it,
open(FOO, '<', $file);
otherwise it's necessary to protect any leading and trailing
whitespace:
$file =~ s#^(\s)#./$1#;
open(FOO, &q
se days.
When using the two-argument form, files with leading or trailing
whitespace will still cause you problems even with an explicit mode
character always prepended.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
This is a horrible idea. Please do not cripple the compiler on projects
that use Autoconf because some people write code that makes assumptions it
shouldn't. This would be like automatically adding -fpermissive to
CXXFLAGS or adding -fno-strict-aliasing to CFLAGS, and just as wrong.
--
is was a GCC macro (I think that's where it started),
because it's expressing trinary information.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Patrick Welche <[EMAIL PROTECTED]> writes:
> On Thu, Jul 20, 2006 at 07:03:27PM -0700, Russ Allbery wrote:
>> Adding -R for system X libraries is always the wrong thing to do on
>> Debian systems and will break multiarch builds. I really don't think
>> this is
ystem X libraries is always the wrong thing to do on Debian
systems and will break multiarch builds. I really don't think this is the
right solution.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
15 matches
Mail list logo
