[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Is PKG_CONFIG_PATH set on the buildsystem?



On 08/09/2007, Michael Schwendt <mschwendt tmp0701 nospam arcor de> wrote:
> On Sat, 8 Sep 2007 13:17:29 +0100, Jonathan Underwood wrote:
>
> > Hi,
> >
> > I was just trying to update  package of mine, and the main change is
> > adding the following macros to the spec file:
> >
> > %define emacs_version %(pkg-config emacs --modversion)
> > %define emacs_lispdir %(pkg-config emacs --variable sitepkglispdir)
> > %define emacs_startdir %(pkg-coonfig emacs --variable sitestartdir)
> >
> > in order to determine those things at package build time (as discussed
> > previously on fedora-packaging). However, on attempting to check the
> > changes in, I get this:
> >
> > cvs diff: [12:11:28] obtained lock in /cvs/extras/rpms/emacs-vm/devel
> > Package emacs was not found in the pkg-config search path.
> > Perhaps you should add the directory containing `emacs.pc'
> > to the PKG_CONFIG_PATH environment variable
> > No package 'emacs' found
> > error: line 31: Version required: Requires: emacs >=
> > error: query of specfile emacs-vm.spec failed, can't parse
>
> (!)
>
> > Package emacs was not found in the pkg-config search path.
> > Perhaps you should add the directory containing `emacs.pc'
> > to the PKG_CONFIG_PATH environment variable
> > No package 'emacs' found
> > error: line 31: Version required: Requires: emacs >=
> > error: query of specfile emacs-vm.spec failed, can't parse
> > cvs tag  -c emacs-vm--
> > ? .build-8.0.3.495-1.fc8.log
> > ? .build-8.0.3.495-3.fc8.log
> > ? .emacs.desktop
> > ? clog
> > ? emacs-vm-8.0.3.495-1.fc8.src.rpm
> > ? emacs-vm-8.0.3.495-3.fc8.src.rpm
> > ? vm-8.0.2-devo-482.tgz
> > ? vm-8.0.3-495
> > ? x86_64
> > ERROR: Tag emacs-vm-- is not in name-version-release format
> > cvs tag: Pre-tag check failed
> > cvs [tag aborted]: correct the above errors first!
> > make: *** [tag] Error 1
> >
> >
> > Is it therefore not possible to call pkg-config from within a spec
> > file? Could this be fixed?
>
> You can fix it by not creating invalid tags in your spec file.
> See (!) above. Just make sure that when pkg-config returns false
> and your macros are empty, you either override the macros with
> defaults or you create valid "Requires" tags via %if/%else/...

Yes - I realize - but I think the issue is the tag is invalid because
pkg-config isn't seeing the .pc file for emacs on the build system,
which is what I would like to fix.. Or am I missing something?
[haven't had any coffee yet today].

J.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]