On 04/18/2018 11:04 AM, Graham Crowe wrote:
On Tue, 2018-04-17 at 12:37 -0700, Terry Coats wrote:
I'm having some compiling trouble and I hope someone can help.
I'm working on getting blfs 8.2 working and wanting to build LXDE.
While working thru all the dependencies I had to compile pcre-8.4.1.
Compilation failed with this error:
*********************
In file included from
/usr/include/c++/7.3.0/ext/string_conversions.h:41:0,
from
/usr/include/c++/7.3.0/bits/basic_string.h:6349,
from /usr/include/c++/7.3.0/string:52,
from pcrecpp.cc:43:
/usr/include/c++/7.3.0/cstdlib:75:15: fatal error: stdlib.h: No such
file or directory
#include_next <stdlib.h>
^~~~~~~~~~
compilation terminated.
make[1]: *** [Makefile:2255: libpcrecpp_la-pcrecpp.lo] Error 1
make[1]: Leaving directory '/blfs/sources/xc/pcre-8.41'
make: *** [Makefile:1322: all] Error 2
*********************
This isn't the first time I've had this error. I had it compiling a
couple of
other things too.
It seems to be a strange permissions problem. If when the error
occurs
I then do "sudo make", compiling continues as it should and finishes
with
no errors. I don't get it. cstdlib and stdlib.h are in the same
folder
and their
permissions look correct. I've googled for solutions but have found
none.
I'm afraid to continue using the "sudo make" trick to get around
this
problem
lest I encounter problems from it down the road. Has anyone else had
to
deal with this and found a solution?
I encounter the same problem with #include_next statements on BLFS 8.1,
even as root. I received a tip to try using 'mkheaders' according to
the caution statement for the GCC chapter in BLFS. That didn't help me.
I also tried reinstalling GCC and that didn't help either. The work
around I have is really ugly, which involves editing the files
containing failing #include_next statements to use full instead
relative paths, e.g.
-#include_next <math.h>
+#include_next </usr/include/c++/7.2.0/math.h>
I'm not at all happy with this solution though and would gladly fix it
if I knew what to fix.
Graham
Terry
Thanks for the tip. Now I'll have something else to try if it happens again.
I've googled and seen this reported a few times but the solutions offered
seemed as varied as the ones offering them, as in no one seems to have
the ultimate solution.
Terry
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
