Re: How to change config script for multiarch?
On Wed, Feb 10, 2016 at 10:59 AM, Alastair McKinstry
<mckinstry@debian.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi ,
>
> I've solved this problem by:
> (1) creating a pkg-config script, adding it as multiarch.
> (2) editing the config script to use the pkg-config script.
>
> In particular, for any non-standard variables, you can read them, by eg:
>
> f90_compiler=$(pkg-config mypkg --variable=f90_compiler)
>
> Its probably a good idea to document the config script as deprecated
> in output, the man page, etc.
(2) wrapper are not cross build safe...
> regards
> Alastair
>
> On 10/02/2016 07:12, NOKUBI Takatsugu wrote:
>> I am a maintainer of chasen package. It contains chasen-config, it
>> work as pkg-config like but it's a single script.
>>
>> Latest lintain reports:
>> E: libchasen-dev: old-style-config-script-multiarch-path
> usr/bin/chasen-config full text contains architecture specific dir
> x86_64-linux-gnu
>>
>> But I want to keep libchasen-dev as Multi-Arch: same. Would you tell
>> me finding the correct way to change the script?
>>
>>
>> --
>> Alastair McKinstry, <alastair@sceal.ie>, <mckinstry@debian.org>,
> https://diaspora.sceal.ie/u/amckinstry
>> Misentropy: doubting that the Universe is becoming more disordered.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJWuwoCAAoJEMvmu05dmtOlhiUP/AuG7t8pMlzb4sgzvO//xAGK
> O8aNRi789Yun4svsClBFrO/lv2GcynH5h6fqLL1oAndmBCX5cuMqjCwzUEEngCcK
> Z5JiQ4MoQvFTqAneN0WGsvDPbq0Ofg6Lfti/FO3OsD6emvSn/f5f1RaF5mrd8vRd
> SolUJDjtABV6DVqX8tY8rbf7u/ecdeYq0zMnEPsKEnUgrNSJQLGm0XC5YyANeDcG
> 2kpxPtPhHF9yz0yqV/hqiYTjDFR53vY29q/9QjjI9amdEV2btdeVf5cvtGFwXNQm
> qL3VpeD0jbzMFYyIfcQy4IjhENkijyWl4BP9MD3sJ3vSpEjmLIfw5PGHVn2PgoEz
> 8zuAT4ub0D0ANRkA2JRLk9fVHtmGtEa4l2lpEztv4HeBeitEbKllOGQ1pU/GROax
> 2CmiGnxhG74T2qFC0bPDqHMKsc8W3SdXs6uYkuv+4WXiPuul14oD/7nOltGUc1p4
> WHS5qSAZ/CV/madVZw1oeYDctehLYMk5RjYM32VO26lAoz0RkhAopdfmk+8QFUV8
> nOJG2PKj1s4E3kJPZk2uLiFRSdhZe9PZXPnGcbJBpiEEw/Yo/6uhLOrm+n43gi/N
> ZAPWnWuEMY/22r7XJg0NQwmNCCPSqGeUVG2k18A7nYlf/eIY+lhnauJUwpKEFass
> JaVBSA7Fop2V1sPkOVzS
> =84mc
> -----END PGP SIGNATURE-----
>
Reply to: