On 20/04/2019 17:26, Bruce Dubbs via blfs-dev wrote: > On 4/20/19 9:30 AM, Pierre Labastie via blfs-dev wrote: >> On 20/04/2019 16:08, Pierre Labastie via blfs-dev wrote: >>> On 19/04/2019 18:41, Bruce Dubbs via blfs-dev wrote: >>>> On 4/19/19 9:55 AM, Pierre Labastie via blfs-dev wrote: >>>>> Hi, >>>>> >>>>> For testing latest changes to jhalfs, I am building a full blfs (systemd >>>>> [*]) book in a VM. I've ticked all the pages in the menu, shuffled the >>>>> "configuration" file obtained, then launched ./gen_pkg_book.sh. So the >>>>> build >>>>> order is supposed to respect dependency order, but otherwise is random. It >>>>> so happened that my build order is: >>>>> >>>>> X libraries ... imlib2 ... w3m, before gdk-pixbuf/gtk. >>>>> >>>>> So w3m wants to use imlib2 for displaying images, and imlib2 links to X >>>>> libraries. But -lX11 is not passed to the linker (it is the same problem >>>>> as >>>>> that fixed by one of the seds for w3m, but that sed fixes only gtk2 image >>>>> loader), so the build fails... >>>>> >>>>> I think one sed could do (but I have not tested it with gtk+-2): >>>>> sed '/IMGX11LDFLAGS=/s/`"/` -lX11"/' -i configure >>>>> >>>>> it would replace the one for gtk2, and add -lX11 to all the libraries >>>>> using >>>>> Xlib. The build passes and basic functionalities are there. I'm not able >>>>> to >>>>> display images in console mode, but it may be a VM problem, not >>>>> imlib2/w3m. >>>>> >>>>> Another possibility is to get rid of w3m, which is: >>>>> - old (no update since 2011) >>>>> - unable to display www.linuxfromscratch.org correctly (some characters >>>>> are >>>>> displayed as question marks; maybe we are missing a switch) >>>>> - having more and more issues with recent toolchains/toolkits >>>>> >>>>> We have two other text browsers in the book. >>>> >>>> I do not have a problem with archiving w3m. Currently the following pages >>>> reference it, all optional: gegl, mutt, PAM, docbook-utils, xmlto, >>>> xorg-libs, >>>> xdg-utils. >>>> >>>> We would need to change the references there to external. The package >>>> that is >>>> most problematic is PAM. w3m is the only internal package we have to >>>> optionally regenerate documentation. The alternative is elinks which is >>>> also >>>> external, but we can probably live with that. >>> >>> I've been able to regenerate the PAM doc with lynx instead of w3m: it needs >>> a >>> sed to configure: >>> sed -e 's/dummy links/dummy lynx/' \ >>> -e 's/-no-numbering -no-references/-force-html -stdin/' \ >>> -i configure >> >> Better: >> sed -e 's/dummy links/dummy lynx/' \ >> -e 's/-no-numbering -no-references/-force-html -nonumbers -stdin/' \ >> -i configure >> >>> >>> then remove the -no-regenerate-documentation switch from configure >>> invocation. >>> >>> and the doc is regenerated (provided you have xsltproc, libxml2, docbook, >>> and >>> lynx). >> >> Add fop for pdf generation, of course. >> >> Should we add this sed to the book, add lynx to optional (and make w3m >> external and remove elinks)? configure's logic with the sed is to use w3m if >> available, then lynx if available. links/elinks is not tested anymore. > > Sounds like a good plan to me. Please go ahead. >
Archived w3m and Added the sed at revision 21481 Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
