[blfs-dev] Change in kernel DRM settings for 4.4.4

[Victor Wren]

In the development version of LFS, the kernel has been bumped up to 
4.4.4.  This has made a small change in frame buffer settings:


https://lists.freedesktop.org/archives/intel-gfx/2015-June/069292.html

In the development version of BLFS, the Xorg Drivers section shows 
setting CONFIG_DRM_I915_KMS.  This is no longer a valid setting in the 
4.4.4 kernel, as the i915 driver will only load if modesetting is 
enabled.  I have confirmed that it has been removed from the kernel 
config in 4.4.4


I also think it might be worth mentioning that these settings depend on 
PCI and AGP being enabled. On most machines with integrated Intel 
graphics, PCI is pretty certain to already be enabled, but I would have 
assumed that AGP went out with the passenger pigeon and failed to set 
it.  I'm trying to figure out the kernel docs, as the option I915 
apparently sets AGP_INTEL=y (convenient).  Still scratching my head over 
this syntax re: AGP:


"Depends on: HAS_IOMEM [=y] && DRM [=y] && X86 [=y] && PCI [=y] && (AGP 
[=y] || AGP [=y]=n)"


Does that mean "don't care" or "preference for [y] but [n] will work, or 
"if you set it [n] I'm gonna change it to [y]"?


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

Re: [blfs-dev] JSON-C 0.12 Make

[Victor Wren]

I understand.  That's why I was trying to BE a resource, doing thorough 
testing and research, presenting a complete fix, with documented 
sources, requiring no extra work.  I debated about submitting it, and 
clearly I made the wrong choice.  Considering that it's been two years 
since the last release, they obviously are not in a great hurry to crank 
out 0.13.


On 3/18/2016 13:24, Bruce Dubbs wrote:

Victor Wren wrote:
Going through the release version of BLFS7.9.  I notice the fix for 
JSON-C
dropping out of make with an "unused variable" warning in 
json_tokener.c.

BLFS fixes this by disabling -Werror on the whole build.   The day after
0.12 was released there was a commit for this that removed the unused
variable, allowing Make to finish, which seems like a more elegant fix.
Works either way.

https://github.com/json-c/json-c/commit/3859e99f50abe11a8dade28efa9ea3d99dfaac11 





We can't keep up with a package's development repository.  Not enough 
resources.


We will be able to pick this up with their next stable release.

  -- Bruce



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

[blfs-dev] S-Lang 'make install' needs -j1?

[ALZ (phyglos.org)]

Hi,

I was building S-Lang-2.2.4 for last BLFS and had some errors in "make 
install-all".


Downloaded the package again to assert the source was right but errors 
repeated. Downloaded a more recent version 2.3.0 and same errors were 
also there.


/usr/bin/install: cannot stat 
'/tmp/slang-2.3.0/src/elfobjs/libslang.so.2.3.0': No such file or directory

make[1]: *** [install-elf-and-links] Error 1
make[1]: *** Waiting for unfinished jobs
make: *** [install-elf] Error 2

The I decided to run the tests before doing "make install" and the 
errors appeared there. Provided that I was compiling with -j1 I went for 
that in the tests doing "make -j1 check" and those errors disappeared.


After checking the source code a few times and having no progress, I 
tried "make -j1 install"... and then I could build S-Lang-2.3.0.


Now I'm building this version with:

make -j1 DESTDIR=$BUILD_PACK install \
SLSH_DOC_DIR=/usr/share/doc/slang-2.3.0/slsh \
install_doc_dir=/usr/share/doc/slang-2.3.0   \

Using DESTDIR is not the culprit as fas as I can tell.

Has anybody found something like this? I don't recall any "make -j1 
install" needed in any other package.


Thanks!
Alz.


A few remarks about S-Lang-2.3.0:

* Notice "make install" instead of "make install-all". S-Lang now has an 
specific "make install-static" to build the static library and "make 
install" defaults to shared libs.


* MC builds and works well with this new version of S-Lang. Nano also 
does, but "set mouse" entry in /etc/nanorc gives a warning when building 
with-slang. (I had no gpm in this build; haven't tried with).


* The source code of S-Lang refers to ncurses5 in some places but my 
build had ncurses6 as per the book. This seems to have no influence in 
this issue and I haven't followed this other path further.

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

Re: [blfs-dev] A note on openssl changes

[Ken Moffat]

On Tue, Mar 15, 2016 at 05:10:16PM +, Ken Moffat wrote:
> On Mon, Mar 14, 2016 at 11:18:48PM -0500, Bruce Dubbs wrote:
> > The latest version of openssl disables SSLv2 by default.  This will cause
> > other packages to break.
> > 
> > I was upgrading wireshark and it failed because a Qt5 library required
> > SSLv2.  Fortunately a simple rebuild of Qt5 fixed the problem.
> > 
> > Just a heads up that other packages that use openssl may need to be rebuilt
> > also.
> > 
> > A quick search of BLFS to find where openssl is referenced shows 71 
> > packages.
> > 
> >   -- Bruce
> For ordinary desktop users, the known packages so far are curl,
> python2, python3.  Fortunately it is in for 7.9, so only people using
> older systems are affected.
> 
I went back to my -rc1 system to test something, and decided to use
links to find a different version at sourceforge (http://) - that
too needed to be recompiled.

ĸen
-- 
This email was written using 100% recycled letters.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] S-Lang 'make install' needs -j1?

[Bruce Dubbs]

ALZ (phyglos.org) wrote:



In the book there are several "make -j1" for compiling or "make -j1
check"
for testing clearly marked. However I haven't found any "make -j1
install"
yet. This is what I found unusual in this package.


Why would you ever want to do a parallel install?  How much time would
you save?  I understand the build and the checks, but the install is the
critical part and the time saved is not significant.



Well, the question is not what I want to do, but what happens in the
context of an LFS/BLFS build by following the instructions.

 From the point of view of an LFS builder, I understood (maybe
incorrectly) that I can set MAKEFLAGS to whatever I prefer and go using
the instructions as they are written. When a package has shown problems
with parallel makes, editors clearly advise so in the specific instruction
on the page. This is done with all "make" and "make check" that are know
to need that.


Yes, but we also say:  IF a problem occurs "the best way to proceed is to 
drop back to a single processor build."


I suppose we could say that we do not recommend MAKEFLAGS or -jN, N>1 for 
the install phase.



On your question about why using parallel install, I'd like to do so while
developing/improving my scripts. I've been doing so with LFS and haven't
had trouble until S-Lang.


Generally wouldn't you be installing to a DESTDIR for that?  I ran a test 
and for slang, the install at -j1 takes about 14 seconds because it wants 
to do some extra compilation in the install phase.  If you are changing 
code, you have most of the files already compiled.  My test when I 
modified a C file then shows make install to take less than a second at -j1.


  -- Bruce

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

Re: [blfs-dev] JSON-C 0.12 Make

[Bruce Dubbs]

Victor Wren wrote:


On 3/18/2016 13:24, Bruce Dubbs wrote:

Victor Wren wrote:

Going through the release version of BLFS7.9.  I notice the fix for JSON-C
dropping out of make with an "unused variable" warning in json_tokener.c.
BLFS fixes this by disabling -Werror on the whole build.   The day after
0.12 was released there was a commit for this that removed the unused
variable, allowing Make to finish, which seems like a more elegant fix.
Works either way.

https://github.com/json-c/json-c/commit/3859e99f50abe11a8dade28efa9ea3d99dfaac11




We can't keep up with a package's development repository.  Not enough
resources.

We will be able to pick this up with their next stable release.


> I understand.  That's why I was trying to BE a resource, doing thorough
> testing and research, presenting a complete fix, with documented sources,
> requiring no extra work.  I debated about submitting it, and clearly I
> made the wrong choice.  Considering that it's been two years since the
> last release, they obviously are not in a great hurry to crank out 0.13.

Please don't top post.

Don't get me wrong.  We appreciate posts like yours.  It's just that there 
are a lot of major updates going on and the fix you propose requires a 
patch and we prefer to avoid those.  The current instructions work and the 
change needed from our point of (building) view is more complex than what 
we have now.


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

Re: [blfs-dev] Change in kernel DRM settings for 4.4.4

[Ken Moffat]

On Fri, Mar 18, 2016 at 07:58:50AM -0500, Victor Wren wrote:
> In the development version of LFS, the kernel has been bumped up to 4.4.4.
> This has made a small change in frame buffer settings:
> 
> https://lists.freedesktop.org/archives/intel-gfx/2015-June/069292.html
> 
> In the development version of BLFS, the Xorg Drivers section shows setting
> CONFIG_DRM_I915_KMS.  This is no longer a valid setting in the 4.4.4 kernel,
> as the i915 driver will only load if modesetting is enabled.  I have
> confirmed that it has been removed from the kernel config in 4.4.4
> 
> I also think it might be worth mentioning that these settings depend on PCI
> and AGP being enabled. On most machines with integrated Intel graphics, PCI
> is pretty certain to already be enabled, but I would have assumed that AGP
> went out with the passenger pigeon and failed to set it.  I'm trying to
> figure out the kernel docs, as the option I915 apparently sets AGP_INTEL=y
> (convenient).  Still scratching my head over this syntax re: AGP:
> 
> "Depends on: HAS_IOMEM [=y] && DRM [=y] && X86 [=y] && PCI [=y] && (AGP [=y]
> || AGP [=y]=n)"
> 
> Does that mean "don't care" or "preference for [y] but [n] will work, or "if
> you set it [n] I'm gonna change it to [y]"?
> 
> Victor Wren

Commenting on the syntax only (my intels have pulled their kernel
configs forward from past versions with make oldconfig) :

It doesn't seem to make sense in that form, but the final =n is, I
think, saying that _unless_ you set AGP to =y (or perhaps =m, the ||
implies two alternatives) then whichever option that 'help' relates
to cannot be selected.

ĸen
-- 
This email was written using 100% recycled letters.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] S-Lang 'make install' needs -j1?

[ALZ (phyglos.org)]

On 03/19/2016 12:07 AM, Ken Moffat wrote:

On Fri, Mar 18, 2016 at 11:14:05PM +0100, ALZ (phyglos.org) wrote:

On 03/17/2016 11:38 PM, Ken Moffat wrote:

On Thu, Mar 17, 2016 at 11:07:34PM +0100, ALZ (phyglos.org) wrote:


Has anybody found something like this? I don't recall any "make -j1 install"
needed in any other package.


I've never used more than -j1 when installing, I regard it as not
worth the risk.  Similarly, for tests (unless somebody has noted
that they work ok like that).

There is/was a ticket raised against openssl for 7.10, noting that
parallel install sometimes failed.

ĸen



Yes, doing "-j1" for all packages is a good choice, as it is running all
available tests before a "release" build. Long build, but no doubts about
how it was build. (I think LFS SBUs are also calculated for -j1)



To be clear: I use -j1 for tests (if I run them) unless advised that
running in parallel is ok and useful (for gcc the tests run as
normal, but the results are all jumbled up and the contrib file that
used to sort out the results no longer seems to do anything) and for
install.



I see your point and I think I'll take some hint to test in my build 
process.


But that's the opposite the book (it seems to me) does. By advising in 
specific spots when parallel "make" or "make chech" are known to fail, 
one can infer that setting MAKEFLAGS "globally" is safe along the rest 
of the instructions.



For everything else in a normal build I normally use -JN [ for
values of N between 3 and 8, depending on what else I am doing ]
when I am building the package.

For the book, most of the time I use -j1 to get an accurate
measurement (based on how long it took the new system to repeat an
SBU : usually, slower with each new toolchain, and not consistent to
more than about 5 seconds even for the same toolchain) on an SSD.

At the moment, one of the desktop packages for which I have a ticket
(shared-mime-info-1.6) builds ok with -j8 on my haswell (I very much
doubt that more than 2 or 3 jobs actually run in parallel) but can
only build if I force -j1 on my SandyBridge i3 and my Kaveri A10.



I can't recall which one, but some other "essential" package from FLS 
(not BLFS) does not build for me in parallel. I assumed it was a local 
issue and haven't asked about that and moved on.



In the book there are several "make -j1" for compiling or "make -j1 check"
for testing clearly marked. However I haven't found any "make -j1 install"
yet. This is what I found unusual in this package.



As I said, I only ever use -j1 for installs (unless a package decides
to override that: not everything obeys the user's CFLAGS, that does also
apply to MAKEFLAGS in at least one weird package which is not in the
book [ MediaInfo ] - I hack it to use what I tell it, because on the
i3 (again) it brought the box to its knees running too many jobs in
the build).



When I put my hat of LFS builder I try to stick as much as possible to 
the book. Whenever I depart I accept the price to pay. I'm now having 
trouble in compiling openssl with ccache enabled and I don't expect the 
book or the editors to solve that.



Anyways, looks like both Arch as well as Gentoo have chosen to build this
package forcing -j1 and ignoring any user defined MAKEFLAGS. They probably
had this issue before.

Thanks!
Alz.


Sounds likely - I don't think many people have any need for it.
/me goes off to look at my scripts: I've been using -j1 to build
s-lang since last September, I presume I needed that when I was
testing gnome for 7.8 on my i3.


So it seems to me that the question regarding S-Lang is solved. And I've 
taken some ideas to test in my build process. That's good business. ;-)


Thank you.
Alz.




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

Re: [blfs-dev] [blfs-book] r16986 - in trunk/BOOK: . general/graphlib introduction/welcome

[Ken Moffat]

- Forwarded message from Ken Moffat  -

Yet again, my replies to -book seem to not appear.  A quick check
showed higgs is idle, so I guess this got filtered to /dev/null.
Resending to -dev using my lfs id.

Date: Thu, 17 Mar 2016 19:06:05 +
From: Ken Moffat 
To: BLFS Book Maintenance List 
Subject: Re: [blfs-book] r16986 - in trunk/BOOK: . general/graphlib 
introduction/welcome
User-Agent: Mutt/1.5.24 (2015-08-30)

On Thu, Mar 17, 2016 at 11:29:01AM -0300, Fernando de Oliveira wrote:
> Em 20-02-2016 03:34, k...@higgs.linuxfromscratch.org escreveu:
> > Author: ken
> > Date: Fri Feb 19 22:34:03 2016
> > New Revision: 16986
> > 
> > Log:
> > poppler-0.41.0 : why does editing always take so long ?
> 
> less than 0.4SBU for the tests.
> 
That was a comment on the overall process, not on the test suite.

> > @@ -6,10 +6,10 @@
> 
> 
> > 

Re: [blfs-dev] S-Lang 'make install' needs -j1?

[ALZ (phyglos.org)]

In the book there are several "make -j1" for compiling or "make -j1
check"
for testing clearly marked. However I haven't found any "make -j1
install"
yet. This is what I found unusual in this package.


Why would you ever want to do a parallel install?  How much time would
you save?  I understand the build and the checks, but the install is the
critical part and the time saved is not significant.



Well, the question is not what I want to do, but what happens in the 
context of an LFS/BLFS build by following the instructions.


From the point of view of an LFS builder, I understood (maybe 
incorrectly) that I can set MAKEFLAGS to whatever I prefer and go using 
the instructions as they are written. When a package has shown problems 
with parallel makes, editors clearly advise so in the specific 
instruction on the page. This is done with all "make" and "make check" 
that are know to need that.


However I haven't seen any "make -j1 install" in the pages of any of the 
packages I've built so far, so when I found trouble installing  S-Lang 
without "-j1" I asked about that.


Of course, it can just be an issue with my specific system or I may have 
misunderstood something in the book. But, as an LFS reader, I could 
expect that if "-j1" is explicitly advised on other instructions maybe 
in this case this package could also need an explicit "make -j1 install" 
advised in the book, provided that this issue can be confirmed for this 
package by others builds on other systems.



On your question about why using parallel install, I'd like to do so 
while developing/improving my scripts. I've been doing so with LFS and 
haven't had trouble until S-Lang.


Sure that's not the best idea ever for building an working LFS system, 
I'm aware of that, but when I focus on scripts refactoring and testing 
'configure' options for added packages I just want the package quickly 
built over and over on a development system.


Later, when it's time for a "good" build I set my mind to conservative 
mode, and then all checks are run (even in the toolchain), all logs go 
verbose and also from what I'm learning now all "make install" would 
better go on strict diet.


Thank you.
Alz.








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

Re: [blfs-dev] Change in kernel DRM settings for 4.4.4

[Pierre Labastie]

On 18/03/2016 13:58, Victor Wren wrote:


