On 14 Jan 2023 01:30, Nick Bowler wrote:
> On 2023-01-13, Mike Frysinger wrote:
> > On 13 Jan 2023 16:01, Karl Berry wrote:
> >> I am doubtful about blithely defining .POSIX unconditionally. I feel
> >> sure that will break existing Makefiles. I don't think we should do that.
> >>
> >> Detecting
On 2023-01-13, Mike Frysinger wrote:
> On 13 Jan 2023 16:01, Karl Berry wrote:
>> I am doubtful about blithely defining .POSIX unconditionally. I feel
>> sure that will break existing Makefiles. I don't think we should do that.
>>
>> Detecting .POSIX in an existing Makefile.am and moving it to
On 13 Jan 2023 13:52, Tim Ruffing wrote:
> On Fri, 2023-01-13 at 05:52 +, Mike Frysinger wrote:
> > i think the expectation is that, if you're using libtool, then you
> > use libtool.
>
> Well, I *use* libtool. libtool needs some AR. I choose to use
> libtool.exe with the ar-lib wrapper.
On 13 Jan 2023 16:01, Karl Berry wrote:
> I am doubtful about blithely defining .POSIX unconditionally. I feel
> sure that will break existing Makefiles. I don't think we should do that.
>
> Detecting .POSIX in an existing Makefile.am and moving it to the front
> sounds desirable, since that is
I am doubtful about blithely defining .POSIX unconditionally. I feel
sure that will break existing Makefiles. I don't think we should do that.
Detecting .POSIX in an existing Makefile.am and moving it to the front
sounds desirable, since that is clearly what the developer intended.
Another (not
On Fri, 2023-01-13 at 05:52 +, Mike Frysinger wrote:
> i think the expectation is that, if you're using libtool, then you
> use libtool.
Well, I *use* libtool. libtool needs some AR. I choose to use
libtool.exe with the ar-lib wrapper.
On 2023-01-13 01:19:39 -0500, Mike Frysinger wrote:
> any reason we don't just define it ourselves unconditionally ? seems
> like the whole point of Automake is for devs to not worry about these
> kind of nitty details.
Probably. Note, however, that .POSIX affects GNU "make" on a few
points (the
> On 13 Jan 2023, at 08:43, Mike Frysinger wrote:
>
> On 13 Jan 2023 07:07, Sam James wrote:
>> $ /tmp/libaacs/configure YACC=bison LEX=flex
>
> the problem is you're forcing `YACC=bison`. Automake defaults to `bison -y`
> which tells bison to operate in POSIX-yacc-compatible mode because
On 13 Jan 2023 07:07, Sam James wrote:
> $ /tmp/libaacs/configure YACC=bison LEX=flex
the problem is you're forcing `YACC=bison`. Automake defaults to `bison -y`
which tells bison to operate in POSIX-yacc-compatible mode because Automake's
rules target POSIX. the end result is that you've
