Re: [blfs-dev] Jasper-2.0.0

[Douglas R. Reno]

Bruce Dubbs wrote:

Douglas R. Reno wrote:

Bruce Dubbs wrote:

Bruce Dubbs wrote:

John Burrell wrote:

I tried to install this version but:


the cmake command has

-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"


but libGL is provided by Mesa and libGLU is provided by glu


Neither is listed as a dependency.


The optional dependencies say 'Freeglut-3.0.0 (required for jiv)'.
Freeglut has mesa required and glu recommended.  The command 
explanation

says that the MAKE_EXE_LINKER_FLAGS option is required for jiv.

I'm not sure how to make this more clear.


Also the man pages seem to want to install in /usr/man


I couldn't find how to specify a MANDIR option. I listed the 
available

options using


It appears that we need

sed -i 's:man):share/man):' src/appl/CMakeLists.txt


But I have not tested that.


Now tested.  It should be:

sed -i 's:man):share/man/man1):' src/appl/CMakeLists.txt

  -- Bruce


I hate to stir up the age-old debate (or "flame war", if that's your
thing) of where dependencies belong, but do we really need to have
Freeglut in the optional dependencies? Last time that I had checked, our
"policy" was to have it so that only recommended and required 
dependencies
are needed to compile the package, with optional dependencies being 
needed

for optional functionality. In our case, people are attempting to build
this and don't have Freeglut installed, so they won't have GLU installed
either. Our instructions don't take this into account.

The specific portion that I am talking about here is
"-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"

In particular, two people have mentioned this to me on IRC. Archetech 
and
emmett1. Both of those people have told me that they didn't have 
freeglut
installed because it was only optional. I had to tell them both to 
install
GLU, and the problems disappeared. Their number one piece of feedback 
was

to make GLU recommended.

I guess this is a question of how we're supposed to do things. Should 
the

package be able to be compiled with only the recommended and required
dependencies, or do we assume that the user has everything under the sun
installed?

Also, considering that a whole program is missing if freeglut is 
missing,

should we or should we not promote that to recommended? That seems like
the package is missing some crucial functionality if we don't include
that. That would be like not installing gtk-update-icon-cache or 
something

like that!


If freeglut is not installed and CMAKE_EXE_LINKER_FLAGS is not used, 
then I'm pretty sure it builds OK.  I did not remove freeglut to test.


Many times users just want jasper for its library, so in that case 
neither CMAKE_EXE_LINKER_FLAGS nor freeglut (and thus libglu and libgl 
are not needed either).


I suppose we can remove the -DCMAKE_EXE_LINKER_FLAGS from the default 
instructions and expand the explanation.


That is what I'd recommend doing, just to clear up the confusion. 
There's been a ton of noise on IRC about it.

I can accept an alternative presentation.

  -- Bruce







--
Douglas R. Reno
--LFS/BLFS systemd maintainer

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

Re: [blfs-dev] Jasper-2.0.0

[John Burrell]

-snip-

>The specific portion that I am talking about here is
>"-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"
>
>In particular, two people have mentioned this to me on IRC. Archetech
>and emmett1. Both of those people have told me that they didn't have
>freeglut installed because it was only optional. I had to tell them both
>to install GLU, and the problems disappeared. Their number one piece of
>feedback was to make GLU recommended.
>
>I guess this is a question of how we're supposed to do things. Should
>the package be able to be compiled with only the recommended and
>required dependencies, or do we assume that the user has everything
>under the sun installed?
>
>Also, considering that a whole program is missing if freeglut is
>missing, should we or should we not promote that to recommended? That
>seems like the package is missing some crucial functionality if we don't
>include that. That would be like not installing gtk-update-icon-cache or
>something like that!

Whichever way you do it, the instructions should be consistent.
At the moment I contend that they are not because you have freeglut
as optional and the "-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"
in the cmake configure.
Either take that out of the configure and add it in the Commands Explanations
or make freeglut required.

jb.


--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
blfs-dev -- BLFS Development List - Linux From 
Scratch
lists.linuxfromscratch.org
The blfs-dev list is for discussion of BLFS Book development. To see the 
collection of prior postings to the list, visit the blfs-dev Archives.


FAQ: http://www.linuxfromscratch.org/blfs/faq.html
BLFS FAQ - Welcome to Linux From 
Scratch!
www.linuxfromscratch.org
Needless to say, if you originally put zlib in /usr/local or did something else 
different, you'll have to adjust those instructions accordingly.


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

Re: [blfs-dev] Jasper-2.0.0

[Bruce Dubbs]

