public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* other/7957: change request: more flexible %D specs directive
@ 2002-09-17 18:26 bh
  0 siblings, 0 replies; only message in thread
From: bh @ 2002-09-17 18:26 UTC (permalink / raw)
  To: gcc-gnats


>Number:         7957
>Category:       other
>Synopsis:       change request: more flexible %D specs directive
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 17 18:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Benoit Hudson
>Release:        gcc 3.2
>Organization:
>Environment:

>Description:
The %D directive currently prints out all the -L options you need in order to link (modulo bug 6668).  My users want not to need to know where g++ is.  The best way I can think of doing that is by adding -R options (or -rpath on linux).  I can do this in two ways:
(a) g++ is a script that adds -R if needed and then feeds to the real g++ (making sure only to add it when I'm linking to avoid spurious warnings)
(b) munge the specs

Setting their LD_LIBRARY_PATH is not an option.

I'd rather (b) to skip the logic of am-I-linking.  For that, it's not terribly hard to add the appropriate stuff to *libgcc ; but a %D analogue that outputs the appropriate -R or -rpath switches would make it easier yet.  Perhaps call it %DR, or %R, or whatever fits best.

Next step would be to add the configury to make it even cleaner: --with-rpath-in-specs or somesuch builds the specs as I would hand-code them automatically.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-09-18  1:26 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-09-17 18:26 other/7957: change request: more flexible %D specs directive bh

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).