Re: startx
Chris Staub <[email protected]>
| Newsgroups | gmane.linux.lfs.general |
|---|---|
| Message-ID | <[email protected]> |
On 12/06/14 18:02, Walter Webb wrote: > I often wonder whether it is worthwhile to point out certain minor > problems, or does it just add to the noise on the internet. Also > if I do point them out, it is not always clear where (other than > lfs-chat) is the right place. > > startx only works if called from the shell. It is easy to correct. > A large number of newlines preceede "#!/bin/sh"; remove them. > It seems to be something the C preprocessor does to "startx.cpp" > in the xinit package. > > I see three possibilities: > 1. It's not a problem. > 2. It's an xinit problem. > 3. It's a GCC problem. > > In a case like this, I usually do nothing. I first encountered it > in LFS 7.4 with cpp (GCC) 4.8.1. I compiled "xinit" in LFS 7.3 > with cpp (GCC) 4.7.2, and startx did not have the newlines. I > seem to recall that I found several other files in XORG_PREFIX/bin > with initial newlines; also xinitrc. > > Recently, I saw some bugs on the net concerning KDM and startx. > It was not clear to me whether it was this simple problem, but > the startx situation was still present in BLFS 7.6. > > What is the best thing to do when I run into situations like this. I don't understand what "problem" you are referring to. Can you just summarize what the issue actually is? For example, if startx only works when started from the shell (and I'm not even sure if that's true) why exactly is that a problem or a bug? What are you trying to say? -- http://lists.linuxfromscratch.org/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page