[blfs-support] fcron md5sum BLFS 10.1/development

The fcron md5sum I see differs from the documentation. md5sum fcron-3.2.1.src.tar.gz generates 489a7f41afdd88f9312b517b8a6c2433, while the documentation shows bd4996e941a40327d11efc5e3fd1f839.  I've downloaded the file several times and the md5s for all other files hit.  What might I be

Re: [blfs-support] Kernel configuration observations/questions - BLFS 10.0/development

On 12/3/20 8:14 PM, Douglas R. Reno via blfs-support wrote: On 11/26/20 4:58 PM, rhubarbpieguy--- via blfs-support wrote: Hi rhubarbpieguy, I looked into the ones that Ken didn't do, and I have some feedback. BlueZ -*- Cryptographic API ---> [CONFIG_CRYPTO]   User-space interf

[blfs-support] Kernel configuration observations/questions - BLFS 10.0/development

autofs File systems --->   <*/M> Kernel automounter version 4 support (also supports v3) [CONFIG_AUTOFS4_FS]    I believe Kernel automounter support has no options.  Should the above lines be deleted? File systems  --->   [*] Network File Systems ---> [CONFIG_NETWORK_FILESYSTEMS]    

[blfs-support] Installation of the kernel systemd documentation - LFS 10.0/development

General setup -->    [*] Control Group support [CONFIG_CGROUPS]    [ ] Enable deprecated sysfs features to support old userspace tools [CONFIG_SYSFS_DEPRECATED]    [*] Configure standard kernel features (expert users) [CONFIG_EXPERT] --->   [*] open by fhandle syscalls [CONFIG_FHANDLE]   

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

On 10/20/20 9:00 AM, Pierre Labastie via blfs-support wrote: On Tue, 2020-10-20 at 06:50 -0500, rhubarbpieguy--- via blfs-support wrote: Sorry, I was sloppy providing output. The problem occurs with 'make' and I included the tail end of 'make install.' The error with 'make' is: ninja

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

Sorry, I was sloppy providing output.  The problem occurs with 'make' and I included the tail end of 'make install.'   The error with 'make' is:    ninja: build stopped: subcommand failed.    make[3]: *** [Makefile.gn_run:552: run_ninja] Error 1    make[3]: Leaving directory

