unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Bruno Haible <bruno@clisp.org>, 41038@debbugs.gnu.org
Subject: bug#41038: gcc creates binaries that don't find their shared libraries
Date: Mon, 04 May 2020 21:52:49 +0200	[thread overview]
Message-ID: <87eerzqxym.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ1RMqGzv9bB_chOr+zCXLz3b8R1cUO-T-O9Ag5NAqBp4Q@mail.gmail.com> (zimoun's message of "Mon, 4 May 2020 11:59:47 +0200")

Hello,

zimoun <zimon.toutoune@gmail.com> skribis:

> Compiling Fortran leads to the same issue, if I understand correctly.
> Is it not the reason of the addition of 'gfortran-toolchain'?
> And I guess it should be the same issue for the other front-ends that
> GCC supports (Ada, etc.), isn't it?
>
> Well, is it not GCC related and not only C specific?
>
> I mean, I seems better to me to remove "@subsection The GCC toolchain"
> from "Application setup" and then to retitle the subsection "The GCC
> toolchain" in "Development" instead of "Packages for C Development".
> Keeping for now how it is worded and letting the GFortran use case as
> an exercise for the reader. ;-)

True!  Do you want to send a patch?  :-)

Thanks,
Ludo’.




  reply	other threads:[~2020-05-04 19:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 23:55 bug#41038: gcc creates binaries that don't find their shared libraries Bruno Haible
2020-05-03 21:07 ` Ludovic Courtès
2020-05-03 23:09   ` Bruno Haible
2020-05-04  8:50     ` zimoun
2020-05-04  9:06     ` zimoun
2020-05-04  9:30     ` Ludovic Courtès
2020-05-04  9:59       ` zimoun
2020-05-04 19:52         ` Ludovic Courtès [this message]
2020-05-06 17:42           ` bug#41038: [PATCH] doc: Reword "The GCC toolchain" zimoun
2020-05-15 16:59             ` zimoun
2020-05-15 19:42             ` Nicolas Goaziou
2020-05-16 14:57               ` zimoun
2020-05-16 15:19                 ` Ludovic Courtès
2020-05-03 22:12 ` bug#41038: gcc creates binaries that don't find their shared libraries Danny Milosavljevic
2020-05-05  9:30   ` Ludovic Courtès
2020-05-05 11:17     ` Bruno Haible

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eerzqxym.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41038@debbugs.gnu.org \
    --cc=bruno@clisp.org \
    --cc=zimon.toutoune@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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