* How to force the AIX build to output libffi.a instead of libffi.so?
@ 2020-12-08 16:09 Randy Geyer
2020-12-08 17:35 ` Anthony Green
0 siblings, 1 reply; 2+ messages in thread
From: Randy Geyer @ 2020-12-08 16:09 UTC (permalink / raw)
To: libffi-discuss
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: How to force the AIX build to output libffi.a instead of libffi.so?
2020-12-08 16:09 How to force the AIX build to output libffi.a instead of libffi.so? Randy Geyer
@ 2020-12-08 17:35 ` Anthony Green
0 siblings, 0 replies; 2+ messages in thread
From: Anthony Green @ 2020-12-08 17:35 UTC (permalink / raw)
To: Randy Geyer; +Cc: libffi-discuss
Are you trying to build a statically linked library? Why not configure
with --disable-shared?
AG
On Tue, Dec 8, 2020 at 11:10 AM Randy Geyer via Libffi-discuss <
libffi-discuss@sourceware.org> wrote:
> 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.
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-12-08 17:35 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-08 16:09 How to force the AIX build to output libffi.a instead of libffi.so? Randy Geyer
2020-12-08 17:35 ` Anthony Green
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).