Open barracuda156 opened 2 months ago
A failure to detect the build triple/quadriple is not unique, here is the same error: https://trac.macports.org/ticket/70686 For it we just a need an upstreamed fix.
On Friday September 06 2024 08:15:15 Sergey Fedorov wrote:
Here it is stuck. Using
autoreconf
does not help, it still ends up with the same error.
This is a new variant of a known problem, no?
Can you confirm that the libtool in $worksrcpath is indeed created from the host libtool? I think I've been stymied by this kind of problem before, and I cannot remember ever having figured out how to fix it other than by using autoreconf (or not using autoreconf). I still have my /usr/bin/libtool so my solution apparently was never to dunk or replace it.
On Friday September 06 2024 10:17:43 Sergey Fedorov wrote:
A failure to detect the build triple/quadriple is not unique, here is the same error: https://trac.macports.org/ticket/70686
I'll be curious to see how that ticket is handled on trac! It's for Linux, shock, horror! ;)
First attempt of the build (as-is) fails on:
Adding the following to portfile
allows the build to proceed, but then it fails on:
Here it is stuck. Using
autoreconf
does not help, it still ends up with the same error.