Date: Sun, 16 Feb 2003 09:44:25 -0500 (EST) From: "James E. Flemer" <jflemer@acm.jhu.edu> To: Alex Kiesel <alex.kiesel@document-root.de> Cc: <freebsd-ports@freebsd.org> Subject: Re: Porting problem: right approach Message-ID: <Pine.LNX.4.33L2.0302160938490.22351-100000@centaur.acm.jhu.edu> In-Reply-To: <20030215160131.GA47084@schlund.de>
next in thread | previous in thread | raw e-mail | index | archive | help
I believe a libtool update is in progress. There are several unofficial libtool patch sets available too, including my own: http://www.cs.rpi.edu/~flemej/freebsd/libtool-upgrade/ I would suggest you wait for the "official" update to finish your port. If you are in a hurry, use an unofficial update, and hope the official one is similar enough to work with your php-gtk port. -James On Sat, 15 Feb 2003, Alex Kiesel wrote: > Hi, > > I'm currently trying to port php-gtk which has some problematic > build-dependencies: > > * automake 1.4 > * autoconf 2.13 > * libtool 1.4.2 > > (At least this combination is reported to work, see > http://gtk.php.net/manual/en/install.unix.php) > > However, any combination I tried did not lead to a stable port that > builds on any system. Sometimes I have been able to create a working > configure-script, but the port that did work fine on one host did fail > on another. > > I guess these problems are caused by the old libtool, so currently there > is no good way to solve this problem. I am thinking of taking the > configure-script and any created files from a host where the port > worked, ship it in an additional tgz and just extract that second tgz > before the configure-process. > > Would this be a good solution or would you say this is crap? > > Thanks for any advice and greets from Karlsruhe, > Alex > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.33L2.0302160938490.22351-100000>