public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: ada/6637: Ada libraries should honour --enable-shared
Date: Sat, 11 May 2002 14:56:00 -0000 [thread overview]
Message-ID: <E176enX-0005JT-00@jsm28.trin.cam.ac.uk> (raw)
>Number: 6637
>Category: ada
>Synopsis: Ada libraries should honour --enable-shared
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat May 11 14:56:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Joseph S. Myers
>Release: 3.2 20020510 (experimental)
>Organization:
none
>Environment:
System: Linux digraph 2.2.20 #2 Sat Nov 10 16:44:22 UTC 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/mainline --disable-shared --enable-threads=posix --with-system-zlib
>Description:
As recently discussed on the gcc list, the Ada libraries do not honour
--enable-shared, instead using another (undocumented) mechanism to
build shared libraries.
They should honour --enable-shared, as other libraries do. They
should also honour --enable-shared=package, with an appropriate
package name (which should be listed in the --enable-shared
documentation), so that, as with other libraries, the use of shared
libraries for them can be controlled independently from that for other
libraries. The default for them should be documented there, and
should probably default to shared libraries being enabled, as with
most other language libraries. Shared libraries should be installed
in $(libdir). Any of the Ada programs that link against the libraries
should (in the installed versions) be linked against the shared
libraries.
When shared libraries are disabled, dead symlinks libgnarl.so and
libgnat.so should not be installed, although they are at present.
This is related to Zack's PR ada/5910 (that no separate "make
gnatlib_and_tools" should be needed); in both cases the normal
"configure" and "make bootstrap" interface to the build should be
followed, and additional user-visible complexity for Ada should be
avoided.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-05-11 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E176enX-0005JT-00@jsm28.trin.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc-gnats@gcc.gnu.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).