From: Mark Klein <mklein@dis.com>
To: gas2@cygnus.com, egcs@cygnus.com
Subject: egcs/ltconfig
Date: Sun, 13 Sep 1998 12:50:00 -0000 [thread overview]
Message-ID: <3.0.3.32.19980913125037.009b9840@garfield.dis.com> (raw)
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.
next reply other threads:[~1998-09-13 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-13 12:50 Mark Klein [this message]
1998-09-13 15:24 ` egcs/ltconfig Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.3.32.19980913125037.009b9840@garfield.dis.com \
--to=mklein@dis.com \
--cc=egcs@cygnus.com \
--cc=gas2@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).