GNU bug report logs - #27344
[PATCH 0/12] Add computational software and circuit simulators

Previous Next

Full log

Message #161 received at 27344 <at> debbugs.gnu.org (full text, mbox):

From: Theodoros Foradis <theodoros.for <at> openmailbox.org>
To: 27344 <at> debbugs.gnu.org
Cc: Theodoros Foradis <theodoros.for <at> openmailbox.org>
Subject: Re: [bug#27344] [PATCH v2 06/12] gnu: Add freehdl.
Date: Mon, 26 Jun 2017 21:40:09 +0300

Hello again,

>
>> +         (add-before 'configure 'patch-pkg-config
>> +           (lambda _
>> +             (substitute* "freehdl/freehdl-config"
>> +               (("pkg-config") (which "pkg-config"))
>> +               (("cat") (which "cat")))
>> +             #t))
>
> freehdl-config is installed, but it uses a path to pkg-config which is from a native-input (so it will not be retained).
>
> Does this ever work again after removing pkg-config from your profile and then doing "guix gc" ?  I doubt it...
>
>> +         (add-after 'configure 'patch-freehdl-pc
>> +           (lambda _
>> +             (substitute* "freehdl.pc"
>> +               (("=g\\+\\+") (string-append "=" (which "g++")))
>> +               (("=libtool") (string-append "=" (which "libtool"))))
>> +             #t))
>
> Same here...
>
>> +         (add-after 'install-scripts 'make-wrapper
>> +           (lambda* (#:key outputs #:allow-other-keys)
>> +             (let ((out (assoc-ref outputs "out")))
>> +               (wrap-program (string-append out "/bin/freehdl-config")
>> +                 `("PKG_CONFIG_PATH" ":" prefix (,(string-append out "/lib/pkgconfig")))))
>
>
>> +             #t)))))
>> +    (inputs
>> +     `(("perl" ,perl)))
>> +    (native-inputs
>> +     `(("pkg-config" ,pkg-config)
>> +       ("libtool" ,libtool)))
>

I looked again into the issue. I would like to note that the same
problem applies to qucs and qucs-s. They both need a native libtool for
cross-compiling, and one for the final package to reference.

I have to make some changes in other references in qucs, qucs-s and asco
as well, but those are not conflicting with native inputs I
think. Namely cp, and sed.

On the topic on how could the issue be resolved, how is it determined
which package will be in PATH if the same package is included as both
native and non-native input under different names? 

Regards,
-- 
Theodoros Foradis

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.