From: Randy Geyer <randy.geyer@gmail.com>
To: libffi-discuss@sourceware.org
Subject: How to force the AIX build to output libffi.a instead of libffi.so?
Date: Tue, 8 Dec 2020 08:09:49 -0800 [thread overview]
Message-ID: <CAKmEa0pGQ3-qRJLx8u-cjwOiAovDORBXqUnvcCXqSGMGsZcZeg@mail.gmail.com> (raw)
We are attempting to upgrade libffi from 3.2.1 to 3.3. In all our past
installs we have been able to control the output name by modifying
configure to set shrext_cmds=.a under the aix[4-9]* specs:
aix[4-9]*)
version_type=linux # correct to gnu/linux during the next big refactor
shrext_cmds=.a
need_lib_prefix=no
This setting no longer seems to succeed in controlling the output name.
next reply other threads:[~2020-12-08 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 16:09 Randy Geyer [this message]
2020-12-08 17:35 ` Anthony Green
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=CAKmEa0pGQ3-qRJLx8u-cjwOiAovDORBXqUnvcCXqSGMGsZcZeg@mail.gmail.com \
--to=randy.geyer@gmail.com \
--cc=libffi-discuss@sourceware.org \
/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).