Hi!
For various reasons I want to override the decision autoconf
makes regarding LN_S. It it set to "ln -s" on my system which
is perfectly fine in every normal case. But in my abnormal case
I want it to be "cp -p". What can I do? I also want this to
propagate to recursive autoconf invocations, so
Den 2010-09-02 21:32 skrev Ralf Wildenhues:
> Hi Peter,
>
> * Peter Rosin wrote on Thu, Sep 02, 2010 at 09:18:29PM CEST:
>> For various reasons I want to override the decision autoconf
>> makes regarding LN_S. It it set to "ln -s" on my system which
>> is per
Den 2010-09-02 21:45 skrev Peter Rosin:
> Den 2010-09-02 21:32 skrev Ralf Wildenhues:
>> Hi Peter,
>>
>> * Peter Rosin wrote on Thu, Sep 02, 2010 at 09:18:29PM CEST:
>>> For various reasons I want to override the decision autoconf
>>> makes regarding LN_S.
Hi Steffen!
Den 2010-09-02 21:50 skrev Steffen Dettmer:
> On Thu, Sep 2, 2010 at 9:18 PM, Peter Rosin wrote:
>> (background: I want to have Libtool on Cygwin drive MSVC, and
>> Cygwin creates soft links that MSVC does not understand. The
>> Libtool testsuite invokes
Den 2010-09-03 11:47 skrev Steffen Dettmer:
> On Fri, Sep 3, 2010 at 8:18 AM, Peter Rosin wrote:
>> Den 2010-09-02 21:50 skrev Steffen Dettmer:
>>> On Thu, Sep 2, 2010 at 9:18 PM, Peter Rosin wrote:
> [cp instead of ln -s]
>>>
>>> couldn't this bre
un([_AS_LN_S_PREPARE],
-[rm -f conf$$ conf$$.exe conf$$.file
+[if test -z "$LN_S"; then
+ rm -f conf$$ conf$$.exe conf$$.file
if test -d conf$$.dir; then
rm -f conf$$.dir/conf$$.file
else
@@ -1208,6 +1209,9 @@ else
fi
rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.fil
Den 2010-10-16 10:39 skrev Ralf Wildenhues:
> Hello Václav,
>
> * Václav Haisman wrote on Fri, Oct 15, 2010 at 08:56:51PM CEST:
>> I am having difficulty testing for compiler features like
>> __declspec(dllimport) and switches like -Wall or -Werror.
>>
>> The problem has started like this. I wante
Den 2010-11-02 06:46 skrev Ralf Wildenhues:
> Except then you may run into MSVC which prints its command-line options
> (dunno whether on stdout or stderr) ...
To expand on that tangent...
MSVC "only" prints the options it ends up feeding to link.exe (or maybe
it's link.exe that prints them?) and
Den 2010-11-02 08:18 skrev Miles Bader:
> On Tue, Nov 2, 2010 at 4:04 PM, Peter Rosin wrote:
>> Den 2010-11-02 06:46 skrev Ralf Wildenhues:
>>> Except then you may run into MSVC which prints its command-line options
>>> (dunno whether on stdout or stderr) ...
>
Den 2010-11-02 20:15 skrev Ralf Wildenhues:
> Hello Peter, Miles,
>
> * Miles Bader wrote on Tue, Nov 02, 2010 at 08:18:24AM CET:
>> On Tue, Nov 2, 2010 at 4:04 PM, Peter Rosin wrote:
>>> Den 2010-11-02 06:46 skrev Ralf Wildenhues:
>>>> Except then you may ru
Den 2011-02-07 09:14 skrev Ralf Corsepius:
> Provided how HW has developed since the discussions from 10 years
> ago, you cited about, I am actually leaning towards proposing the
> converse of your proposal: Autoconf toconsider to abandoning
> config.cache.
No, it still needs to be optional. Not
Den 2011-02-07 11:12 skrev Ralf Corsepius:
> On 02/07/2011 10:02 AM, Peter Rosin wrote:
>> Den 2011-02-07 09:14 skrev Ralf Corsepius:
>>> Provided how HW has developed since the discussions from 10 years
>>> ago, you cited about, I am actually leaning towards proposi
Den 2011-02-09 05:42 skrev Miles Bader:
> On Wed, Feb 9, 2011 at 4:39 AM, Ralf Corsepius wrote:
>>> At the least, constructs like
>>> AC_CHECK_HEADERS([stdint.h unistd.h fcntl.h sys/mman.h sys/stat.h])
>>> could check all the entries in parallel.
>>
>> Only simple scenarios, in which headers and h
Den 2011-02-09 10:55 skrev Miles Bader:
> Peter Rosin writes:
>>> [I meant, all the entries _within a single invocation_ (of
>>> AC_CHECK_HEADERS, etc) could be checked in parallel...]
>>
>> Yes, in a perfect world. If you e.g. do this:
>>
>> AC_CHE
Den 2011-07-31 01:57 skrev NightStrike:
> On Sat, Jul 30, 2011 at 3:26 PM, Gary V. Vaughan wrote:
>> On 31 Jul 2011, at 02:04, NightStrike wrote:
*snip*
>>> Consider, though, using cl.exe in an msys environment. That uses /
>>> instead of - for switches, for instance.
>>
>>
>> I would be quite
Werner LEMBERG skrev 2011-12-07 21:08:
>>> I still don't understand the details of the autoconf problem (and I
>>> still think that something is fishy), but defining this macro works
>>> just fine :-)
>>
>> Clearly, depending on an implementation-dependent macro is not
>> suitable for portable soft
Werner LEMBERG skrev 2012-02-03 10:45:
>
>>> is there an autoconf macro to detect MS Windows?
>>
>> Is that a joke? The trouble is, that autoconf requires a shell and
>> M4, which Windows doesn't provide (only in Cygwin). So MS Windows is
>> detected when autoconf/configure does not run...
>
> V
Eric Blake skrev 2012-02-23 23:42:
> On 02/23/2012 02:48 PM, Stefano Lattarini wrote:
>> * lib/Makefile.am (installcheck-local): To verify that the installed
>> scripts are actually executable, simply use 'test -x', instead of
>> resorting to perl and its '-x' file operator. Today, 'test -x'
>> sh
Eric Blake skrev 2012-02-27 14:58:
> On 02/26/2012 03:14 PM, Peter Rosin wrote:
>
>> Sorry for the late reply, but this might be relevant. Personally, I wouldn't
>> classify the below as a working "test -x", but I'm not sure what working is
>> in
&
On 2012-08-16 22:17, Eric Blake wrote:
> On 08/16/2012 02:04 PM, Javier Jardón wrote:
>> Hello,
>>
>> Im working on port GNOME moduels to use autoreconf instead our own
>> tool, gnome-autogen [1] (they do almost the same, but gnome-autogen
>> was created before autoreconf exist)
>
> A bit of rese
On 2013-03-15 05:05, Russ Allbery wrote:
> Zack Weinberg writes:
>
>> I think we should try to come up with a principled cutoff for how old is
>> too old, though. I started this thinking POSIX.1-2001 (including XSI,
>> but maybe not any other options) was a reasonable place to draw the
>> line, b
On 2013-03-15 21:18, Zack Weinberg wrote:
> On 2013-03-15 9:14 AM, Peter Rosin wrote:
>
>> I just wanted to chime in with the fact that it's working just fine to
>> use one of said UNIX-like portability environments and have Autoconf
>> probe MSVC directly.
>
&g
[Technically this is a Libtool question, but I'll answer here anyway]
On 2014-01-08 07:58, Harlan Stenn wrote:
> I need configure to tell me if I can use --no-as-needed or --as-needed.
>
> Right now we have been only using these flags if we're using GCC, and
> I've got a case (solaris) where gcc
On 2018-08-20 16:11, Sébastien Hinderer wrote:
> Dear all,
>
> I am writing an autoconf script for a project which is supposed to
> compile under both Unix and Windows.
>
> Under Windows, the project will be built under Cygwin but it should be
> possible to use both MingW and cl.exe to compile it
On 2016-01-22 12:33, Marko Lindqvist wrote:
> When building a project on MSYS2 environment, my configure fails to
> find out that the winsock2.h is available there.
> Simple AC_CHECK_HEADER() for winsock2.h fails, and so would many
> standard macros if it was to be included. The reason for that f
25 matches
Mail list logo
