GNU bug report logs -
#74456
unactionable -no-install warnings on macos during 'make check'
Previous Next
Reported by: Simon Josefsson <simon <at> josefsson.org>
Date: Thu, 21 Nov 2024 08:19:01 UTC
Severity: normal
Done: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 74456 in the body.
You can then email your comments to 74456 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-libtool <at> gnu.org
:
bug#74456
; Package
libtool
.
(Thu, 21 Nov 2024 08:19:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Simon Josefsson <simon <at> josefsson.org>
:
New bug report received and forwarded. Copy sent to
bug-libtool <at> gnu.org
.
(Thu, 21 Nov 2024 08:19:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi
Gordon noticed that 'make check' in libidn prints warnings on macOS,
which are coming from libtool:
libtool: warning: '-no-install' is ignored for aarch64-apple-darwin23.6.0
libtool: warning: assuming '-no-fast-install' instead
https://lists.gnu.org/archive/html/help-libidn/2024-11/msg00006.html
https://gitlab.com/libidn/libidn/-/jobs/8321237800
I haven't analyzed the code in libtool behind the warning, but looking
at this from the outside, if some feature is known to not be supported
on some platform, it doesn't make a lot of sense to warn about that fact
on every compilation.
So two ideas:
1) Could we silence the warning generally?
or
2) Could we silence the warning on some set of architectures which is
known to not support this? And document that property.
or
3) Have a mechanism for maintainers to disable this warning?
Thanks,
/Simon
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-libtool <at> gnu.org
:
bug#74456
; Package
libtool
.
(Thu, 05 Dec 2024 17:58:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 74456 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 21/11/2024 10:18, Simon Josefsson via bug-libtool via Bug reports for
the GNU libtool shared library maintenance tool wrote:
> Hi
>
> Gordon noticed that 'make check' in libidn prints warnings on macOS,
> which are coming from libtool:
>
> libtool: warning: '-no-install' is ignored for aarch64-apple-darwin23.6.0
> libtool: warning: assuming '-no-fast-install' instead
>
> https://lists.gnu.org/archive/html/help-libidn/2024-11/msg00006.html
> https://gitlab.com/libidn/libidn/-/jobs/8321237800
>
> I haven't analyzed the code in libtool behind the warning, but looking
> at this from the outside, if some feature is known to not be supported
> on some platform, it doesn't make a lot of sense to warn about that fact
> on every compilation.
The warning messages for darwin have been present since this commit [1],
and for windows, it has been over two decades. I could remove the
warning message entirely. I think existing users should already be aware
of the warning, but I would like to avoid confusion with new users.
> So two ideas:
>
> 1) Could we silence the warning generally?
>
> or
>
> 2) Could we silence the warning on some set of architectures which is
> known to not support this? And document that property.
>
> or
>
> 3) Have a mechanism for maintainers to disable this warning?
Users can disable all libtool warnings with '--warnings=none' or
'--no-warnings', which I just realised the second is not documented in
the manual. libtool does not have warning categories (except 'all' and
'none'), so silencing the warning for some architectures by default
would mean just removing the existing warning messages for them.
I can update the documentation to reflect what the comments state and
remove the warning messages, but anything else would likely involve a
large rework to how libtool warnings operate.
[1]
https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=51f91963e600423f22d8c4ee01f2bf3a9e7a63bb
--
Ileana Dumitrescu
GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]
[OpenPGP_signature.asc (application/pgp-signature, attachment)]
Information forwarded
to
bug-libtool <at> gnu.org
:
bug#74456
; Package
libtool
.
(Thu, 05 Dec 2024 20:28:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 74456 <at> debbugs.gnu.org (full text, mbox):
I think it is the "unactionable" part that is the problem. OK, so there's a warning message. What is anyone supposed to do about it? There is no apparent source of the offending flag -- it just shows up when some packages use libtool, and there's absolutely nothing a person compiling such a package can do about it; they just have to sit through dozens or hundreds of repetitions of the exact same warning. (I personally have sometimes had such warnings cause my logs to balloon past the file rollover point!) Under these circumstances, the warning message is pointless, especially since the behaviour assumed instead does not seem to cause any obvious problems.
Gordon S.
> On Dec 5, 2024, at 9:56 AM, Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com> wrote:
>
> On 21/11/2024 10:18, Simon Josefsson via bug-libtool via Bug reports for the GNU libtool shared library maintenance tool wrote:
>> Hi
>> Gordon noticed that 'make check' in libidn prints warnings on macOS,
>> which are coming from libtool:
>> libtool: warning: '-no-install' is ignored for aarch64-apple-darwin23.6.0
>> libtool: warning: assuming '-no-fast-install' instead
>> https://lists.gnu.org/archive/html/help-libidn/2024-11/msg00006.html
>> https://gitlab.com/libidn/libidn/-/jobs/8321237800
>> I haven't analyzed the code in libtool behind the warning, but looking
>> at this from the outside, if some feature is known to not be supported
>> on some platform, it doesn't make a lot of sense to warn about that fact
>> on every compilation.
>
> The warning messages for darwin have been present since this commit [1],
> and for windows, it has been over two decades. I could remove the
> warning message entirely. I think existing users should already be aware
> of the warning, but I would like to avoid confusion with new users.
>
>> So two ideas:
>> 1) Could we silence the warning generally?
>> or
>> 2) Could we silence the warning on some set of architectures which is
>> known to not support this? And document that property.
>> or
>> 3) Have a mechanism for maintainers to disable this warning?
>
> Users can disable all libtool warnings with '--warnings=none' or
> '--no-warnings', which I just realised the second is not documented in
> the manual. libtool does not have warning categories (except 'all' and
> 'none'), so silencing the warning for some architectures by default
> would mean just removing the existing warning messages for them.
>
> I can update the documentation to reflect what the comments state and
> remove the warning messages, but anything else would likely involve a
> large rework to how libtool warnings operate.
>
> [1] https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=51f91963e600423f22d8c4ee01f2bf3a9e7a63bb
>
> --
> Ileana Dumitrescu
>
> GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
>
> <OpenPGP_0x6570EA01146F7354.asc>
Information forwarded
to
bug-libtool <at> gnu.org
:
bug#74456
; Package
libtool
.
(Mon, 09 Dec 2024 16:43:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 74456 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 05/12/2024 22:26, Gordon Steemson wrote:
> I think it is the "unactionable" part that is the problem. OK, so
> there's a warning message. What is anyone supposed to do about it?
> There is no apparent source of the offending flag -- it just shows
> up when some packages use libtool, and there's absolutely nothing a
> person compiling such a package can do about it; they just have to
> sit through dozens or hundreds of repetitions of the exact same
> warning. (I personally have sometimes had such warnings cause my
> logs to balloon past the file rollover point!) Under these
> circumstances, the warning message is pointless, especially since
> the behaviour assumed instead does not seem to cause any obvious
> problems.
Looking at the warning message, '-no-install' should not be passed
on for aarch64-apple-darwin23.6.0, so the action to take would be
removing the flag from the compilation. The warning message should
not be considered pointless because the flag is hard to find or
because no obvious problems have been observed.
Please look at my previous email for how to disable all libtool
warnings and for my suggested change to libtool to address these old
and hopefully well known warnings. I have applied this change to the
development branch [1].
[1]
https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=416ff25e14c900ba9cc220f1df0f2ee672cad4c9
--
Ileana Dumitrescu
GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]
[OpenPGP_signature.asc (application/pgp-signature, attachment)]
Reply sent
to
Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
:
You have taken responsibility.
(Thu, 13 Feb 2025 16:01:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Simon Josefsson <simon <at> josefsson.org>
:
bug acknowledged by developer.
(Thu, 13 Feb 2025 16:01:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 74456-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
These commits [1][2] have been applied to master which should resolve
this issue, so closing.
[1]
https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=e24d6ec92bcb95e15a75bb6a66067f4b4da05b58
[2]
https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=e66abb28cf2e6cf33b3a3243b5ec7d29f5b1ad51
--
Ileana Dumitrescu
GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]
[OpenPGP_signature.asc (application/pgp-signature, attachment)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 14 Mar 2025 11:24:12 GMT)
Full text and
rfc822 format available.
This bug report was last modified 99 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.