* egcs/ltconfig
@ 1998-09-13 12:50 Mark Klein
1998-09-13 15:24 ` egcs/ltconfig Alexandre Oliva
0 siblings, 1 reply; 2+ messages in thread
From: Mark Klein @ 1998-09-13 12:50 UTC (permalink / raw)
To: gas2, egcs
Is this file generated or hand coded? (I see it uses ac_link which is why
I ask).
On MPE there is no such thing as static linking - the only way to tell that
a library routine doesn't exist is to attempt to compile and run something
that references it. This is further compounded by the fact that the parameters
must be correct or the program will still blow up. The approach I've taken is
to modify the m4 macros for autoconf specifically for MPE and always
regenerate
the configure scripts with my version of autoconf before running them. That
works fine. But, for ltconfig, I see no ltconfig.in, hence my question.
TIA,
Mark
--
Mark Klein DIS International, Ltd.
http://www.dis.com 415-892-8400
PGP Public Key Available Remove "nospam" to reply.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: egcs/ltconfig
1998-09-13 12:50 egcs/ltconfig Mark Klein
@ 1998-09-13 15:24 ` Alexandre Oliva
0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Oliva @ 1998-09-13 15:24 UTC (permalink / raw)
To: Mark Klein; +Cc: gas2, egcs
Mark Klein <mklein@dis.com> writes:
> Is this file generated or hand coded?
It is generated from ltconfig.in, distributed with GNU libtool. But
the `generation' of it just takes care of version and line numbers, so
it is quite safe to modify it. Anyway, you should report a problem to
bug-libtool@gnu.org, so we may try to fix this problem in the next
release of libtool. You may want to check whether its latest
snapshot, libtool-1.2b (available at ftp://alpha.gnu.org/gnu ), already
fixes this problem.
> The approach I've taken is to modify the m4 macros for autoconf
> specifically for MPE and always regenerate the configure scripts
> with my version of autoconf before running them. That works
> fine. But, for ltconfig, I see no ltconfig.in, hence my question.
It admittedly borrows a lot of code from autoconf 2.10... The fix
vshould be similar. Furthermore, now that autoconf is being actively
maintained again, you may be able to get your fixes into its next
distribution... Post your suggestions to configure@cygnus.com
libtool, OTOH, has got quite stale since Gordon Metzigkeit, its
original author, decided to stop maintenaning it. After some
arrangements, I agreed with him on starting a co-maintainership if he
could find some site to host a CVS repository with anonymous access.
Maybe Cygnus would be willing to donate some disk space and network
connection to the libtool project...
BTW, we're looking for more people to join the team, since both Gord
and I are busy people, and libtool is too important a project to be
maintained by two people that don't have much time to develop it :-(
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1998-09-13 15:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-09-13 12:50 egcs/ltconfig Mark Klein
1998-09-13 15:24 ` egcs/ltconfig Alexandre Oliva
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).