Re: [blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

On 10/17/20 9:14 PM, Ken Moffat via blfs-support wrote: On Sat, Oct 17, 2020 at 04:11:07PM -0500, rhubarbpieguy--- via blfs-support wrote: Compiling QtWebEngine fails with the following end output:    make[3]: *** No rule to make target '/sources/qtwebengine-everywhere-src-5.15.0/build/src

[blfs-support] QtWebEngine - make: *** [Makefile 49: sub-src-make_first] Error 2 - BLFS 10.0

Compiling QtWebEngine fails with the following end output:    make[3]: *** No rule to make target '/sources/qtwebengine-everywhere-src-5.15.0/build/src/core/release/QtWebEngineCore.stamp', needed by '../../lib/libQt5WebEngineCore.so.5.15.0'.  Stop.    make[3]: Leaving directory

[blfs-support] 'systemctl enable bluetooth' failure - BLFS 9.1 (systemd)

Executing 'systemctl enable bluetooth' responds with the following:    Failed to execute /lib/systemd/systemd-sysv-install: No such file or directory I believe I compiled systemd in LFS and BLFS according to instructions and don't see /lib/systemd/systemd-sysv-install in the LFS 9.1

[blfs-support] Compiling systemd and dbus in chroot? - BLFS 9.1 systemd

Can/should systemd and dbus be compiled in chroot?  I assume so, partly due to the following in the dbus documentation:    "If not in chroot, at this point, you should reload the systemd daemon, and reenter multi-user mode with the following commands (as the root user):"    systemctl

[blfs-support] libusb kernel configuration - BLFS 9.1

A minor point, but I think the following is inaccurate:    Device Drivers --->         [*] USB support ---> [CONFIG_USB_SUPPORT]           <*/M> Support for Host-side USB  [CONFIG_USB]      (Select any USB hardware device drivers you may need on the same page) The 'Support for

[blfs-support] Firefox 'gold linker' mozconfig documentation - BLFS 9.1/development

I'm a touch confused about the following in the Firefox mozconfig documentation:    # Do not specify the gold linker which is not the default. It will take    # longer and use more disk space when debug symbols are disabled. There seems to be no action to be taken.  Most other lines specify

[blfs-support] Bluez/bluetooth keyboard timeout and no reconnection at reboot. BLFS 9.0

I've compiled Bluez and can connect to my ThinkPad bluetooth keyboard which works well.  However, the keyboard times out.  And, before timing out, if I reboot or return from hibernation the keyboard doesn't reconnect. To eliminate the keyboard as a problem I tested with a binary

[blfs-support] BlueZ documentation duplication. BLFS 9.0/development

The following is listed in the Kernel Configuration and testsuite sections of the Bluez documentation.    [*] Networking support ---> [CONFIG_NET] Could/should it be removed from the testsuite section?  A small matter, but it would remove duplication.

[blfs-support] BlueZ documentation duplication. BLFS 9.0/development

The following is listed in the Kernel Configuration and testsuite sections of the Bluez documentation.    [*] Networking support ---> [CONFIG_NET] Could/should it be removed from the testsuite section?  A small matter, but it would remove duplication.

[blfs-support] Bluez test failure? BLFS 9.0

Compiling Bluez with 'make test' fails with:    ./test-driver line 107:   8971 Aborted   "$@" > log_file 2>&1    FAIL: unit/test-sdp The process then locks.  What does the failure mean?  To that point the following pass:    PASS: unit/test-eir    PASS:

[blfs-support] Bluez test failure? BLFS 9.0

Compiling Bluez with 'make test' fails with:    ./test-driver line 107:   8971 Aborted   "$@" > log_file 2>&1    FAIL: unit/test-sdp The process then locks.  What does the failure mean?  To that point the following pass:    PASS: unit/test-eir    PASS:

[blfs-support] For the tests? elogind-241.3 - BLFS 9.0/development

The Optional section of the elogind documentation refers to packages required for the tests.  However, the installation section states elogind does not come with a test suite.  So what tests? And I receive the following when compiling elogind:    meson.build:63:8: ERROR: Program or command

[blfs-support] Autoconf2.13 documentation - BLFS 9.0/development

For consistency, should the title in the autoconf documentation be Autoconf-2.13? -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page

[blfs-support] Glib -Dselinux=false Command Explanation - BLFS 9.0/development

-Dselinux=false is a Command Explanation in the Glib documentation.  Should it be -Dselinux=disabled?  I don't see disabled as a valid configuration option. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the

[blfs-support] UnZip - 6.0/ Zip - 3.0 BLFS 9.0/development

A minor point, but should 'UnZip - 6.0' and 'Zip - 3.0' in the documentation be 'UnZip - 60' and 'Zip - 30' or perhaps UnZip60 and Zip30?  All other packages reference the file name. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html

Re: [blfs-support] Installing Python modules in BLFS - BLFS 9.0/development

On 9/21/19 9:37 AM, Bruce Dubbs via blfs-support wrote: On 9/21/19 7:46 AM, rhubarbpieguy--- via blfs-support wrote: Although Python 3 is now installed in LFS, it appears necessary to reinstall Python 3 in BLFS to install Python modules.  From the Python 3 documentation:     "Pyt

[blfs-support] Installing Python modules in BLFS - BLFS 9.0/development

Although Python 3 is now installed in LFS, it appears necessary to reinstall Python 3 in BLFS to install Python modules.  From the Python 3 documentation:    "Python 3 was installed in LFS.  The only reason to install it here is if optional modules are needed." I understand the note, but

[blfs-support] Minor documentation typo -D=LLVM_ENABLE_RTTI=ON - BLFS 9.0/development

The LLVM-8.0.1 documentation lists -D=LLVM_ENABLE_RTTI=ON in the Command Explanations section.  I believe it should be -DLLVM_ENABLE_RTTI=ON. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information

[blfs-support] Bluetooth keyboard bluez configuration. AutoEnable, timeouts? - BLFS 8.4

I'm attempting to use a ThinkPad bluetooth external keyboard with my BLFS 8.4 build.  I can access it using bluetoothctl with the following:    power on    agent KeyboardOnly    default-agent    pairable on    scan on    pair 90:7F:61:2A:CD:42    trust 90:7F:61:2A:CD:42    connect

Re: [blfs-support] Rustc documentation - "Unusually, a DESTDIR-style method is being used to install this package."

On 5/27/19 10:29 AM, Eric via blfs-support wrote: On Mon, 27 May 2019 14:42:26 +0200, Pierre Labastie via blfs-support wrote: On 27/05/2019 13:58, rhubarbpieguy via blfs-support wrote: The BLFS and development Rustc documentation states the following:   Unusually, a DESTDIR-style method

[blfs-support] Rustc documentation - "Unusually, a DESTDIR-style method is being used to install this package."

The BLFS and development Rustc documentation states the following:    Unusually, a DESTDIR-style method is being used to install this package. A small matter perhaps, but should it be:    Usually, a DESTDIR-style method is used to install this package. --

[blfs-support] D-bus error with bluetoothctl

When attempting to run bluetoothctl I receive the following: Waiting to connect to bluetoothd...dbus[11864]: arguments to dbus_connection_get_object_path_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 5905. This is normally a bug in some

[blfs-support] BlueZ with bluetooth keyboard

I'm attempting to use a bluetooth keyboard and assume I need BlueZ.  I've compiled it and see no errors but have problems/questions. Most step-by-step instructions I've found use hcitool, hciconfig and such, but it appears those no longer exist.  Correct? I'm confused by bluemoon and

Re: [blfs-support] BLFS 8.4 - Firefox 65.0.1 showing up as Nightly on my system

On 3/9/19 11:17 AM, Douglas R. Reno via blfs-support wrote: Good morning (or afternoon), I setup a build of Firefox to run overnight on one of my 8.4 systems. Using my pre-existing script and mozconfig, which worked for 8.4's release testing to give me a Firefox Quantum install, gave me a

[blfs-support] Xorg Intel Driver documentation - BLFS 8.3/development

In November of 2018 a thread addressed the Intel I810 driver in the Intel Driver documentation. I810 references were removed from the menu configuration section but the following remains: "Enable the following options in the kernel configuration.  Only one of the lines "Intel I810" or

[blfs-support] Thin vertical line with X.

I've developed a thin vertical line about three quarters to the right of my screen.  Frankly, I'm uncertain this is a BLFS question as I considered it a hardware problem but ... My old box ran BLFS 8.2 and developed an identical problem.  As a result, I replaced it with my current box (BLFS

Re: [blfs-support] Xorg Intel Driver-20180223 Kernal Configuration. - BLFS 8.3/development

I honestly think it'd be smart to pull up the Kernel Configuration section in the Index and verify that every package that has special kernel configuration hasn't had it's options moved. We need a volunteer for that.  The current editors' plates are pretty full.   -- Bruce I realize

Re: [blfs-support] Xorg Intel Driver-20180223 Kernal Configuration. - BLFS 8.3/development

On 11/24/18 10:14 PM, Bruce Dubbs via blfs-support wrote: On 11/24/2018 10:04 PM, renodr via blfs-support wrote: On 2018-11-24 20:49, Bruce Dubbs via blfs-support wrote: On 11/24/2018 06:25 PM, Ken Moffat via blfs-support wrote: On Sat, Nov 24, 2018 at 11:33:35AM -0600, rhubarbpieguy via

[blfs-support] Xorg Intel Driver-20180223 Kernal Configuration. - BLFS 8.3/development

The Xorg Intel Driver-20180223 documentation states the following regarding kernel configuration: Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be selected. I see no "Intel i810" option with make menuconfig. Also, "If you select the latter, “Enable modesetting...”

[blfs-support] JS-52.2.1gnome1 "If installing in the chroot environment, be sure to export the SHELL environment variable or configuration of the package will fail" - BLFS 8.3

The JS-52.2.1gnome1 documentation states the following. "If installing in the chroot environment, be sure to export the |SHELL| environment variable or configuration of the package will fail" That's good, but would it make sense to change it to: "If you are compiling JS in chroot,

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3 [solved]

My problem was caused by incorrectly configuring xorgproto.  I typed 'meson --prefix=/$XORG_PREFIX ..' instead of 'meson --prefix=$XORG_PREFIX ..'  The slash caused //usr when compiling. Unfortunately, it didn't seem to cause an error message but caused problems when compiling Poppler.

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

On 10/15/18 7:45 PM, Michael Shell via blfs-support wrote: In the meantime, Bruce and rhubarbpieguy, what version of cmake are each of you running? cmake --version rhubarbpieguy, can you try a 0.67 build with the two patches: patch -p1 -i ../poppler_fix_cmake_gtk3_include_dir.patch patch

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

On 10/11/18 9:57 PM, Michael Shell via blfs-support wrote: 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

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

On 10/10/18 11:55 PM, Michael Shell via blfs-support wrote: Could you paste the gcc/g++ commands just before and after the build failure occurred so we can see what command line options gcc/g++ was invoked with when attempting to build gtk-test.cc? I see two batches of Error 2 errors.  I

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

The attached patch reverts what I think is your trouble maker. Apply it to 0.63.0 and later (it should work with 0.69.0 as well) using: patch -p1 -i ../poppler_revert_gtk3_include_dirs.patch And let us know if you can build 0.63.0 and later after applying the patch. Cheers, Mike

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

On 10/9/18 4:21 AM, Michael Shell via blfs-support wrote: Can you compile Poppler-0.67.0 on your gcc 8.2.0 system *if* $CPLUS_INCLUDE_PATH and/or $C_INCLUDE_PATH are *not* set (don't have any pathappend lines in /etc/profile.d/xorg.sh, unset/clear C_INCLUDE_PATH CPLUS_INCLUDE_PATH, and restart

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

On 10/7/18 10:31 PM, Ken Moffat via blfs-support wrote: On Sat, Oct 06, 2018 at 08:52:26AM -0500, rhubarbpieguy via blfs-support wrote: Again, I should mention Poppler was the only problem package and the older version works well, but it would be nice to know what I've done wrong

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

"Without any CPLUS_INCLUDE_PATH etc. variables set, can you build poppler 0.62 on the gcc 8.2.0 system?" - I misread your above

[blfs-support] MarkupSafe/Beaker/Mako ModuleNotFoundError: No module named 'html' - BLFS 8.3

I remember receiving "ModuleNotFoundError: No module named 'html' for the MarkupSafe, Beaker, and Mako Python 3 modules when compiling X.  I put the problem on the back burner as those modules compiled for Python 2 without error so Mesa subsequently compiled. However, now that I've finished

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

On 10/5/18 1:55 AM, Michael Shell via blfs-support wrote: On Thu, 4 Oct 2018 22:03:45 -0400 Michael Shell via blfs-support wrote: On your system, run these commands: After helping Alex some more, these commands reveal info we need from your system: echo $CPLUS_INCLUDE_PATH echo

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

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:

Re: [blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

On 9/25/18 4:08 PM, rhubarbpieguy wrote: I receive the following error with the make and 'make install' Poppler commands.  Poppler-data installs without error. /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory  #include_next

[blfs-support] Poppler-0.67.0 gtk-test.dir/all Error 2 - BLFS 8.3

I receive the following error with the make and 'make install' Poppler commands.  Poppler-data installs without error. /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory  #include_next    ^~ compilation terminated. make[2]: ***

[blfs-support] Falkon?

As Qupzilla is now Falkon and part of KDE, will Falkon be in BLFS? I see only QupZilla in the development documentation. I ask this mostly from curiosity.  I realize things take time. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ:

[blfs-support] xdg-utils - config.status: WARNING: 'scripts/Makefile.in' seems to ignore the --datarootdir setting - BLFS 8.2

I receive "config.status: WARNING: 'scripts/Makefile.in' seems to ignore the --datarootdir setting" when compiling xdg-utils.  Can this error be ignored? I also receive:    xmlto: /compiler/xdg-utils-1.1.2/scripts/html/../desc/xdg-desktop-menu.xml does not validate (status 3)    xmlto:

Re: [blfs-support] xdg-utils validation error? - BLFS 8.2

On 06/06/2018 10:33 PM, rhubarbpie...@gmail.com wrote: I receive the following when compiling xdg-utils.  I've compiled xmlto and w3m. checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking for xmlto... /usr/bin/xmlto configure:

[blfs-support] Python module libxml2 needed by itstool? - BLFS 8.2

When compiling itstool in BLFS 8.2 I receive:    checking for Python module libxml2... not found    configure error: Python module libxml2 is needed to run this package I'm confused as I don't see the Python module listed as a requirement.  I see docbook (installed), which requires libxml2

[blfs-support] xdg-utils validation error? - BLFS 8.2

I receive the following when compiling xdg-utils.  I've compiled xmlto and w3m. checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking for xmlto... /usr/bin/xmlto configure: creating ./config.status config.status: creating Makefile

[blfs-support] gtk+-2 required to compile Thunderbird? - BLFS 8.2/development

Compiling Thunderbird without gtk+-2 installed produces the following: - DEBUG: configure:12485: checking for gtk+-2.0 >= 2.18.0 gtk+-unix-print-2.0 glib-2.0 >= 2.22 gobject-2.0

[blfs-support] libxshmfence-1.2.tar.bz2 - BLFS 8.2

Compiling |libxshmfence-1.2.tar.bz2 fails during make. |--- | make all-recursive make[1]: Entering directory '/sources/libxshmfence-1.2' Making all in src make[2]: Entering directory

[blfs-support] Fluxbox "File format not recognized" - BLFS 8.1

I receive the following error when compiling Fluxbox-1.3.7: make[2]: Entering directory '/sources/fluxbox-1.3.7' g++ -g -O2-o fluxbox src/fluxbox-AlphaMenu.o src/fluxbox-ArrowButton.o src/fluxbox-AttentionNoticeHandler.o src/fluxbox-CascadePlacement.o src/fluxbox-ClientMenu.o

Re: [blfs-support] Firefox 57 File/File Open screen placement. BLFS development

On 12/17/2017 06:03 PM, rhubarbpie...@gmail.com wrote: When opening a file in Firefox 57 (File/File Open) the Open window isn't positioned properly.  It's too high and the top of the window is cut off. Firefox also won't open maximized.  I assume the problems are related. Good news/bad

[blfs-support] Firefox 57 File/File Open screen placement. BLFS development

When opening a file in Firefox 57 (File/File Open) the Open window isn't positioned properly.  It's too high and the top of the window is cut off. Firefox also won't open maximized.  I assume the problems are related. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ:

[blfs-support] Firefox 57 undefined errors. - BLFS 8.1

I receive the following errors when compiling Firefox 57 with BLFS 8.1: /sources/firefox-57.0/js/src/jsstr.cpp:1525: error: undefined reference to 'unorm2_normalizeSecondAndAppend_59' /sources/firefox-57.0/js/src/jsstr.cpp:1534: error: undefined reference to

[blfs-support] Flash Player-26.0.0.151 downloads. BLFS 8.1/Development

The NPAPI plugin for Gecko (Mozilla) and WebKit 64-bit download link produces the following: The requested URL /pub/flashplayer/pdc/26.0.0.151/flash_player_npapi_linux.x86_64.tar.gz was not found on this server. In fact, all links but for Chromium Launcher seem unresponsive. --

[blfs-support] Midori keyboard shortcuts - BLFS 8.0

My shortcut key for the url bar doesn't work in Midori. I'm uncertain whether Midori considers the Navigationbar or Location the url bar but I've tried both unsuccessfully. And regardless of which I program, focus is first on the search bar and then the url bar if I press the key twice.

[blfs-support] PyCairo-1.13.2 Python Modules development documentation.

The PyCairo development documentation in Python Modules section contains the following: Cairo-1.14.8 , *python* , and/or Python-3.6.1

[blfs-support] Occasional loss of sound. BLFS 8.0

I occasionally lose sound. Alsamixer shows routine volume levels and nothing's muted. The problem is infrequent and sound returns after an hour or so. It's a minor problem, but I'd be interested in the cause and what I can do to correct the situation. --

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9

I have a correction to my 04/07/17 post. /etc/fonts/local.conf with hintstyle set to hintfull can exist. In fact, on my box it must exist for crisper fonts if /etc/fonts/conf.d/10-hinting-slight.conf is present. However, the gist of the post was correct. On my box, with or without

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9

This problem returned in BLFS 8.0 but with a twist as neither method I used in 7.10 works. But deleting/renaming /etc/fonts/conf.d/10-hinting-slight.conf plus adding the following to /etc/profile works: export FREETYPE_PROPERTIES="truetype:interpreter-version=35 cff:no-stem-darkening=1

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

On 04/05/2017 05:44 PM, Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: On 04/04/2017 11:04 PM, Michael Shell wrote: On Tue, 4 Apr 2017 10:43:29 -0500 Bruce Dubbs wrote: This is what I found via google: https://access.redhat.com/articles/65378

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

On 04/04/2017 11:04 PM, Michael Shell wrote: On Tue, 4 Apr 2017 10:43:29 -0500 Bruce Dubbs wrote: This is what I found via google: https://access.redhat.com/articles/65378 https://forum.manjaro.org/t/acpi-error-on-boot-after-updating-to-4-9/12894 And for me, this

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

On 04/03/2017 09:15 PM, Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: On 04/03/2017 05:01 PM, Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: Through LFS 7.10 I've suppressed ACPI errors with a /etc/sysctl.conf file containing 'kernel.printk = 4.' However, with LFS 8.0 and the 4.9.9

Re: [blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

On 04/03/2017 05:01 PM, Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: Through LFS 7.10 I've suppressed ACPI errors with a /etc/sysctl.conf file containing 'kernel.printk = 4.' However, with LFS 8.0 and the 4.9.9 kernel the errors aren't suppressed. Is this a kernel issue? I see the

[blfs-support] ACPI errors and 4.9.9 kernel. LFS 8.0

Through LFS 7.10 I've suppressed ACPI errors with a /etc/sysctl.conf file containing 'kernel.printk = 4.' However, with LFS 8.0 and the 4.9.9 kernel the errors aren't suppressed. Is this a kernel issue? I see the following in Kernal Hacking/printk and dmesg options --->: Default

Re: [blfs-support] Qtwebkit - bash: qmake: command not found. BLFS 7.10/development

On the qt5 page: cat > /etc/profile.d/qt5.sh << "EOF" # Begin /etc/profile.d/qt5.sh QT5DIR=/opt/qt5 pathappend $QT5DIR/bin PATH pathappend $QT5DIR/lib/pkgconfig PKG_CONFIG_PATH export QT5DIR # End /etc/profile.d/qt5.sh EOF You probably need to source that before building

Re: [blfs-support] Qtwebkit - bash: qmake: command not found. BLFS 7.10/development

On 01/28/2017 06:17 PM, Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: I receive 'bash: qmake: command not found' when compiling qtwebkit. I compiled qt in /usr and /usr/bin/qt5/qmake exists. Qtwebkit compiles if I enter /usr/bin/qt5/qmake. Also, I receive 'find: '/lib/pkgconfig': No

[blfs-support] Qtwebkit - bash: qmake: command not found. BLFS 7.10/development

I receive 'bash: qmake: command not found' when compiling qtwebkit. I compiled qt in /usr and /usr/bin/qt5/qmake exists. Qtwebkit compiles if I enter /usr/bin/qt5/qmake. Also, I receive 'find: '/lib/pkgconfig': No such file or directory.' My $QT5PREFIX variable exists from compiling qt,

[blfs-support] BLFS 7.10 fonts less clear than in 7.9

I found simply deleting or renaming /etc/fonts/conf.d/10-hinting-slight.conf restores the less bold fonts I had in BLFS 7.9. I believe another solution is to use the following code in /etc/fonts/local.conf: true hintfull false This is not a BLFS

Re: [blfs-support] Midori - opening images and reading html documentents locally. BLFS 7.10

On 10/02/2016 03:14 AM, Pierre Labastie wrote: On 01/10/2016 21:46, rhubarbpie...@gmail.com wrote: If I open a local jpg in Midori the image doesn't appear. Instead, it looks as if it opens in a text editor. I've read Midori uses GIO and I have compiled GConf. I don't see a solution in

[blfs-support] Midori - opening images and reading html documentents locally. BLFS 7.10

If I open a local jpg in Midori the image doesn't appear. Instead, it looks as if it opens in a text editor. I've read Midori uses GIO and I have compiled GConf. I don't see a solution in Edit/Preferences/File Types. Local html documents also appear as if opened in a text editor.

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

True, a quick diff didn't highlight that. My 7.10 desktop is powered off at the moment, and those symlinks actually point to /usr/share/fontconfig/conf.avail in my case - I looked at my first-stage backups, in /staging on my server, but of course the links are broken when I do that. A (very)

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

On 09/23/2016 07:41 PM, Ken Moffat wrote: On Thu, Sep 22, 2016 at 02:26:02PM -0500, rhubarbpie...@gmail.com wrote: I thought fontconfig creates /etc/fonts/fonts.conf and the files differ between 7.9 and 7.10. In fact they differ significantly in size. It seems compiling fontconfig is pretty

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

On 09/21/2016 09:09 PM, Michael Shell wrote: On Wed, 21 Sep 2016 16:30:57 -0500 rhubarbpie...@gmail.com wrote: antialias - Changing the antialias setting from 'true' to 'false' helped significantly. The fonts are just a touch 'blotchy' but the bold problem is eliminated. However, if I

[blfs-support] LibreOffice-5.2.1 external/tarballs link commands. BLFS Development

Perhaps I'm reading this wrong, but it seems we have two too many ../'s in the following: install -dm755 external/tarballs && ln -sv ../../../libreoffice-dictionaries-5.2.1.2.tar.xz external/tarballs/ && ln -sv ../../../libreoffice-help-5.2.1.2.tar.xz external/tarballs/ The documentation

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

For the lcdfilter, try lcdlight or lcdnone in place of lcddefault and see what happens. Please do let us know if you learn anything in this regard because in the future others will probably run into the same problem. Cheers, Mike Shell I admire your dedication to this and your

Re: [blfs-support] Installing dejavu fonts - Xorg-7.7 Testing and Configuration. BLFS 7.10/BLFS Development

st like every other package. ... -- Bruce I think the issue rhubarbpieguy is pointing out is that the *.ttf files are in a sub-directory (dejavu-fonts-ttf-2.37/ttf), but the install command in the book is trying to copy them from the current directory (*.ttf instead of ttf/*.ttf). Paul

[blfs-support] Installing dejavu fonts - Xorg-7.7 Testing and Configuration. BLFS 7.10/BLFS Development

The documentation to install dejavu fonts states: As a font installation example, consider the installation of the DejaVu fonts. From the unpacked source directory, run the following commands as the |root| user

Re: [blfs-support] BLFS 7.10 fonts less clear than in 7.9.

On 09/19/2016 02:53 PM, Michael Shell wrote: On Mon, 19 Sep 2016 19:29:19 +0100 Ken Moffat wrote: The internet has a plethora of suggestions for tweaking what happens in fontconfig. The quality of on-screen font rendering under Linux has long irked me. It seems that

[blfs-support] BLFS 7.10 fonts less clear than in 7.9.

I've run BLFS 7.10 for several days and noticed less clear fonts than with 7.9. I reinstalled from square one without success and don't see my error. As a test, I reinstalled BLFS 7.10, but with BLFS 7.9 dejavu and fontconfig packages (dejavu-fonts-ttf-2.35 and fontconfig-2.11.1) and my

[blfs-support] libpng-1.6.24-apng.patch.gz problem - Development BLFS 2016-08-07

Attempting to apply libpng-1.6.24-apng.patch.gz with "gzip -cd ../libpng-1.6.24.patch.gz | patch -p1" yields the following: can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? I've also unzipped it manually and patched separately using "patch -Np1

Re: [blfs-support] Midori startup errors.

On 07/25/2016 03:55 PM, Douglas R. Reno wrote: rhubarbpie...@gmail.com wrote: On 07/25/2016 03:44 PM, Douglas R. Reno wrote: rhubarbpie...@gmail.com wrote: On 07/22/2016 05:38 PM, Douglas R. Reno wrote: Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: I've recently compiled Midori and

Re: [blfs-support] Midori startup errors.

On 07/22/2016 05:38 PM, Douglas R. Reno wrote: Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: I've recently compiled Midori and receive the following upon starting with "midori": GLib-GIO-Message: Using the 'memory GSettings backend. Your settings will not be saved or shared with

[blfs-support] Midori startup errors.

I've recently compiled Midori and receive the following upon starting with "midori": GLib-GIO-Message: Using the 'memory GSettings backend. Your settings will not be saved or shared with other applications. (midori4:15329): Gtk-CRITICAL **: gtk_action_set_action_group: assertion

[blfs-support] Adwaita errors.

Adwaita lists no dependencies in the documentation. But if I compile Adwaita prior to compiling librsvg I receive the following: Can't load file: Unrecognized image file format Makefile:441: recipe for target 'install-data-local' failed make[3]: *** [install-data-local] Error 1

[blfs-support] Missing libgiognomeproxy.so after glib-networking installation.

I'm missing libgiognomeproxy.so after compiling glib-networking. The documentation indicates libgiognomeproxy.so and libgiognutls.so should be installed libraries. I do have the following: /usr/lib/gio/modules/libgiognutls.la /usr/lib/gio/modules/libgiognutls.so I see no errors in

[blfs-support] android on qemu/KVM?

Is anyone running android using qemu/KVM? I receive a never-ending android splash screen with: qemu -enable-kvm -hda vdisk.img \ -cdrom android-x86-4.4-r5.iso \ -boot d \ -m 384 I have less

Re: [blfs-support] "make PREFIX=/usr i \" - pciutils-3.4.1 BLFS 7.9 (downloadable documentation only)

On 03/20/2016 03:22 PM, Bruce Dubbs wrote: . . wrote: On 3/13/16, Bruce Dubbs wrote: rhubarbpie...@gmail.com wrote: The downloadable pciutils-3.4.1 BLFS documentation http://linuxfromscratch.org/blfs/downloads/stable/blfs-book-7.9-html.tar.bz2 seems to differ from

[blfs-support] "make PREFIX=/usr i \" - pciutils-3.4.1 BLFS 7.9 (downloadable documentation only)

The downloadable pciutils-3.4.1 BLFS documentation http://linuxfromscratch.org/blfs/downloads/stable/blfs-book-7.9-html.tar.bz2 seems to differ from the online versions. The second make block displays an unnecessary "i." make PREFIX=/usr i \ The online BLFS and development

[blfs-support] Qt 5 "-demosdir: invalid command-line switch" - BLFS 7.8/Development

Qt-5 documentation for the /usr option includes "-demosdir /usr/share/doc/qt5/demos" in the configuration. However, running .configure produces "-demosdir: invalid command-line switch" and ".configure --help" shows no -demosdir option. Should the line be removed? --

Re: [blfs-support] GConf-3.2.6 - No package 'libxml-2.0' found. BLFS 7.8

On 12/22/2015 06:23 PM, Ken Moffat wrote: On Tue, Dec 22, 2015 at 05:12:20PM -0600, rhubarbpie...@gmail.com wrote: On 12/22/2015 02:59 PM, Ken Moffat wrote: On Tue, Dec 22, 2015 at 01:36:49PM -0600, rhubarbpie...@gmail.com wrote: I receive "No package 'libxml-2.0' found" when compiling

Re: [blfs-support] GConf-3.2.6 - No package 'libxml-2.0' found. BLFS 7.8

On 12/22/2015 02:59 PM, Ken Moffat wrote: On Tue, Dec 22, 2015 at 01:36:49PM -0600, rhubarbpie...@gmail.com wrote: I receive "No package 'libxml-2.0' found" when compiling GConf-3.2.6. I assume the problem lies with libxml2-2.9.2 but see neither errors during compiling nor libxml-2.0 in the

[blfs-support] Python-2.7.10 requirement for Qt-5.5.0? BLFS 7.8

Should Python-2.7.10 be listed as a requirement for Qt-5.5.0? Compiling Qt-5.5.0 without Python-2.7.10 produces: Makefile:2492: recipe for target '.generated/RegExpJitTables.h' failed Makefile:49: recipe for target 'sub-qml-make_first-ordered' failed Makefile:45: recipe for target

Re: [blfs-support] Python-2.7.10 requirement for Qt-5.5.0? BLFS 7.8

On 12/14/2015 02:27 PM, Pierre Labastie wrote: On 14/12/2015 21:11, rhubarbpie...@gmail.com wrote: Should Python-2.7.10 be listed as a requirement for Qt-5.5.0? Compiling Qt-5.5.0 without Python-2.7.10 produces: Makefile:2492: recipe for target '.generated/RegExpJitTables.h' failed

  1   2   >