On 2/18/19 12:46 PM, Roger Koehler via blfs-dev wrote:
I built a new SysV system from scratch using jhalfs with the latest svn release, and I am still unable to build Qt. I'm surprised that no one else has run into this issue (see my recent posts on this list).

I have used all of the recommended and required dependencies and only minor edits to the scripts generated by jhalfs so as not to need doxygen or texlive or, in the case of highlight, qt.

It might help to see the script you actually used. I built qt over the weekend with no problems. I used:

VERSION=5.12.1

export QT5PREFIX=/opt/qt5
sudo rm -rf /opt/qt-$VERSION $QT5PREFIX
sudo mkdir -p $QT5PREFIX


find . -name "*.pr[io]" | xargs sed -i 's/python/&3/' &&

    ./configure -prefix $QT5PREFIX   \
                -sysconfdir /etc/xdg \
                -confirm-license     \
                -opensource          \
                -dbus-linked         \
                -openssl-linked      \
                -system-harfbuzz     \
                -system-sqlite       \
                -nomake examples     \
                -no-rpath            \
                -skip qtwebengine    &&

make -j4 &&

$SUDO make install              &&

$SUDO find $QT5PREFIX/ -name \*.prl \
      -exec sed -i -e '/^QMAKE_PRL_BUILD_DIR/d;' {} \; &&

$SUDO mv $QT5PREFIX /opt/qt-$VERSION &&
$SUDO ln -svfn qt-$VERSION /opt/qt5

I did make two departures from a default build: 1) I used Linux 4.9.158, and 2) I mounted /var to a different partition and used /var/lib/sources for my source archive. /opt is at the same partition as /usr (root).

I don't see where that would make a difference.

The first thing I did after LFS was complete was install DHCP client and wpa_supplicant (without dbus or qt) so that I could wirelessly connect to the internet. Then I rebuilt shadow with Pam and Cracklib and Python3. Then ALSA, followed by X Windows.

The very next thing I wanted to do is build Qt. All dependencies built fine, but then Qt bombed out at the exact same place as before: vulkan.

After it stops, build again at -j1 so you can find where the build errors out. We need to see that to help.

Let me note that that the space required is very large. Make sure you are not running out of disk space or, less likely, memory.

  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to