From: SourceForge.net <no...@so...> - 2007-03-28 09:43:46
|
Bugs item #1688560, was opened at 2007-03-26 19:07 Message generated for change (Comment added) made by eriklns You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1688560&group_id=10894 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: 52. Configuration and Build Tools Group: current: 8.4.14 >Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: Erik Leunissen (eriklns) Assigned to: Jeffrey Hobbs (hobbs) Summary: ./configure chokes on variables passed on the command line Initial Comment: When passing variables to a configure script, like: ./configure RANLIB=target-ranlib RC=/some/place/windres CC=target-gcc AR=target-ar the following error is generated: configure: warning: RANLIB=target-ranlib: invalid host type configure: warning: RC=/some/place/windres: invalid host type configure: error: can only configure for one host and one target at a time Googling for the error message, made me believe that the autoconf version that produces the configure script may not be up to par. On the other hand it might be the case that autoconf is broken. Note aside: passing variables as arguments to ./configure is the explicitly recommended (in favor of setting the environment variables before invoking ./configure) as per: http://www.gnu.org/software/autoconf/manual/autoconf.html#Defining-Variables ---------------------------------------------------------------------- >Comment By: Erik Leunissen (eriklns) Date: 2007-03-28 11:43 Message: Logged In: YES user_id=113903 Originator: YES Oh, forgot to log in, when saying: "Indeed, it is 8.4.14" ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2007-03-28 11:41 Message: Logged In: NO Indeed, it is 8.4.14 ---------------------------------------------------------------------- Comment By: Donal K. Fellows (dkf) Date: 2007-03-28 11:02 Message: Logged In: YES user_id=79902 Originator: NO Is this an 8.4 build? If so, it's just a limitation of autoconf 2.13 which is the version used for 8.4 (and before) for historical reasons, and won't be fixed. If it is for 8.5 which used autoconf 2.57 (or is it 2.59?) there's a problem that needs to be fixed. But you indicate that 2.57 works, so I suspect it isn't 8.5... ---------------------------------------------------------------------- Comment By: Erik Leunissen (eriklns) Date: 2007-03-26 19:35 Message: Logged In: YES user_id=113903 Originator: YES After having produced a configure script from the distribution supplied configure.in, with my autoconf version 2.57, the error went away. This confirms the suspicion against the autoconf version with which configure script are produced. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1688560&group_id=10894 |