public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/108462] duplicate install of static libraries
Date: Thu, 19 Jan 2023 15:01:52 +0000	[thread overview]
Message-ID: <bug-108462-4-ugcRIlZ2cz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108462-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108462

--- Comment #2 from Gaius Mulley <gaius at gcc dot gnu.org> ---
There should be archives in the different architecture directories as per
normal.  Accompanying these should be the library module source SYSTEM.def
(which could vary depending upon architectural characteristics).
The remaining sources are copies from the source tree.
It certainly looks as if the source files in ../13.0.1 are unnecessary given
the driver search path uses:

   -I ... 13.0.1/m2/m2pim    -L ... 13.0.1/m2/m2pim

I think the static archives and sources in 13.0.1 could be removed.

  parent reply	other threads:[~2023-01-19 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 10:41 [Bug modula2/108462] New: " rguenth at gcc dot gnu.org
2023-01-19 14:26 ` [Bug modula2/108462] " gaius at gcc dot gnu.org
2023-01-19 15:01 ` gaius at gcc dot gnu.org [this message]
2023-01-20 14:55 ` gaius at gcc dot gnu.org
2023-01-23  9:47 ` rguenth at gcc dot gnu.org
2023-01-23 10:08 ` rguenth at gcc dot gnu.org
2023-01-31 14:55 ` cvs-commit at gcc dot gnu.org
2023-01-31 14:56 ` rguenth at gcc dot gnu.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=bug-108462-4-ugcRIlZ2cz@http.gcc.gnu.org/bugzilla/ \
    --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).