GCC front-ends (was: GFortran can’t find system headers)

2013-10-19 Thread Nikita Karetnikov
I guess this triggers a complete rebuild, right? (That means it would go in ‘core-updates’.) Using the ‘substitute-keyword-arguments’ hack as in base.scm would allow you to avoid that. Also, the ‘origin’ thing should be factorized: (define (gcc-source version) (origin ...)) It’s

Re: GFortran can’t find system headers

2013-10-17 Thread Nikita Karetnikov
Instead, what should do is preserve the arguments; the value associated with #:configure-flags should be changed to replace any --enable-languages=.* flag with yours. See ‘gcc-boot0’ in base.scm for how to do that. Are you talking about the ‘substitute-keyword-arguments’ part? Alternately,

Re: GFortran can’t find system headers

2013-10-17 Thread Ludovic Courtès
Nikita Karetnikov nik...@karetnikov.org skribis: Instead, what should do is preserve the arguments; the value associated with #:configure-flags should be changed to replace any --enable-languages=.* flag with yours. See ‘gcc-boot0’ in base.scm for how to do that. Are you talking about the

Re: GFortran can’t find system headers

2013-10-15 Thread Ludovic Courtès
Nikita Karetnikov nik...@karetnikov.org skribis: I’m trying to package APL, which requires LAPACK, which requires Fortran. Cool. Here’s my attempt to add the last one: (define-public gfortran-4.8 (package (inherit gcc-4.8) (name gfortran) (arguments `(#:configure-flags

GFortran can’t find system headers

2013-10-14 Thread Nikita Karetnikov
I’m trying to package APL, which requires LAPACK, which requires Fortran. Here’s my attempt to add the last one: (define-public gfortran-4.8 (package (inherit gcc-4.8) (name gfortran) (arguments `(#:configure-flags '(--enable-languages=fortran) I get the following error while