Is ./configure really portable?

Richard Garand richard at garandnet.net
Sat Jul 20 02:02:39 UTC 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On July 19, 2002 02:18 pm, Noa Cantin wrote:
> cd . && /bin/sh ./config.status Makefile
> config.status: error: invalid argument: Makefile
> gmake: *** [Makefile] Error 1
>
> Are these files supposed to be portable?

Actually, the default configure.in has problems. Find the line that says 
something like AC_CONFIG_FILES([ ./Makefile ]) and remove the ./. The problem 
is that something tells config.status to expect ./Makefile (probably the 
configure.in file) but the Makefile that runs config.status uses Makefile 
instead. Run gmake again after modifying configure.in and everything should 
work.
- -- 
Richard Garand   - r i c h a r d @ g a r a n d n e t . n e t
ICQ: 12190132 - http://www.garandnet.net
To the systems programmer, users and applications serve only to provide a test 
load.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9OMTDjuZKnjxs0fMRAviiAKDuUeuEl8NluYzndK7DIeY/dgZpIgCgtDQI
aiKuM2SOjn5KbZLI+IkF8f4=
=7vIi
-----END PGP SIGNATURE-----


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop mailing list