On 2023-12-02 19:29, Zack Weinberg wrote:
`grep -q` *is* in POSIX, but I seem to recall tripping over a
system that didn't have it (probably either a Solaris successor, or AIX)
during the run-up to Autoconf 2.71.
Solaris 10 /usr/bin/grep does not support -e, -E, -f, -F, -q, or -x.
Solaris 10
Mike Frysinger wrote:
On 02 Dec 2023 17:07, Jacob Bachmeyer wrote:
Mike Frysinger wrote:
On 06 Apr 2023 21:29, Jacob Bachmeyer wrote:
Karl Berry wrote:
jb> a more thorough test would locate the autom4te script and grep it
for the perllibdir that was
On 12 Apr 2023 18:14, Reuben Thomas via Bug reports for Automake wrote:
> On Wed, 12 Apr 2023 at 17:59, Reuben Thomas wrote:
> > On Wed, 12 Apr 2023 at 16:17, Reuben Thomas wrote:
> >
> >> I am bootstrapping GNU a2ps git master[1] with automake 1.16.5. When I do
> >> a parallel build (in my
On Sat, Dec 2, 2023, at 8:58 PM, Jacob Bachmeyer wrote:
> Zack Weinberg wrote:
>> Either way is no problem from my end, but it would be more work
>> for automake (parsing --version output, instead of just checking the
>> exit status of autom4te --assert-high-resolution-timestamp-support)
>> Karl,
On Sat, Dec 2, 2023, at 9:08 PM, Mike Frysinger wrote:
> On 02 Dec 2023 15:53, Karl Berry wrote:
>> Exit status yes, but at least historically, grep -q has been
>> considered non-portable, in favor of grep ... >/dev/null.
>
> i get that `grep -q` is something historically we've avoided, but i
>
On 30 Nov 2023 22:45, Nick Bowler wrote:
> Interestingly the libtool manual also says "If [libtool] can't infer a
> tag, then it defaults to the configuration for the C language", which is
> clearly not the case (it seems what actually happens is that if libtool
> can't infer a tag then it
On 02 Dec 2023 15:53, Karl Berry wrote:
> also, can we really not trust the exit status of grep ?
> if echo "$PERL" | grep -q '[\t ]'; then
>
> Exit status yes, but at least historically, grep -q has been considered
> non-portable, in favor of grep ... >/dev/null.
i get that
On 27 Nov 2023 14:35, Karl Berry wrote:
> https://savannah.gnu.org/patch/?10417
>
> Unfortunately, last I heard, the new libtool maintainer was AWOL and no
> one is left actively maintaining it. Or even looking for a maintainer. A
> sad state of affairs :(. --best, karl.
i've always been
Zack Weinberg wrote:
On Sat, Dec 2, 2023, at 7:33 PM, Jacob Bachmeyer wrote:
Zack Weinberg wrote:
Would it help if we added a command line option to autom4te that made
it report whether it thought it could use high resolution timestamps?
Versions of autom4te that didn't recognize this
On 02 Dec 2023 17:07, Jacob Bachmeyer wrote:
> Mike Frysinger wrote:
> > On 06 Apr 2023 21:29, Jacob Bachmeyer wrote:
> >> Karl Berry wrote:
> >>> jb> a more thorough test would locate the autom4te script and grep it
> >>> for the perllibdir that was substituted when autoconf was
> >>>
On 02 Dec 2023 18:33, Jacob Bachmeyer wrote:
> Zack Weinberg wrote:
> > On Sat, Dec 2, 2023, at 6:37 PM, Karl Berry wrote:
> >> The best way to check if high-resolution
> >> timestamps are available to autom4te is to have perl load
> >> Autom4te::FileUtils and check if that also loaded
On 02 Dec 2023 19:17, Zack Weinberg wrote:
> On Sat, Dec 2, 2023, at 6:37 PM, Karl Berry wrote:
> > The best way to check if high-resolution
> > timestamps are available to autom4te is to have perl load
> > Autom4te::FileUtils and check if that also loaded Time::HiRes.
> >
> > The
On Sat, Dec 2, 2023, at 7:33 PM, Jacob Bachmeyer wrote:
> Zack Weinberg wrote:
>> Would it help if we added a command line option to autom4te that made
>> it report whether it thought it could use high resolution timestamps?
>> Versions of autom4te that didn't recognize this option should be
>>
On 02 Dec 2023 15:09, Karl Berry wrote:
> very extensive "Portable Shell Programming" chapter:
>
> https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/html_node/Portable-Shell.html
>
> I know. The Autoconf manual already describes this issue in detail.
> The point of
Zack Weinberg wrote:
On Sat, Dec 2, 2023, at 6:37 PM, Karl Berry wrote:
The best way to check if high-resolution
timestamps are available to autom4te is to have perl load
Autom4te::FileUtils and check if that also loaded Time::HiRes.
The problem with that turned out to be that
On Sat, Dec 2, 2023, at 6:37 PM, Karl Berry wrote:
> The best way to check if high-resolution
> timestamps are available to autom4te is to have perl load
> Autom4te::FileUtils and check if that also loaded Time::HiRes.
>
> The problem with that turned out to be that Time::HiRes got
The best way to check if high-resolution
timestamps are available to autom4te is to have perl load
Autom4te::FileUtils and check if that also loaded Time::HiRes.
The problem with that turned out to be that Time::HiRes got loaded from
other system modules, resulting in the test
Mike Frysinger wrote:
On 06 Apr 2023 21:29, Jacob Bachmeyer wrote:
Karl Berry wrote:
jb> a more thorough test would locate the autom4te script and grep it
for the perllibdir that was substituted when autoconf was
configured.
I guess that would work.
Challenge
(Trying to switch to add to
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64756.)
this doesn't work on systems that wrap `autom4te`.
Had no idea anyone did that.
grep: /Autom4te/FileUtils.pm: No such file or directory
Oops.
seems like the only reliable option is to invoke
echo "$PERL" | grep '[ \t]'
I don't think there's any portable way to use \t to insert a tab in a
shell string, besides literally. There's something like
tab=`printf '\t'`
.. "$tab" ...
but I don't see a need to go that far here. I just used a literal tab char.
also, can we really
very extensive "Portable Shell Programming" chapter:
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/html_node/Portable-Shell.html
I know. The Autoconf manual already describes this issue in detail.
The point of the brief mention in the Automake manual is because
However it looks like there is no tag defined for Objective C[1]
(presumably it would be --tag=OBJC). Adding this option does appear
to make things "work" in the sense that libtool just complains about
the unknown tag but then proceeds to actually do stuff, rather than
exiting
On Sat, Dec 2, 2023, at 6:58 AM, Mike Frysinger wrote:
> On 06 Apr 2023 21:29, Jacob Bachmeyer wrote:
>> Karl Berry wrote:
>> > jb> a more thorough test would locate the autom4te script and grep it
>> > for the perllibdir that was substituted when autoconf was
>> > configured.
>> >
>>
On 06 Apr 2023 21:29, Jacob Bachmeyer wrote:
> Karl Berry wrote:
> > jb> a more thorough test would locate the autom4te script and grep it
> > for the perllibdir that was substituted when autoconf was
> > configured.
> >
> > I guess that would work.
>
> Challenge accepted. Here's a
On 27 May 2023 19:12, Karl Berry wrote:
> I (finally) installed this patch to quit early if the perl path has
> spaces. Thanks.
>
> As for MKDIR_P and INSTALL, I guess it is somewhere in the
> prerequisite/autoconf stuff. I suppose it would be rare that they would
> be found in a path with spaces
On 18 Nov 2023 19:27, Karl Berry wrote:
> Hi Michael,
>
>
> Date: Sun, 16 Oct 2016 18:35:53 +0200
> From: Michael Stapelberg
> To: automake-patches@gnu.org
> Subject: [PATCH] texinfo: add pointer about combining tests
>
>
27 matches
Mail list logo