[MacPorts] #16009: arts-1.1.2: patch failure: KDE requires autoconf 2.52, 2.53 or 2.54
MacPorts
noreply at macports.org
Thu Jan 22 14:01:45 PST 2009
#16009: arts-1.1.2: patch failure: KDE requires autoconf 2.52, 2.53 or 2.54
--------------------------------+-------------------------------------------
Reporter: zweistein12@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.6.0
Keywords: | Port: arts
--------------------------------+-------------------------------------------
Comment(by dr2chase@…):
MORE:
First, I have no idea how to undo the steps I am about to suggest. So
maybe you don't want to do them, or maybe you want to do some more
research. It says this software is unmaintained, maybe I am volunteering.
To workaround this bug, download arts, and as root (sudo bash)
{{{
cd /opt/local/var/macports/distfiles/arts
mkdir safe
cp *.bz2 safe
mkdir work
cp *.bz2 work
cd work
bunzip2 *.bz2
for i in *.tar ; do
tar xf $i
end
}}}
You then need to edit both copies of cvs.sh, fixing the lines for
autoconf, autoheader, and automake,
more or less like so:
{{{
Autoconf*2.5* | autoconf*2.5* | Autoconf*2.6* | autoconf*2.6* ) : ;;
Autoconf*2.5* | autoheader*2.5* | Autoconf*2.6* | autoheader*2.6* ) :
;;
automake*1.5* | automake*1.5-* | automake*1.6.* | automake*1.7* |
automake*1.8* | automake*1.9* | automake*1.10* | automake*1.11* ) : ;;
}}}
This is not a robust fix, but it will get you to the next step.
Retar and re-bzip2 the files:
{{{
tar cvf arts-1.1.2.tar arts-1.1.2
tar cf kde-admindir-20030601.tar admin
bzip2 *.tar
cp *.bz2 ..
}}}
Attempt to install (it will fail):
{{{
sudo port install -v arts
}}}
The output will whine about a checksum.
At this point, you need to go find the portfile
(/opt/local/var/macports/sources/rsync.macports.org/release/ports/audio/arts/Portfile)
and edit it to put in the "correct" checksums for the files you just
mutilated.
This is still not enough. When you build, it while fail because it passes
an invalid warning flag to the C++ compiler (if either party had been
willing to let the warning slide, either not to ask for it, or merely to
warn on an inappropriate warning flag, which by definition is not going to
affect the output, this would work, but such is not the case). I edited
all those out (there's 14 of them) from every file that set it.
This will get you to the NEXT failure, which is
{{{
buffer.h:102: error: extra ';'
}}}
and that is in fact the case.
I've spent enough time on this for one day.
--
Ticket URL: <http://trac.macports.org/ticket/16009#comment:6>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list