Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#59225 closed defect (fixed)

faac @1.29.9.2: Build failure on PowerPC due to calling in clang-9.0 as compiler

Reported by: SerpentChris (Chris Calderon) Owned by: jmroot (Joshua Root)
Priority: Normal Milestone:
Component: ports Version: 2.6.1
Keywords: Cc:
Port: faac

Description

Attempting to install faac (a dependency of MPlayer +mencoder_extras) on Mac OS X 10.5.8 fails with the following message:

--->  Computing dependencies for faac
Error: Cannot install clang-9.0 for the arch 'powerpc' because
Error: its dependency python27 does not build for the required arch by default
Error: and the configured universal_archs 'i386 ppc' are not sufficient.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port faac failed

Change History (7)

comment:1 Changed 5 years ago by SerpentChris (Chris Calderon)

Summary: faac @1.29.9.2 Build failure on PowerPC due to calling in clang-9.0 as compilerfaac @1.29.9.2: Build failure on PowerPC due to calling in clang-9.0 as compiler

comment:2 Changed 5 years ago by kencu (Ken)

this has been fixed in the latest commit to base master [42b36f4ae65e27b1824dd34c9fc23c022caa61e3/macports-base].

You can add it manually yourself, or install base from git master, or leave everything broken and wait for MacPorts 2.6.2...

More of us need to be involved in MacPorts base development!

comment:3 Changed 5 years ago by jmroot (Joshua Root)

Owner: set to jmroot
Resolution: fixed
Status: newclosed

In ca1d0a6870b7e22aa54f44c0bab4b2a870173db1/macports-ports (master):

faac: use macports-gcc on ppc

Fixes: #59225

comment:4 Changed 5 years ago by kencu (Ken)

Well, that's faac, but there are dozens and dozens of other ports that have blacklisted *gcc-3.* *gcc-4.*.

I know, because I blacklisted most of them.

comment:5 in reply to:  2 Changed 5 years ago by SerpentChris (Chris Calderon)

Replying to kencu:

this has been fixed in the latest commit to base master [42b36f4ae65e27b1824dd34c9fc23c022caa61e3/macports-base].

You can add it manually yourself, or install base from git master, or leave everything broken and wait for MacPorts 2.6.2...

More of us need to be involved in MacPorts base development!

Since I already have macports installed via the pkg installer, what is the best way for me to switch to the git version? Should I uninstall macports, along with all my installed ports, and then follow the normal instructions for installing from git, or is there a less painful way?

comment:6 Changed 5 years ago by kencu (Ken)

It takes only a few minutes, and you don't have to uninstall anything.

Clone the current base repo, and install from there, like this (from memory):

cd ~/Downloads
git clone https://github.com/macports/macports-base.git
cd macports-base
./configure && make && sudo make install
make clean

and you're on your way.

If you're using my /opt/bootstrap SSL enhancement method, don't forget to add those configure args. If you don't know what I'm talking about, that's a topic for another day.

comment:7 Changed 5 years ago by jmroot (Joshua Root)

In this case, it's probably easier to just apply that change to /opt/local/libexec/macports/lib/port1.0/portconfigure.tcl. That way you can still selfupdate when we release new versions, rather than being stuck on master until 2.7.0.

Note: See TracTickets for help on using tickets.