On Thu, 4 Oct 2018, 6:29 pm Ken Moffat via blfs-support, < [email protected]> wrote:
> On Thu, Oct 04, 2018 at 04:01:16PM -0700, Paul Rogers via blfs-support > wrote: > > > > > > Thanks Michael. That did it. Even though CPLUS_INCLUDE_PATH was not > set > > > and returned empty when echoed, setting explicitly it as "export > > > CPLUS_INCLUDE_PATH=/usr/include/c++/8.2.0:/usr/include" did the trick. > I > > > have the packages compile correctly now, hopefully will finish the > build. > > > > > > I still don't see why there is a need to set that variable, when it is > > > not being set by jhalfs and can't find any reference to it under /etc > > > either. The packages should have compiled successfully without the > need > > > for it. > > > > > > Thanks for all those who tried to help, much appreciated. > > > > > > Regards, > > > > > > Alex > > > > Alex, indeed, that would really bother me too! It really does suggest > there are further problems in your system. I'd stop until I could figure > out why this workaround is necessary. > > > > In an ideal world, yes, we would all stop until we (thought) we > understood how a problem had arrived. But a modern linux desktop > system is a complex beast. > > Currently (see the -book list) I'm looking at a problem (tests now > hang in a perl module) which might be related to a newer openssl, but > to me appears to be related to more-recent kernel (4.18) point > releases. > > At the moment my interesting systems are unavailable (currently, > updating rustc and firefox as part of my firefox upgrade scripts : > 62.0.3 should be fine with rustc-1.25.0 but I was not expecting > another 62 point release and was getting the scripts ready for > 63-beta testing. > > But when that finishes, I will be trying a developer version of that > module which appears to fix the problem (I want to check that things > work even where they used to with 8.3) and trying to confirm that a > recent stable 4.18 caused the problem seems like a waste of time > > (4.18.3 seems ok, 4.18.8 included a CVE fix, 4.18.9 has problems). > But as with everything else in the LFS area - your system, your > choices. > Thanks Ken, I hope the root cause of this anomaly will be found or it presents itself sooner than later. The work around seems to be working well for now, perhaps until something else breaks that too, but let's hope not. Regards Alex > > ĸ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 >
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
