public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/13572] New: Inappropriate files installed in $(prefix)/share/make/
Date: Mon, 05 Jan 2004 16:22:00 -0000 [thread overview]
Message-ID: <20040105162145.13572.jsm28@gcc.gnu.org> (raw)
GCC 3.4 installs inappropriate files Makefile.generic and Makefile.prolog
in $(prefix)/share/make/.
(a) They need licence notices, not just copyright notices, as otherwise
they must be presumed undistributable and shouldn't be in GCC at all.
(b) They get installed in $(prefix)/share/make. There are two problems
with this. First, the names of the files and the directory are rather
too generic for that; $(prefix)/share/gnat or $(prefix)/share/ada might be
better to make clear where they come from. Second, --datadir is a
supported configure option, so $(datadir) should be used instead of
$(prefix)/share. (File with such generic names should only go in
$(datadir)/make if they really were generic files from GNU make
rather than some other package; otherwise any number of packages might
equally well try to claim those names.)
--
Summary: Inappropriate files installed in $(prefix)/share/make/
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsm28 at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13572
next reply other threads:[~2004-01-05 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 16:22 jsm28 at gcc dot gnu dot org [this message]
2004-01-05 17:29 ` [Bug ada/13572] " pinskia at gcc dot gnu dot org
2004-01-07 11:48 ` charlet at gcc dot gnu dot org
2004-01-12 11:36 ` cvs-commit at gcc dot gnu dot org
2004-01-12 11:47 ` charlet at gcc dot gnu dot org
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=20040105162145.13572.jsm28@gcc.gnu.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).