On Thu, Oct 04, 2018 at 06:33:07PM -0500, rhubarbpieguy via blfs-support wrote:
>
> On 10/3/18 7:17 PM, Michael Shell via blfs-support wrote:
> > It seems another BLFS user has encountered this issue (but with
> > applications other than poppler):
> >
> > http://lists.linuxfromscratch.org/pipermail/blfs-support/2018-October/080407.html
> >
> > I also found this:
> >
> > https://www.linuxquestions.org/questions/slackware-14/on-current-qt-include-directory-appears-2x-4175636463/
> >
> > Check what the environment variable CPLUS_INCLUDE_PATH is being
> > set to and where it is being set:
> >
> > echo $CPLUS_INCLUDE_PATH
> > grep -s CPLUS_INCLUDE_PATH /etc/*
> >
> > Problems can occur here if a path is duplicated within $CPLUS_INCLUDE_PATH
> >
> >
> > Cheers,
> >
> > Mike
>
>
> Perhaps CPLUS_INCLUDE_PATH is the problem as I have no such variable.
> However, I'm confused, as the only reference I see in the documentation
> refers to installing X outside the standard prefix. I install X using /usr,
> which I understood as the standard prefix.
>
> What have I missed? Is there another area where I'm to set
> CPLUS_INCLUDE_PATH?
>
No, that is the only place, and only people who build Xorg in
somewhere other than /usr are known to need it. But maybe setting
it will work for you when building poppler - if so, we would all be
_slightly_ closer to understanding what is going wrong for you.
Alternatively, it might not help. But it seems worth trying since
we don't have any other suggestions (I guess my suggestion that you
maybe used the old CMMI instead of cmake didn't fit).
We have seen a number of settings which are only needed by some
people, e.g. when building rustc, setting RUSTFLAGS to link to
libffi, but if needed they do no harm.
ĸen
--
Well grubbed , old mole!
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
