[MacPorts] #15838: gcc34 build fails on Mac OS X 10.5.4 intel
MacPorts
noreply at macports.org
Mon Jul 7 16:37:50 PDT 2008
#15838: gcc34 build fails on Mac OS X 10.5.4 intel
------------------------------------+---------------------------------------
Reporter: shirose at jamstec.go.jp | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: new
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.6.0
Resolution: | Keywords:
------------------------------------+---------------------------------------
Changes (by raimue at macports.org):
* cc: raimue at macports.org (added)
Comment:
Replying to [comment:5 ryandesign at macports.org]:
> Replying to [comment:4 raimue at macports.org]:
> > As gcc34 does not compile on Tiger or Leopard, we should think about
removing the port.
>
> Removing the gcc34 port? There are still 10 ports that declare
dependencies on it. Those dependencies should be changed first before we
consider removing gcc34.
Right, I was taking this as an implied requirement :-)
{{{
$ port echo depends:gcc34
algae
mipsel-linux-uclib
p5-extutils-f77
pgplot
py-scipy03
mercury
}}}
(depends: is a trunk feature)
As 'port depends' uses the PortIndex only, this does not take variants
into account.
But most of them listed only need g77, which could be used from gcc4x as
well. Also, most of them don't have a maintainer.
{{{
$ port info --name --depends --maintainer depends:gcc34
}}}
shows details (again, trunk only).
Currently these ports are not usable without a working gcc34 build. So
either we need to fix gcc34 or we have to investigate the dependencies of
these ports, switch them to another compiler version or if there is no
other possibility remove them, too.
--
Ticket URL: <http://trac.macports.org/ticket/15838#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list