[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 01/01: gnu: custom-gcc: Delete broken or conflicting executables.
From: |
Ludovic Courtès |
Subject: |
Re: 01/01: gnu: custom-gcc: Delete broken or conflicting executables. |
Date: |
Thu, 17 Mar 2016 22:51:33 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Ricardo Wurmus <address@hidden> skribis:
> Ricardo Wurmus <address@hidden> 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’.