On Fri, 12 Oct 2018 14:33:35 +0200
Pierre Labastie via blfs-support
wrote:
> Because the piece of code (lines 18 to 23 intest/CMakeLists.txt) which
> generates the error seems to not have been changed in 0.69? But, maybe it
> is upstream job to try to debug this...
Yeah, the problematic code
On Thu, 11 Oct 2018 17:58:44 -0500
rhubarbpieguy via blfs-support wrote:
> I see two batches of Error 2 errors. I hope this is what you want:
We want to see not just the error message, but the actual g++ command
line that caused the error.
When you build via:
make VERBOSE=1
you should be
On Sun, 14 Oct 2018 21:23:06 -0500
rhubarbpieguy via blfs-support wrote:
> OK, it's not that big a deal to redo LFS 8.3. I've nuked all my log
> files but don't remember a problem with the output of "Adjusting the
> Toolchain." Regardless, I'll go again and save that output. I'll
> repost
On Sun, 14 Oct 2018 14:28:01 -0500
rhubarbpieguy via blfs-support wrote:
> [ 89%] Building CXX object test/CMakeFiles/gtk-test.dir/gtk-test.cc.o
> ..
> /usr/include/glib-2.0 -isystem /usr/lib/glib-2.0/include -isystem
> //usr/include -Wall -Wextra -Wpedantic -Wno-unused-parameter
> ..
Good!
On Mon, 15 Oct 2018 00:31:15 -0500
Bruce Dubbs via blfs-support wrote:
> Yes.
Bruce,
OK, could run the following build test on poppler 0.67 applying the
attached poppler_gtk-test_force_build_fail.patch (and no other patches):
patch -p1 -i ../poppler_gtk-test_force_build_fail.patch
mkdir
On Mon, 15 Oct 2018 14:40:12 -0500
rhubarbpieguy via blfs-support wrote:
> Poppler 0.67 compiles without error using
> poppler_fix_cmake_gtk3_include_dir.patch.
:)
Good! OK, there is a problem in the poppler build system. However, there
is *also* something unusual with your system - well, at
On Mon, 15 Oct 2018 21:31:36 -0500
rhubarbpieguy via blfs-support wrote:
> -I//usr/include
Again that is there. Where is this strange path coming from?
> find /etc -type f -print|sort|xargs grep /usr/include reports:
> /etc/udev/hwdb.d/60-keyboard.hwdb:# is the bus-id (see
>
rhubarbpieguy,
For a 0.67 poppler release after the cmake command has been run (I don't
think it matters if the make step was later run and whether or not the
build was actually successful, but you have to do the
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr
On Wed, 3 Oct 2018 23:50:15 -0600
Alex B wrote:
> "export CPLUS_INCLUDE_PATH=/usr/include/c++/8.2.0:/usr/include" did the
> trick.
> ..
> 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
On Thu, 4 Oct 2018 18:33:07 -0500
rhubarbpieguy via blfs-support wrote:
> What have I missed? Is there another area where I'm to set
> CPLUS_INCLUDE_PATH?
See my recent reply to Alex who has a similar problem in the BLFS thread
"Compilation failures - missing header files".
On your system,
On Sun, 7 Oct 2018 07:28:34 -0500
rhubarbpieguy via blfs-support wrote:
> Yes, I changed /etc/profile.d/xorg.sh according to Introduction to
> Xorg-7. So without that change I see the following:
OK, the include search paths look OK to me for both your g++/gcc 8.2.0 and
7.3.0 systems - that is
On Tue, 9 Oct 2018 18:32:08 -0500
rhubarbpieguy via blfs-support wrote:
> I've never set $CPLUS_INCLUDE_PATH and/or $C_INCLUDE_PATH as I compile
> X in /usr. My original (and current) problem is Poppler-0.67.0 won't
> compile and those variables are not set. I only set them as I thought
> you
On Wed, 10 Oct 2018 16:47:49 -0500
rhubarbpieguy via blfs-support wrote:
> I applied the patch to poppler-0.63.0 and poppler-0.67.0.
> Both compiled successfully.
The changeset between 0.63 and 0.64 is tens of thousands of lines long.
Tis much like finding a needle in haystack on the first
On Mon, 1 Oct 2018 21:24:52 +0200 (CEST)
Ben Bellemans via blfs-support wrote:
> Both "/etc/rc.d/init.d/lightdm start" and "init 5" don't start the greeter
> and procuce this warning: "WARNING: Failed to get list of logind seats:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
On Mon, 1 Oct 2018 19:18:40 -0500
rhubarbpieguy via blfs-support wrote:
> > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such
> > file or directory
> > #include_next
> > ^~
Perhaps the first link below is the most helpful:
I also found this:
https://www.linuxquestions.org/questions/slackware-14/on-current-qt-include-directory-appears-2x-4175636463/
(referenced by https://trac.wildfiregames.com/ticket/5157)
Check what the environment variable CPLUS_INCLUDE_PATH is being
set to and where it is being set:
echo
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:
On Wed, 3 Oct 2018 12:18:19 -0600
Alex via blfs-support wrote:
> /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such
> file or directory
> .
> .
> Has anyone encountered this or something similar?
Yes, rhubarbpieguy has:
On Sat, 6 Oct 2018 08:52:26 -0500
rhubarbpieguy via blfs-support wrote:
> It appears setting the new variables didn't fix the problem. I hope
> I've followed your and Ken's guidance correctly. Again, I should mention
> Poppler was the only problem package and the older version works well,
>
On Sat, 22 Sep 2018 22:53:39 +0100
Ken Moffat via blfs-support wrote:
> export LIBSSH2_SYS_USE_PKG_CONFIG=1
>
> just before the DESTDIR install.
Thanks Ken! I'm sure this is going to help more than a few folks out
there. If rustc is going to be used for production, the rust developers
better
On Sun, 23 Sep 2018 01:15:23 +0100
Ken Moffat via blfs-support wrote:
> The other worrying thing about building rust is the way that it
> builds multiple versions of some of the crates (presumably as
> dependencies for different other crates), with all the versions set
> in stone. I fear that
On Sat, 9 Feb 2019 21:29:42 +0100
Cliff McDiarmid via blfs-support
wrote:
> Yes that's it Douglas. I had avoided the legacy fonts, not thinking they
> would effect TWM.
Perhaps this little gotcha should be mentioned on the TWM BLFS page:
On Tue, 30 Jul 2019 10:20:24 +0100
Richard Melville via blfs-support
wrote:
> There's also Startpage and Qwant
Thanks for those! But, Startpage does rely on Google's engine,
and Qwant on Bing's:
https://en.wikipedia.org/wiki/Startpage.com
https://en.wikipedia.org/wiki/Qwant
I also forgot
On Thu, 25 Jul 2019 20:55:18 +0100
Ken Moffat via blfs-support wrote:
> Sorry, I've no idea for what to search for (current google mostly
> returns results for multiple terms with one of the crossed through
> in the 'must include' underneath the summary.
FWIW, Google is really, really going
On Thu, 17 Oct 2019 05:45:10 +
EscuelitaViva via blfs-support wrote:
> New to the list and will be helping out as best I can to support my
> favorite project, LFS. I'm a grey beard, a throw back from the Commodore,
> Atari, Timex Sinclair, Trash 80 days. Anyone program Fortran here?
> Never
On Tue, 08 Sep 2020 11:31:58 +0200
Stephen Berman via blfs-support wrote:
> added the line `gtk-print-backends = cups,file,lpr' to
> ~/.config/gtk-3.0/settings.ini and now firefox shows the printer.
Thanks for posting the solution.
Maybe this setting should be added to the GTK+3 configuration
On Wed, 6 Jan 2021 22:24:21 -0600
Paul via blfs-support wrote:
> Question 2: Is it possible to run a system using only the kernel, grub
> (or other bootloader), maybe a compiler/libc if I need it, and a single
> executible loaded by the kernel that I would write in C?
Just for the record,
27 matches
Mail list logo