Douglas R. Reno wrote:

Bruce Dubbs wrote:

Bruce Dubbs wrote:

John Burrell wrote:

I tried to install this version but:


the cmake command has

-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"


but libGL is provided by Mesa and libGLU is provided by glu


Neither is listed as a dependency.


The optional dependencies say 'Freeglut-3.0.0 (required for jiv)'.
Freeglut has mesa required and glu recommended.  The command explanation
says that the MAKE_EXE_LINKER_FLAGS option is required for jiv.

I'm not sure how to make this more clear.


Also the man pages seem to want to install in /usr/man


I couldn't find how to specify a MANDIR option. I listed the available
options using


It appears that we need

sed -i 's:man):share/man):' src/appl/CMakeLists.txt


But I have not tested that.


Now tested.  It should be:

sed -i 's:man):share/man/man1):' src/appl/CMakeLists.txt

  -- Bruce


I hate to stir up the age-old debate (or "flame war", if that's your
thing) of where dependencies belong, but do we really need to have
Freeglut in the optional dependencies? Last time that I had checked, our
"policy" was to have it so that only recommended and required dependencies
are needed to compile the package, with optional dependencies being needed
for optional functionality. In our case, people are attempting to build
this and don't have Freeglut installed, so they won't have GLU installed
either. Our instructions don't take this into account.

The specific portion that I am talking about here is
"-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"

In particular, two people have mentioned this to me on IRC. Archetech and
emmett1. Both of those people have told me that they didn't have freeglut
installed because it was only optional. I had to tell them both to install
GLU, and the problems disappeared. Their number one piece of feedback was
to make GLU recommended.

I guess this is a question of how we're supposed to do things. Should the
package be able to be compiled with only the recommended and required
dependencies, or do we assume that the user has everything under the sun
installed?

Also, considering that a whole program is missing if freeglut is missing,
should we or should we not promote that to recommended? That seems like
the package is missing some crucial functionality if we don't include
that. That would be like not installing gtk-update-icon-cache or something
like that!


If freeglut is not installed and CMAKE_EXE_LINKER_FLAGS is not used, then 
I'm pretty sure it builds OK.  I did not remove freeglut to test.


Many times users just want jasper for its library, so in that case neither 
CMAKE_EXE_LINKER_FLAGS nor freeglut (and thus libglu and libgl are not 
needed either).


I suppose we can remove the -DCMAKE_EXE_LINKER_FLAGS from the default 
instructions and expand the explanation.


I can accept an alternative presentation.

  -- 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] lxdm

[Douglas R. Reno]

On Fri, Dec 2, 2016 at 9:30 PM, Ken Moffat  wrote:

> On Tue, Nov 29, 2016 at 01:32:18AM +, Ken Moffat wrote:
> > On Mon, Nov 28, 2016 at 01:59:26PM -0700, Roger Koehler wrote:
> > > On Mon, Nov 28, 2016 at 1:55 PM, Douglas R. Reno 
> wrote:
> > > >
> > > >
> > > > On Mon, Nov 28, 2016 at 2:48 PM, Roger Koehler <
> roger.o.koeh...@gmail.com>
> > > > wrote:
> > > >>
> > > >> It crashes for me, too, with the latest xorg-server. If I go back to
> > > >> the previous version of xorg-server and libXfont, it works.
> > > >>
> > > >
> > > > I don't have xorg-server-1.19 on my workstation, I'm still at
> 1.18.x. I do
> > > > have the latest libXfont though.
> > >
> > > That may be the issue. Try libXfont 1.5.2.
> > I guess you meant "try libXfont-1.5.1 ?"  The new font lib is
> > libXfont2.
> >
> > I assume both need to be old - with 1.5.1 and 1.19.0 it is still
> > broken for me.
> >
> > Raised upstream at https://sourceforge.net/p/lxde/bugs/842/
> >
> I haven't made any progress on this.  According to upstream, lxdm
> doesn't reference libXfont, and it works on fedora25 with
> libXfont-1.5.2 and xorg-server-1.19.0.
>
> The segfault is after glibc seems to think my locale is
> ANSI_X3.4-1968 and failing to convert the UTF-8 message.  Root's
> locale when running lxdm via gdb was en_GB.UTF-8.
>
> Fedora are using lxdm-git : I tried that but it too segfaulted for
> me - I didn't bother to look at a bt for the moment, so I guess it
> might be different.
>
> I'm starting to wonder if something in current glibc broke this,
> but basically I'm flailing around and trying to clutch at straws.
>
> If I can't make any progress in the next few days, I guess I'd
> better raise a BLFS ticket asserting that this is broken.
>
>
Ken,

