URL: <https://savannah.gnu.org/support/?111158>
Summary: 'make check' fails on older Mac, especially when
building fat binaries
Group: GNU Libtool
Submitter: None
Submitted: Tue 03 Dec 2024 07:15:19 AM UTC
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email: gstee...@gmail.com
Open/Closed: Open
Discussion Lock: Any
Operating System: Mac OS
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Tue 03 Dec 2024 07:15:19 AM UTC By: Anonymous
I'm using a Power Mac G5 with Mac OS 10.5.8 (Darwin 9.8). My package manager
massages the build environment a bit to ensure consistent behaviour. Part of
that involves ensuring that compiler runs always get "-arch xxxx" flags
inserted when a 64-bit or universal binary is being built (an absolute
requirement, because otherwise extension modules and test programs do not
necessarily get built with the same architecture as the rest of the package,
which causes immediate failure when (for example) a 64-bit program tries to
link to a 32-bit plug-in bundle, or the like). In this environment, libtool's
test suite exhibits three incorrect failures and one incorrect skip. I
believe that three of the four would still occur without it.
Test 95, for localization, artificially fails because it does not know to
ignore the additional error message from the 'lipo' tool that follows the
expected compiler error.
Test 119, with the enforced library prefix, fails because the linker refuses
to link an extension bundle (Mach filetype MH_BUNDLE) to a dynamic library
(Mach filetype MH_DYLIB). I have yet to determine whether this is due to the
somewhat outdated native linker, or to a formal policy inherent to Mac OS.
Test 161, the Darwin fat compile, is incorrectly skipped. As far as I can
tell this is gated by a very straightforward test for the string 'darwin'
appearing in the OS name (which it does, according to the logs), so how it is
deciding to skip that is a mystery to me.
Test 172, which repeats a large subset of the entire test suite with a shorter
maximum command line length, incorrectly reports failure when the only failed
tests are the same ones that failed at normal line lengths. If nothing
changed, this should not be reporting a failure.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111158>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
