all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: custom-gcc: Delete broken or conflicting executables.
Date: Thu, 17 Mar 2016 22:51:33 +0100	[thread overview]
Message-ID: <874mc4pyca.fsf@gnu.org> (raw)
In-Reply-To: <idjvb4mtvkz.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Wed, 16 Mar 2016 14:13:00 +0100")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:

[...]

>> I’ll investigate this.  It’s odd that “-lgfortran” cannot be found only
>> because we deleted useless wrappers.
>
> I found that for randomjungle the native inputs must now also include
>
>     ("gfortran" ,gfortran "lib")
>
> in *addition* to the usual
>
>     ("gfortran" ,gfortran)
>
> I can prepare a patch for the three broken packages, but I wonder why
> this is necessary.  “gfortran” alone does not install “libgfortran.so”,
> only the “lib” output does.

For GCC we hack the “lib” spec (as show by ‘gcc -dumpspecs’) so that it
has an extra -L for libgcc_s (search for ‘GNU_USER_TARGET_LIB_SPEC’ in
gcc.scm).

Should something similar be done here?

Ludo’.

      reply	other threads:[~2016-03-17 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 13:14 01/01: gnu: custom-gcc: Delete broken or conflicting executables Efraim Flashner
2016-03-16 11:37 ` Ricardo Wurmus
2016-03-16 13:13   ` Ricardo Wurmus
2016-03-17 21:51     ` Ludovic Courtès [this message]

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=874mc4pyca.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.