Hi I have the same problem with icons when I build kde plasma.Some icons are missing after compilation and first run. I load icon theme e.g.papyrus from system settings. Anyway Plasma works very well in blfs 8 thanks to all of you. Riccardo
Il 13 giu 2017 9:00 PM, <[email protected]> ha scritto: Send blfs-support mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.linuxfromscratch.org/listinfo/blfs-support or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of blfs-support digest..." Today's Topics: 1. Testing OpenJDK Problem (Alan Feuerbacher) 2. Re: texlive doesn't create pdflatex -> pdftex symlink (Sync Ak Belore) 3. Re: Testing OpenJDK Problem (Pierre Labastie) 4. Runtime dependency? (It doesn't say.) (Paul Rogers) 5. Re: Runtime dependency? (It doesn't say.) (Bruce Dubbs) ---------------------------------------------------------------------- Message: 1 Date: Mon, 12 Jun 2017 13:22:22 -0600 From: Alan Feuerbacher <[email protected]> To: BLFS Support List <[email protected]> Subject: [blfs-support] Testing OpenJDK Problem Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed In BLFS systemd version 8.0, I'm trying to test JVM in OpenJDK-1.8.0.121 using the method shown in the BLFS book, where Xvfb is used. The last of the series of commands it: xhost + which returns the error: xhost: unable to open display ":20" I've run through each command line individually to see if they execute properly -- no issues until the last one. I've rebooted the machine and recompiled OpenJDK, with the same result. Could there be some kind of authorization problem with X? I found a reference on the Net to such a problem from 2008, which was fixed by messing with the /etc/X11/xdm/xdm-config, but there's no such file on my machine, nor any reference in the BLFS book to such an animal. After executing all the command lines I tried to see if Xvfb and twm were running, so: ps -a | grep -i xvfb Returned nothing. ps -a | grep -i twm Returned a single instance of twm running in tty2, as expected, since I started twm in Console 2. Ideas? Probably something simple. Alan ------------------------------ Message: 2 Date: Mon, 12 Jun 2017 17:49:15 -0400 From: Sync Ak Belore <[email protected]> To: BLFS Support List <[email protected]> Subject: Re: [blfs-support] texlive doesn't create pdflatex -> pdftex symlink Message-ID: <cajyuf+m2sbh1u7mrqs83ayjrq3vzuaw7uhhbe34-0hvxtse...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Thank you very much, I think latex works as I expected for now, the but next time I build it I will take care with `ldconfig`, just to clarify I was trying to build both the 2016 version then the 2017 version with both I have the same problem, and of course I (re)run a couple of times because error so probably there was other mistake from my part. Will continue with other packages, thank you again for your time 2017-06-11 17:28 GMT-04:00 Ken Moffat <[email protected]>: > On Sun, Jun 11, 2017 at 07:41:36PM +0200, Pierre Labastie wrote: > (some detailed information which helped me understand the problem, > but which I have now snipped) > > Summary: I think running plain 'ldconfig' is the problem, and that > texlive doesn't need to know about anything more. > > Sorry for the delay in replying, I was looking at the things I > upgrade for a new firefox (due this week, I think) and testing out > nss, then catching up with food and TV/recording. I started a > reply, but I've had to build texlive again to check things. > > The thing we run before 'make texlinks' is ldconfig. That is in > /sbin, so the '&&' means things will stop at that point for those > who do not have that on their PATH, I think ? > > To fix that, I will change it to invoke /sbin/ldconfig like we do > for e.g. Xorg Libraries. I think that should solve the problem. > > There now follows a breakdown of what *I* think 'make texlinks' > does. TLDR: ln -s (for progs and scripts,if the links do not yet > exist, or trash them if they do). > > For 'make texlinks', the top-level Makefile has > > texlinks_dir = texk/texlive/tl_scripts > > and > > texlinks: > cd $(texlinks_dir) && $(MAKE) $(AM_MAKEFLAGS) run-texlinks > > and also > > LN_S = ln -s > > When that file has been created below the tex-build directory, it > eventually invokes the *links.am files in the am directory below the > top source directory (i.e. ../am/ from texlive-build). > > For programs (bin_links.am) > > install-bin-links: > if !WIN32 > $(MKDIR_P) $(DESTDIR)$(bindir) > @cd $(DESTDIR)$(bindir) && \ > for s in $(bin_links); do \ > link=`echo $$s | sed 's,.*:,,'`; \ > file=`echo $$s | sed 's,:.*,,'`; \ > rm -f $$link; \ > echo "creating link '$$link' -> '$$file'"; \ > $(LN_S) $$file $$link || exit 1; \ > done > endif !WIN32 > > similarly for header links (hdr_links.am) (are there any?) > > all-local: > @for file in $(hdr_links); do \ > test -f $$file || continue; \ > inst=`echo $$file | sed -e 's/^.*\///'`; \ > test -f $$inst || { \ > rm -f $$inst; \ > if $(AM_V_P); then echo "$(LN_S) $$file $$inst"; \ > else echo " INST $$inst"; fi; \ > $(LN_S) $$file $$inst; } || exit 1; \ > done > > for man pages (man1_links.am) > > install-man1-links: > @cd $(DESTDIR)$(man1dir) && \ > for s in $(man1_links); do \ > link=`echo $$s | sed 's,.*:,,'`; \ > file=`echo $$s | sed 's,:.*,,'`; \ > rm -f $$link.1; \ > echo "creating link '$$link.1' -> '$$file.1'"; \ > echo ".so man1/$$file.1" >$$link.1; \ > done > > and for scripts (script_links.am) it runs install-links for lua, > perl (pl), shell (sh) : > > install-links: > @relpath="$(top_srcdir)/../../build-aux/relpath"; \ > test -r $$relpath || { \ > echo 'script_links.am:install-links: could not find > relpath script'; \ > exit 1; \ > }; \ > REL=`$(SHELL) $$relpath '$(DESTDIR)' '$(bindir)' > '$(datarootdir)'`; \ > if test -z "$$REL"; then \ > echo 'script_links.am:install_links: unable to compute > relative path for linked $(TYPE) scripts' >&2; \ > exit 1; \ > fi; \ > cd $(DESTDIR)$(bindir) && \ > for f in $($(TYPE)_scripts); do \ > rm -f $$f; \ > if $(AM_V_P); then echo "creating link '$$f' -> > '$$REL/$(scriptsdir)/$$f.$(EXT)'"; \ > else echo " LINK $$f"; fi; \ > $(LN_S) $$REL/$(scriptsdir)/$$f.$(EXT) $$f || exit 1; \ > done > > This also means that the original poster (Diego) will not have run > any of the commands in the block after 'ldconfig', so that he does > not have any perl modules in /opt/texlive/2017/tlpkg/TeXLive/ (or > 2016 if that was what he built). > > IFF (and only if) that is true, he can as root run > /sbin/ldconfig && > make texlinks && > (etc.) > > and then he should probably also rerun mktexlsr, fmt-util-sys --all, > mtxrun --generate to be sure those fix up everything. > > ĸen > -- > I live in a city. I know sparrows from starlings. After that > everything is a duck as far as I'm concerned. -- Monstrous Regiment > -- > http://lists.linuxfromscratch.org/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfromscratch.org/pipermail/blfs-support/ attachments/20170612/cec6950e/attachment-0001.html> ------------------------------ Message: 3 Date: Tue, 13 Jun 2017 15:05:09 +0200 From: Pierre Labastie <[email protected]> To: BLFS Support List <[email protected]> Subject: Re: [blfs-support] Testing OpenJDK Problem Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 On 12/06/2017 21:22, Alan Feuerbacher wrote: > In BLFS systemd version 8.0, I'm trying to test JVM in OpenJDK-1.8.0.121 using > the method shown in the BLFS book, where Xvfb is used. > > The last of the series of commands it: > > xhost + > > which returns the error: > > xhost: unable to open display ":20" > > I've run through each command line individually to see if they execute > properly -- no issues until the last one. > > [...] Looks like Xvfb did not start. Did you have a look at the "Xvfb.out" file? Also, do you have a file Xvfb.pid? Same questions of course for twm.out and twm.pid... As you may have seen, there are no double ampersand (&&) in that sequence of commands. They can't be used here, because they break the behavior of the single ampersand (&). That's all I can say now... Pierre ------------------------------ Message: 4 Date: Tue, 13 Jun 2017 10:16:02 -0700 From: Paul Rogers <[email protected]> To: blfs <[email protected]> Subject: [blfs-support] Runtime dependency? (It doesn't say.) Message-ID: <1497374162.3252366.1008174832.409bd...@webmail.messagingengine.com> Content-Type: text/plain; charset="utf-8" All the icon themes should be identified as runtime dependencies, shouldn't they? (I've just finished building my ~430 packages for 7.10, and am only now trying to work on "appearance" issues in bare fluxbox, deciding on things like icons and themes and hoping it's not too late. Firefox is also missing a few icons.) -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - Email service worth paying for. Try it for free ------------------------------ Message: 5 Date: Tue, 13 Jun 2017 12:36:54 -0500 From: Bruce Dubbs <[email protected]> To: BLFS Support List <[email protected]> Subject: Re: [blfs-support] Runtime dependency? (It doesn't say.) Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8; format=flowed Paul Rogers wrote: > All the icon themes should be identified as runtime dependencies, > shouldn't they? (I've just finished building my ~430 packages for 7.10, > and am only now trying to work on "appearance" issues in bare fluxbox, > deciding on things like icons and themes and hoping it's not too late. > Firefox is also missing a few icons.) Icons should all be runtime. I can't think of a reason why they wouldn't be. It really does not matter whether they are done before or after the individual packages. I've run into the missing icons issue too. It does depend on the theme to some extent. The easy thing to do is to just add all the icon packages. -- Bruce ------------------------------ Subject: Digest Footer -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page ------------------------------ End of blfs-support Digest, Vol 828, Issue 1 ********************************************
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
