On Mon, May 28, at 11:08 Dan Nicholson wrote:
> On 5/28/07, Baho Utot <[EMAIL PROTECTED]> wrote:
> > When compiling libXfont-1.1.0.tar.bz2 part of Xorg Utilities
> >
> > I get the following
> >
> > checking for XFONT... configure: error: Package requirements (xproto xtrans
> > fontsproto fontenc) were not met:
> >
> > No package 'xtrans' found
> > No package 'fontenc' found
> >
> > Consider adjusting the PKG_CONFIG_PATH environment variable if you
> > installed software in a non-standard prefix.
> 
> This very much sounds like PKG_CONFIG_PATH isn't set to the location
> that you're trying to install Xorg. Make sure that you have
> PKG_CONFIG_PATH=$XORG_PREFIX/lib/pkgconfig and you have that exported
> in the shell you're building in.
>

Fisrt, I wanted to do that for a long time, and I did found the chance
with this post in support.

I think we don't make it obvious, in any of our pages, how important
the PKG_CONFIG_PATH variable and a run for ldconfig (when you are
installing libs) is, for a succesfull build.

With regards to PKG_CONFIG_PATH is mentioned in a brief in the bash startup 
files and of cource it's in own page, but that's all.

I think a small paragraph in the Notes on Building Software of each of
these items, would be a wise addition.

Some more notes.

We have also append in LFS (during glibc installation) the /opt/lib in 
the /etc/ld.so.conf.
Just yesterday, Dan in r6791, reverted a patch that appended PATH and
PKG_CONFIG_PATH in /opt, so at a first glance this looks like a contradiction. 
Anyway this is belongs to LFS.

And second.
The PKG_CONFIG_PATH is only usefull during compilation but it serves no
purpose in a production system, thus it has to be avoided in any shell startup
file during loging.

It may brings more questions in support, but *if* we place these notes I was
talking about, we can always redirect the support questions to that
section of the book.
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to