The port graphics/aqsis contains multiple build errors. The first one is an internal compiler error -- it can be solved by compiling with GCC 3.2 (other versions may work too, but I tried this one). Then it complained about a missing reference to pthread_mutex_init and pthread_mutex_destroy. To solve this, add -pthread to the failing compiler command line. I tried to patch the Makefiles, but since I'm a novice, I managed to screw it up even more. There were other errors (one being a complaint about a missing Automake) but they seemed to be transient, as they went away when I added -v to the make command line. Fix: Compile with GCC 3.2 and add -pthread to the first failing compiler command line (see description above). How-To-Repeat: Build the port graphics/aqsis.
Responsible Changed From-To: freebsd-ports-bugs->vs Take. I think I've got it, it's a libtool-issue after all.
State Changed From-To: open->patched I just committed a fix for this. Could you please try the updated port and report if the resulting binary behaves as expected?
Am 09. Aug 2004 um 17:20 CEST schrieb Daniela: > Now it wants to build version 0.6.6, but I have 0.9.1. I think that Makefile > is out of date. Hm, how did you update the Ports Collection? Everything's okay there: http://www.freshports.org/graphics/aqsis Did you use cvsup? -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME L-Attriwutgrammatik
Now it wants to build version 0.6.6, but I have 0.9.1. I think that Makefile is out of date. The error message is: ===> Patching for aqsis-0.6.6 ===> Applying FreeBSD patches for aqsis-0.6.6 Ignoring previously applied (or reversed) patch. 1 out of 1 hunks ignored--saving rejects to aqsis/aqsis.cpp.rej >> Patch patch-aqsis.cpp failed to apply cleanly. *** Error code 1 Stop in /usr/ports/graphics/aqsis.
On Monday 09 August 2004 15:45, Volker Stolz wrote: > Am 09. Aug 2004 um 17:20 CEST schrieb Daniela: > > Now it wants to build version 0.6.6, but I have 0.9.1. I think that > > Makefile is out of date. > > Hm, how did you update the Ports Collection? Everything's okay there: > http://www.freshports.org/graphics/aqsis > > Did you use cvsup? No, I used sysinstall. I didn't know that sysinstall screws it up. I'll try cvsup.
On Mon, Aug 09, 2004 at 06:00:18PM +0000, Daniela wrote: > No, I used sysinstall. I didn't know that sysinstall screws it up. > I'll try cvsup. sysinstall didn't screw up, but (usually) installs the snapshot of the release it was shipped with, so you probably wound up with a 3-6 month outdated Ports Collection ;) If you have something better than the average modem, you should use cvsup regularly for updating. Volker -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME L-Attriwutgrammatik
On Tuesday 10 August 2004 07:12, Volker Stolz wrote: > On Mon, Aug 09, 2004 at 06:00:18PM +0000, Daniela wrote: > > No, I used sysinstall. I didn't know that sysinstall screws it up. > > I'll try cvsup. > > sysinstall didn't screw up, but (usually) installs the snapshot of the > release it was shipped with, so you probably wound up with a 3-6 month > outdated Ports Collection ;) If you have something better than the average > modem, you should use cvsup regularly for updating. Everything OK. No errors this time.
State Changed From-To: patched->closed I believe this is settled. Thanks for your submission!