I'll have to build another DE that uses D-Bus when doing GNOME (and for
some other stuff).

Do you want me to build LXDM to round a complete LXDE installation and
report back to you ASAP?
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] lxdm

[Ken Moffat]

On Tue, Nov 29, 2016 at 01:32:18AM +, Ken Moffat wrote:
> On Mon, Nov 28, 2016 at 01:59:26PM -0700, Roger Koehler wrote:
> > On Mon, Nov 28, 2016 at 1:55 PM, Douglas R. Reno  
> > wrote:
> > >
> > >
> > > On Mon, Nov 28, 2016 at 2:48 PM, Roger Koehler 
> > > wrote:
> > >>
> > >> It crashes for me, too, with the latest xorg-server. If I go back to
> > >> the previous version of xorg-server and libXfont, it works.
> > >>
> > >
> > > I don't have xorg-server-1.19 on my workstation, I'm still at 1.18.x. I do
> > > have the latest libXfont though.
> > 
> > That may be the issue. Try libXfont 1.5.2.
> I guess you meant "try libXfont-1.5.1 ?"  The new font lib is
> libXfont2.
> 
> I assume both need to be old - with 1.5.1 and 1.19.0 it is still
> broken for me.
> 
> Raised upstream at https://sourceforge.net/p/lxde/bugs/842/
> 
I haven't made any progress on this.  According to upstream, lxdm
doesn't reference libXfont, and it works on fedora25 with
libXfont-1.5.2 and xorg-server-1.19.0.

The segfault is after glibc seems to think my locale is
ANSI_X3.4-1968 and failing to convert the UTF-8 message.  Root's
locale when running lxdm via gdb was en_GB.UTF-8.

Fedora are using lxdm-git : I tried that but it too segfaulted for
me - I didn't bother to look at a bt for the moment, so I guess it
might be different.

I'm starting to wonder if something in current glibc broke this,
but basically I'm flailing around and trying to clutch at straws.

If I can't make any progress in the next few days, I guess I'd
better raise a BLFS ticket asserting that this is broken.

ĸen
-- 
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.' -- Small Gods
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Jasper-2.0.0

[Chris Staub]

On 12/02/2016 05:59 PM, John Burrell wrote:

I tried to install this version but:


the cmake command has

-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"


but libGL is provided by Mesa and libGLU is provided by glu


Neither is listed as a dependency.


Freeglut is listed as an optional dependency, and it requires Mesa.



Also the man pages seem to want to install in /usr/man


I couldn't find how to specify a MANDIR option. I listed the available
options using


cmake -LH


but nothing to do with MANDIR appeared.


I gave up at this point.


jb.



It doesn't look like there is any option to specify mandir. I manually 
edited the installation location with a sed:


sed -i '/DESTINATION/s@man)@share/man/man1)@' ../src/appl/CMakeLists.txt
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Jasper-2.0.0

[Bruce Dubbs]

John Burrell wrote:

I tried to install this version but:


the cmake command has

-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"


but libGL is provided by Mesa and libGLU is provided by glu


Neither is listed as a dependency.


The optional dependencies say 'Freeglut-3.0.0 (required for jiv)'. 
Freeglut has mesa required and glu recommended.  The command explanation 
says that the MAKE_EXE_LINKER_FLAGS option is required for jiv.


I'm not sure how to make this more clear.


Also the man pages seem to want to install in /usr/man


I couldn't find how to specify a MANDIR option. I listed the available options 
using


It appears that we need

sed -i 's:man):share/man):' src/appl/CMakeLists.txt


But I have not tested that.

  -- Bruce

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

[blfs-dev] Jasper-2.0.0

[John Burrell]

I tried to install this version but:


the cmake command has

-DCMAKE_EXE_LINKER_FLAGS="-lGL -lGLU"


but libGL is provided by Mesa and libGLU is provided by glu


Neither is listed as a dependency.


Also the man pages seem to want to install in /usr/man


I couldn't find how to specify a MANDIR option. I listed the available options 
using


cmake -LH


but nothing to do with MANDIR appeared.


I gave up at this point.


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

Re: [blfs-dev] Sendmail page - Think we are missing a command

[akhiezer]

> From: Bruce Dubbs 
> Date: Thu, 1 Dec 2016 11:18:59 -0600
> Subject: Re: [blfs-dev] Sendmail page - Think we are missing a command
>
.
.
> # Put in place as root
> install -m755 /etc/mail


(install -d ...)


> install -m644 aliases /etc/mail/aliases
>



akh





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