[beports] Re: ./configure
- From: Andreas Färber <andreas.faerber@xxxxxx>
- To: beports@xxxxxxxxxxxxx
- Date: Thu, 1 May 2008 09:48:24 +0200
Hi,
Am 01.05.2008 um 00:33 schrieb scott mc:
In Haiku when I get a package that requires running ./configure it
usually bombs out not know how to handle Haiku. Are you guys seeing
this as well? And how are you getting around it?
That's what the --build=i586-pc-beos is for, as a workaround. That way
it thinks it is being configured under BeOS and usually knows how to
adapt.
http://tools.assembla.com/BePorts/wiki/PortingTips#gcc2.xdefault
The real solution is to replace config.guess, config.sub and ltmain.sh
with Haiku's local versions, which usually happens when you run the ./
autogen.sh (or ./auto_gen.sh or ./buildconf) script when working from
the original repository. Sometimes it may be necessary to remove them
first in order to be replaced. But after doing so, you may have to add
support for *-*-haiku* (or *-*-haiku) to the configure script first to
avoid -lm issues and the like.
Note, the Haiku-related changes in those files are preliminary by Ingo
and were asked not yet to be merged upstream.
Not sure how to handle this mid-term - we might opt to not include
these files in upstream patches (sometimes they are versioned,
sometimes not), but the changes necessary to configure.{in,ac} for
i586-pc-haiku are probably already mergeable, no? I'd assume an
expression like *-*-haiku* will hold.
Andreas
--
BePorts homepage - http://tools.assembla.com/BePorts
List archives: //www.freelists.org/archives/beports
Administrative contact: brecht@xxxxxxxxxxx
Other related posts:
