Re: [blfs-dev] Poppler build options

2014-09-30 Thread Fernando de Oliveira

On 30-09-2014 02:33, Christopher Gregory wrote:

Hello,

Whilst updating poppler, I noticed that there was an option displayed
during the configure stage of weather to use gtk-doc.

I noticed on the poppler page that we have no reference to enabling
gtk-doc like we do on other packages.

Is there a reason that I am unaware of, for not including this?

I enabled it, and it builds fine with it enabled.

Could someone please check, as it *may* well mean that we no longer have
to manually copy the documentation as the current instructions have.

I have not tested that part, as I wanted to leave well enough alone if the
manual copying is still needed, as it would have rendered the results for
generating the stats etc invalid.

Regards,

Christopher.


Thanks.

Fixed at 14431.

Included gtk-doc as optional dependency. The html API docs are generated 
by default, but not installed, so I included a command for this.


You may have seen many packages where gtk-docs is included as I did 
here, and the docs manually installed.



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


Re: [blfs-dev] WebKitGtk 2.6.0 Discussion please. (Was:... 4.6.0...)

2014-09-30 Thread Fernando de Oliveira

On 28-09-2014 13:59, Christopher Gregory wrote:

On Mon, September 29, 2014 5:19 am, Fernando de Oliveira wrote:

On 28-09-2014 11:19, Christopher Gregory wrote:





I am re-sending this as a new posting as I have just completed a
destdir installation using the following:

mkdir build && pushd build && cmake -DCMAKE_BUILD_TYPE=Release  \
-DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_SKIP_RPATH=ON   \
-DPORT=GTK  \
-DENABLE_GTKDOC=ON  \
-DUSE_SYSTEM_MALLOC=ON  \
-DCMAKE_INSTALL_DOCDIR=/usr/share/doc \
-DLIB_INSTALL_DIR=/usr/lib .. &&


make -j1

In addition to the above points, I notice that system_malloc is also
disabled by default.  Should this be included as I have done on my
system?


I left as optional. No strong reason for that. If anyone else answers 
your question, we may rethink, right?




Also the sbu value has doubled, at least for me with this build.


For me a little less than double, so we are in the same track.



Christopher, thanks for sharing all this with us.


Have not yet started to study this package. After Epiphany failed to
build in series 2.4, it is evident that WebKitGtk-2.6.0 it needs to go into
the book. However, the other packages have not yet been ported to this
version, thus WebKitGTK+-2.4.5 must stay in the book. This is being
discussed in ticket #5575:



Hello Fernando,

I already had in the back of my mind to put up a seperate page with this
application due to the incompatibility at this stage with most other
things.


OK. I misread that other post.


The new directories are:
   /usr/include/webkitgtk-4.0,
   /usr/lib/webkit2gtk-4.0,
   /usr/libexec/webkit2gtk-4.0,
   /usr/share/gtk-doc/html/webkit2gtk-4.0, and
   /usr/share/gtk-doc/html/webkitdomgtk-4.0

The library names are:
   libjavascriptcoregtk-4.0.so and
   libwebkit2gtk-4.0.so

The interesting thing is that with this particular version they have
created a new directory in libexec, whereas the previous version placed
the files directly in libexec, so this seems to be why we are going to be
able to install both versions side by side.

To this end, I have just finished creating a new page for this version,
however I have not yet run make validate and undoubtably changes will need
to be made as I may well not have everything up to the required BLFS
standards.


Our pages are a little different, much due to different styles and 
points of view, only.


Thank you very much.

Your posts were very useful and much facilitated my task. And some 
point, such as the libexec subdirectory, were very clarifying.



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


[blfs-dev] Gnome Keyring test suite

2014-09-30 Thread Christopher Gregory
Hello,

I think we may need to modify the instructions for testing gnome-keyring.

If the test suite is run on a fresh install with no previous version of
gnome-keyring installed you get 23 failures with the following error:

(gnome-keyring-daemon:14664): GLib-GIO-ERROR **: Settings schema
'org.gnome.crypto.cache' is not installed

If you run the test suite after gnome-keyring is installed you only get
two failures.

I have done a little research and there was a patch made some time last
year for an earlier version, however the list I found it on, did not have
the patch actually included.

This now leads to the next question.  Should we look for the patch and
include it, or should we just modify the instructions to say that if a
previous installation of gnome-keyring is not installed you get the above
mentioned error,  or should we just ignore adding a patch and modify the
instructions to say that the test suite needs to be run after
gnome-keyring is installed?

Regards,

Christopher.

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