#25907 closed defect (fixed)
libvpx 0.9.1 fails to build on Leopard
Reported by: | yaseppochi (Stephen J. Turnbull) | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | raimue (Rainer Müller), michaelld (Michael Dickens) | |
Port: | libvpx |
Description
This is a /different/ failure than that of #25815.
Apparently gcc-4.0 doesn't like -maltivec, but the configure script for the codecs puts it in the flags, resulting in "can't invoke compiler". I've reproduced the failure from the command line and verified that removing -maltivec from the command line allows gcc to execute. I haven't tried to modify configure.
Attaching main.log and config.err.
Attachments (3)
Change History (11)
Changed 14 years ago by yaseppochi (Stephen J. Turnbull)
Changed 14 years ago by yaseppochi (Stephen J. Turnbull)
Attachment: | config.err added |
---|
comment:1 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
comment:2 Changed 14 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Owner: | changed from macports-tickets@… to raimue@… |
---|
Changed 14 years ago by paulbeard@…
Attachment: | typescript-libvpx.gz added |
---|
typescript of libvpx building and installing, but w/o using port
comment:3 Changed 14 years ago by paulbeard@…
I got libvpx to configure, build and install on my ancient system [Darwin gee5.paulbeard.org 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC Power Macintosh]
But not w/in the port infrastructure. See the typescript attached.
comment:4 follow-up: 7 Changed 14 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | new → closed |
I have the same issue on 10.5 i386. The generic problem is that, by default, libvpx's 'configure' scripts will install as 'universal' no matter if in the Portfile +universal or "universal_variant no" is set. The particular manifestation is setting both -arch i386 and -arch ppc, as well as some conflicting flags which make GCC error out. The solution is to specify the exact "--target=FOO" to compile for, solely as a single architecture (no universal). I just checked in changes in r70235 that should fix this issue. Please "sync", "clean", and try again & report back. I'm closing this ticket, but please reopen if these changes don't work for you for this specific ticket's issue.
comment:7 Changed 14 years ago by yaseppochi (Stephen J. Turnbull)
Replying to michaelld@…:
Please "sync", "clean", and try again & report back.
I got a clean build and install, as you predicted. Dependencies are also upgrading properly.
Thanks!
comment:8 Changed 14 years ago by michaelld (Michael Dickens)
I'm glad to hear that it's working for for y'all (and, me too)! The upstream on this port has some work to do ...
On ppc without universal, it's enabling a bunch of i386 stuff including throwing -arch i386 into CFLAGS ... It's also trying to use the Leopard SDK rather than /