"Depends on: HAS_IOMEM [=y] && DRM [=y] && X86 [=y] && PCI [=y] && 
(AGP [=y] || AGP [=y]=n)"


Does that mean "don't care" or "preference for [y] but [n] will work, 
or "if you set it [n] I'm gonna change it to [y]"?



According to
https://www.kernel.org/doc/Documentation/kbuild/kconfig-language.txt,
the above expression is not really a boolean expression: it can return
three values : n (or 0), m (or 1), y (or2), and all its subexpressions can
also have three values.

The expression "e1 = e2 " evaluates to 0 if e1 is not equal to e2,
and 2 if e1 and e2 are equal.
The expression e1 && e2 means "min(e1,e2)".
The expression e1 || e2 means "max(e1,e2)".
a symbol is converted to its value, so:
- if you have not selected AGP, it is n
- if you have selected it as a module it is m
- if you have selected it to y it is y
so (AGP || AGP=n) means:
y if AGP=y or n
m if AGP=m

Now the whole expression means :
if any symbol (aside of AGP) is n : the expression is n
(the symbol is not shown)
if some or all symbols are m and others are y : the
symbol is shown with angle brackets, and you can
select only as m
if all symbols are y, but AGP is y or n: the symbol is
shown with square brackets, and you can select it
with y or m.

Regards
Pierre


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

Re: [blfs-dev] Qupzilla-1.8.9 broken with qtwebkit-5.6.0

[Fernando de Oliveira]

Em 19-03-2016 12:27, Fernando de Oliveira escreveu:
> 
> 
> 

Please, disregard. It was supposed to be a private message.

-- 
[]s,
Fernando, aka Sísifo
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-dev] Qupzilla-1.8.9 broken with qtwebkit-5.6.0

[Fernando de Oliveira]

-- 
[]s,
Fernando, aka Sísifo
cd src/lib/ && ( test -e Makefile || /opt/qt5/bin/qmake /tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/lib/lib.pro -o Makefile ) && make -f Makefile 
make[1]: Entering directory '/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/lib'
make[1]: Nothing to be done for 'first'.
make[1]: Leaving directory '/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/lib'
cd src/main/ && ( test -e Makefile || /opt/qt5/bin/qmake /tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/main/main.pro -o Makefile ) && make -f Makefile 
make[1]: Entering directory '/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/main'
g++ -Wl,-O1 -Wl,--enable-new-dtags -Wl,-rpath-link,/opt/qt5/lib -o ../../bin/qupzilla ../../build/main.o   /tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so -L/opt/qt5/lib -lQt5WebKitWidgets -lQt5PrintSupport -lQt5Widgets -lQt5WebKit -lQt5Gui -lQt5Network -lQt5Sql -lQt5Script -lQt5DBus -lQt5Core -lGL -lpthread 
/usr/bin/ld: warning: libANGLE.so.1, needed by /opt/qt5/lib/libQt5WebKitWidgets.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libWebKit1.so.1, needed by /opt/qt5/lib/libQt5WebKitWidgets.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libWebCore.so.1, needed by /opt/qt5/lib/libQt5WebKitWidgets.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libJavaScriptCore.so.1, needed by /opt/qt5/lib/libQt5WebKitWidgets.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libWTF.so.1, needed by /opt/qt5/lib/libQt5WebKitWidgets.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libleveldb.so.1, needed by /opt/qt5/lib/libQt5WebKit.so, not found (try using -rpath or -rpath-link)
../../build/main.o: In function `qupzilla_signal_handler(int) [clone .part.13]':
main.cpp:(.text+0x8d7): undefined reference to `qWebKitVersion()'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::setDevicePixelRatio(float)'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::selectedText() const'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::defaultUserAgentString()'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebHistoryInterface::setDefaultInterface(QWebHistoryInterface*)'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebHistory::backItem() const'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::handleShortcutOverrideEvent(QKeyEvent*)'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebHistory::canGoForward() const'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebHistory::forward()'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebFrameAdapter::handleGestureEvent(QGestureEventFacade*)'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebHitTestResultPrivate::operator=(QWebHitTestResultPrivate const&)'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebSettings::fontSize(QWebSettings::FontSize) const'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebFrameAdapter::ensureAbsoluteUrl(QUrl const&)'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::inputMethodQuery(Qt::InputMethodQuery) const'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `typeinfo for QtPluginWidgetAdapter'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `operator<<(QDataStream&, QWebHistory const&)'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::focusOutEvent(QFocusEvent*)'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebHistory::items() const'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebHistoryInterface::qt_metacall(QMetaObject::Call, int, void**)'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::dragUpdated(QMimeData const*, QPoint const&, QFlags)'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebSettings::globalSettings()'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebFrameAdapter::hasView() const'
/opt/qt5/lib/libQt5WebKitWidgets.so: undefined reference to `QWebPageAdapter::inputMethodEvent(QInputMethodEvent*)'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to `QWebElementCollection::QWebElementCollection(QWebElementCollection const&)'
/tmp/porg-build-2016.03.19-10h21m51s/qupzilla-1.8.9/src/../bin/libQupZilla.so: undefined reference to 

