[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-users] [crossdev] [PATCH] Add option to specify the path to nc
From: |
Thomas Petazzoni |
Subject: |
Re: [gpsd-users] [crossdev] [PATCH] Add option to specify the path to ncurses5-config |
Date: |
Thu, 26 Jul 2012 10:29:51 +0200 |
Le Wed, 25 Jul 2012 12:03:19 -0400,
Mike Frysinger <address@hidden> a écrit :
> why bother at all ? gpsd supports ncurses pkg-config files which solves all
> these sort of problems. did you pass --enable-pc-files when running ncurses'
> configure script ?
And the --enable-pc-files support in ncurses is completely stupid:
(*) In its configure.in file, it checks whether the PKG_CONFIG_LIBDIR
directory exists to decide whether it should install .pc files or
not. This is stupid, it should just install them unconditionally
(you already said --enable-pc-files, so why bothering checking
once again?). But anyway, you pass
PKG_CONFIG_LIBDIR=/home/foo/mybuildsystem/staging/usr/lib/pkgconfig,
and there you go, ./configure understands that you *REALLY* want
those damn .pc files to be installed.
(*) But then, their misc/Makefile.in installs the .pc files not in
$(PKG_CONFIG_LIBDIR), but in $(DESTDIR)/$(PKG_CONFIG_LIBDIR). So,
since your DESTDIR is going to be /home/foo/mybuildsystem/staging,
and PKG_CONFIG_LIBDIR
is /home/foo/mybuildsystem/staging/usr/lib/pkgconfig, guess what
happens... your .pc files are installed
in
/home/foo/mybuildsystem/staging//home/foo/mybuildsystem/staging/usr/lib/pkgconfig.
And, to make things even better, their configure.in can't be parsed by
the normal autoconf, it needs a special fork of autoconf 2.13 to
regenerate the configure script, so you have basically no chance of
fixing things properly.
Sigh.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com