[blfs-dev] BLFS 7.9 missing dependency on GLibmm-2.46.3

[Victor Wren]

I'm building a 32-bit version of BLFS on an Intel platform.  I've spent 
most of the day trying to get a clean make check out of GLibmm, and it 
kept coming up with a fail on "giomm_tls_client/test".  Mentions of that 
exact error in the BLFS mailing list archive say that the failure 
indicates a missing GnuTLS, but I knew that didn't apply to my 
situation. I rebuilt GnuTLS multiple times, even going back and 
rebuilding its dependencies.


After doing some research, I found a mention of glib-networking 
implementing the TLS back-end ( 
http://code.metager.de/source/xref/gnome/Bindings/glibmm/tests/giomm_tls_client/main.cc, 
which was probably in my source tree, but was easier to find on the 
Internet, oddly enough).  It would seem that GLibmm depends on 
glib-networking to register that the GnuTLS backend is available. After 
I installed glib-networking, make check on GLibmm ran through without an 
error.  It would seem that whether or not GlibMM  is functional without 
glib-networking, it may/will fail at least that test if it doesn't find it.


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

[blfs-dev] qtwebkit

[Bruce Dubbs]

Trolltech has released qtwebkit-opensource-src-5.6.0.tar.xz. 
(https://download.qt.io/community_releases/5.6/5.6.0/)


It is used for libprocessui from libksysguard (I don't think it is 
required) in plasma and kf5 pim (which is not yet in the book)


The build instructions are really non standard.  What I had to do was:

source setqt5
QT5PREFIX=$BUILDDIR/install

sed -i '/Werror/ s/isEqual/#isEqual/' \
   Tools/qmake/mkspecs/features/unix/default_post.prf &&

syncqt.pl -version 5.6.0 Source/sync.profile &&

Tools/Scripts/build-webkit --prefix=$QT5PREFIX \
   --qt\
   --makeargs=-j4  \
   --no-webkit2&&

# test with 'Tools/Scripts/run-launcher'

sudo make -C WebKitBuild/Release install


It does not seem to support DESTDIR or equivalent.  When I built, it 
wanted to delete things from my Qt5 directory, specifically 
/opt/qt5/include/ files, even though I told it to install in /tmp.


I did -makeargs=-j4 for timing purposes.  If omitted, it uses all cores on 
the system.


Some statistics:

SBU: 18.2  (1689.8 seconds)
Tarball size: 33.667 MB
Build Size: 837M
Install size: 163M (stripped)

The build/install log file is 44M

It appears to overwrite a lot of qt5 files.  At least the timestamps have 
been updated.


Dependencies:

Qt version 5.0.0 or later
gperf (v3.0 or later)
sqlite (development files)
fontconfig (development files)
xrender (development files)
phonon (development files)
libjpeg (development files)
libpng (development files)

Even with the --prefix above, it installs some files in the qt5 directory. 
 In my case libQt5WebKit.so.5.6.0 is installed in /opt/qt5/lib.


The bottom line is that --prefix is not really honored but the location of 
qt5 is used for the actual libQt5WebKit.so library and supporting files.


Right now for Qt4 we include qtwebkit on the Qt4 page.  I'm inclined to 
put this on a separate page immediately below Qt5.


Comments?

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