Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Bruce Dubbs

On 1/4/20 7:45 PM, Ken Moffat wrote:

On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote:


On 1/4/20 1:45 PM, Flareon Zulu wrote:


On January 4, 2020, at 09:47, Scott Andrews
 wrote:


Anyone have this error?
ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
m-regex.o mbrlen.o regex.o
ranlib libgrep.a
make[3]: Leaving directory
'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
Making all in src
here=`pwd`; \
cd ../../libtextstyle/lib && \
   /usr/bin/make install-nobase_includeHEADERS
install-nobase_nodist_includeHEADERS includedir="$here"
make[3]: *** No rule to make target 'install-nobase_includeHEADERS'.

Stop.

make[2]: *** [Makefile:3955: textstyle.h] Error 2
make[1]: *** [Makefile:2173: all-recursive] Error 1
make: *** [Makefile:2041: all] Error 2
Didn't see anything on the list about this
Gettext-0.19.8.1 is ok
--




Especially in light of this: https://savannah.gnu.org/bugs/?56333

It seems there could be an issue with build order, essentially. I didn't
have an issue, but some people online have had this happen, they're just
not on this list.

Flareon Zulu


Could very well be,  I will follow up on the link you posted and see if I
caqn make sense in it.



The usual workaround for what that sounds like is "make -j1".
Apologies if you are already doing that.  My most recent example of
that was in bison on a Skylake (an i3 so I'd been running make -j4 :
perhaps -j3 or -j2 might have sufficed).  On other machines (haswell
i7, ryzen 3400G) make -j8 was fine.  Modern CPUs can be a pain.

And that is another thing to learn from LFS - ISTR that dropping
back to -j1 in case of problems is mentioned in the FAQ.


In section 4.5. About SBUs, the last sentence in the note:

"If you run into a problem with a build step, revert back to a single 
processor build to properly analyze the error messages."


This may be the cause of the error, but I think it is unlikely.  The 
last release of gettext was in May and we certainly would have run into 
the problem before this if it has a race condition.


  -- Bruce
.

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Failure Building Cyrus and OpenLDAP

2020-01-04 Thread Bruce Dubbs

On 1/4/20 7:15 PM, Alan Feuerbacher wrote:

On 1/4/2020 12:59 PM, Xi Ruoyao wrote:

On 2020-01-04 10:56 -0700,Alan Feuerbacher wrote:

I'm not sure if this should go to the lfs or blfs support list,
since I'm still in the chroot environment at the end of the LFS
book, but am installing several programs that are useful when
I eventually get systemd running.


I'm building some helpful BLFS programs using Beyond
Linux® From Scratch (systemd Edition) - Version 2020-01-03

At this point I'm trying to build Cyrus SASL-2.1.27 and
OpenLDAP-2.4.48. According to this hint:
http://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl

This page was wrote 14 years ago!

http://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl?action=history

I believe it's outdated and we should remove this URL from the book.
(Well, back in 2006 I was using Windoge XP and didn't know Linux :)

I agree!


I removed that page.

  -- Bruce


Though I don't use OpenLDAP, I think the correct method is to build 
and install
Cyrus SASL w/o OpenLDAP, then build and install OpenLDAP, then rebuild 
Cyrus

SASL.  (Just like how we deals Freetype and Harfbuzz.)


That's what I just did, and it seems to work fine.

Alan



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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Ken Moffat
On Sat, Jan 04, 2020 at 05:11:18PM -0500, Scott Andrews wrote:
> 
> On 1/4/20 1:45 PM, Flareon Zulu wrote:
> > 
> > On January 4, 2020, at 09:47, Scott Andrews
> >  wrote:
> > 
> > >Anyone have this error?
> > >ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
> > >m-regex.o mbrlen.o regex.o
> > >ranlib libgrep.a
> > >make[3]: Leaving directory
> > >'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
> > >Making all in src
> > >here=`pwd`; \
> > >cd ../../libtextstyle/lib && \
> > >  /usr/bin/make install-nobase_includeHEADERS
> > >install-nobase_nodist_includeHEADERS includedir="$here"
> > >make[3]: *** No rule to make target 'install-nobase_includeHEADERS'. 
> > Stop.
> > >make[2]: *** [Makefile:3955: textstyle.h] Error 2
> > >make[1]: *** [Makefile:2173: all-recursive] Error 1
> > >make: *** [Makefile:2041: all] Error 2
> > >Didn't see anything on the list about this
> > >Gettext-0.19.8.1 is ok
> > >--

> > 
> > Especially in light of this: https://savannah.gnu.org/bugs/?56333
> > 
> > It seems there could be an issue with build order, essentially. I didn't
> > have an issue, but some people online have had this happen, they're just
> > not on this list.
> > 
> > Flareon Zulu
> > 
> Could very well be,  I will follow up on the link you posted and see if I
> caqn make sense in it.
> 
> 
The usual workaround for what that sounds like is "make -j1".
Apologies if you are already doing that.  My most recent example of
that was in bison on a Skylake (an i3 so I'd been running make -j4 :
perhaps -j3 or -j2 might have sufficed).  On other machines (haswell
i7, ryzen 3400G) make -j8 was fine.  Modern CPUs can be a pain.

And that is another thing to learn from LFS - ISTR that dropping
back to -j1 in case of problems is mentioned in the FAQ.

ĸen
-- 
The right of the people to keep and arm Bears, shall not be infringed.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Failure Building Cyrus and OpenLDAP

2020-01-04 Thread Alan Feuerbacher

On 1/4/2020 12:59 PM, Xi Ruoyao wrote:

On 2020-01-04 10:56 -0700,Alan Feuerbacher wrote:

I'm not sure if this should go to the lfs or blfs support list,
since I'm still in the chroot environment at the end of the LFS
book, but am installing several programs that are useful when
I eventually get systemd running.


I'm building some helpful BLFS programs using Beyond
Linux® From Scratch (systemd Edition) - Version 2020-01-03

At this point I'm trying to build Cyrus SASL-2.1.27 and
OpenLDAP-2.4.48. According to this hint:
http://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl

This page was wrote 14 years ago!

http://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl?action=history

I believe it's outdated and we should remove this URL from the book.
(Well, back in 2006 I was using Windoge XP and didn't know Linux :)

I agree!

Though I don't use OpenLDAP, I think the correct method is to build and install
Cyrus SASL w/o OpenLDAP, then build and install OpenLDAP, then rebuild Cyrus
SASL.  (Just like how we deals Freetype and Harfbuzz.)


That's what I just did, and it seems to work fine.

Alan

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Glibc Localedef Problem

2020-01-04 Thread Alan Feuerbacher

On 1/4/2020 12:49 PM, Xi Ruoyao wrote:

On 2020-01-04 10:21 -0700,Alan Feuerbacher wrote:

I've run into a problem in building Version 20200101-systemd Section
6.9. Glibc-2.30.

After several repetitions of compiling, I've found that if I run
"make check", the various localedef invocations that follow, like
"localedef -i cs_CZ -f UTF-8 cs_CZ.UTF-8", sometimes fail with a message like
"cannot create temporary file: /tools/lib/locale/locale-archive.J6uC5g:
No such file or directory".
However, if I skip "make check", all of the "localedef" commands
run ok.

That's abnormal.  NEVER continue blindly with this kind of phenomena.  That may
be a bomb and may blow up your entire system.


Can you please expand on what I did wrong? I don't really understand 
what you mean by "continue blindly".



After some investigation I found the following:

The behavior is partly repeatable, in the sense that in doing about
half a dozen builds, sometimes the problem appeared and sometimes not.
I could see no pattern to the failures and successes. The final time
I ran "make check", all of the "localedef ..." commands succeeded.
So I've proceeded with the rest of Section 6 to nearly the end.

Before doing all builds again, I wiped the hard drive and started
from scratch, installing everything in the LFS book up through
Section 6.9.

A few details:

After all the runs of "make check", whether "localedef ..." succeeded
or not, /tools/lib exists but /tools/lib/locale does not exist. So
the question is: why is "localedef" sometimes looking for a
non-existent directory?
Glibc configuration script sets up a variable named "libc_cv_complocaledir".
It's value is defaulted to be $libdir/locale.  It's then hard-coded into
localedef binary and libc libraries.  So /tools/bin/localedef will always look
for /tools/lib/locale.
But I thought that configuring with --prefix=/usr forces files to be put 
in /usr/lib and /usr/bin . So I would think that you would get a default 
of /usr/lib/locale. I checked, and there does exist 
/usr/lib/locale/locale-archive, which I'm sure is correct.

My guess: either you forgot to run "make install" after "make check" (I really
have done this stupid thing several times), or you forgot to use "+h" in section
6.4.  Without "+h" bash may remember /tools/bin/localedef and use it even if
/usr/bin/localedef is newly installed.


I've wrapped the various commands in a sort of script, so that I can 
more easily run them reliably, since running each command individually 
from the LFS book is extremely prone to errors of omission for me. I 
think I screwed up some of the syntax.


I started over again with glibc after cleaning up my script. No issues 
now. Thanks!


Alan

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Bruce Dubbs

On 1/4/20 4:11 PM, Scott Andrews wrote:


On 1/4/20 1:45 PM, Flareon Zulu wrote:


On January 4, 2020, at 09:47, Scott Andrews 
 wrote:


>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
>m-regex.o mbrlen.o regex.o
>ranlib libgrep.a
>make[3]: Leaving directory
>'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
>Making all in src
>here=`pwd`; \
>cd ../../libtextstyle/lib && \
>  /usr/bin/make install-nobase_includeHEADERS
>install-nobase_nodist_includeHEADERS includedir="$here"
>make[3]: *** No rule to make target 'install-nobase_includeHEADERS'.  
Stop.

>make[2]: *** [Makefile:3955: textstyle.h] Error 2
>make[1]: *** [Makefile:2173: all-recursive] Error 1
>make: *** [Makefile:2041: all] Error 2
>Didn't see anything on the list about this
>Gettext-0.19.8.1 is ok
>--
>http://lists.linuxfromscratch.org/listinfo/lfs-support
>FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>Unsubscribe: See the above information page
>Do not top post on this list.
>A: Because it messes up the order in which people normally read text.
>Q: Why is top-posting such a bad thing?
>A: Top-posting.
>Q: What is the most annoying thing in e-mail?
>http://en.wikipedia.org/wiki/Posting_style

Especially in light of this: https://savannah.gnu.org/bugs/?56333

It seems there could be an issue with build order, essentially. I 
didn't have an issue, but some people online have had this happen, 
they're just not on this list.


Flareon Zulu

Could very well be,  I will follow up on the link you posted and see if 
I caqn make sense in it.


It is doubtful that the problem is build order.  Most of the time when 
we update packages we do a complete rebuild of all LFS packages by 
extracting the instructions from the xml source.  Th eprocess is 
completely automated and errors will show up then.


Since the problem is in Chapter 5, there are really only two 
possibilities: an error when following previous instructions or a 
problem with the host system.


  -- Bruce

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Where to place downloaded "blfs-systemd-units-20191026" ?

2020-01-04 Thread Alan Feuerbacher

On 1/4/2020 1:14 PM, Douglas R. Reno wrote:

On 1/4/20 12:41 PM, Alan Feuerbacher wrote:


I'm at the end of the LFS book and installing a few helpful
BLFS programs, using
Beyond Linux® From Scratch (systemd Edition) - Version 2020-01-03

At the end of installing Cyrus SASL-2.1.27 you're supposed to
run "make install-saslauthd" after downloading the file in
"blfs-systemd-units-20191026". The question is where this
should be downloaded to.

The section BLFS Systemd Units states:

. . . When a systemd unit is requested from BLFS Systemd Units,
simply change to the directory, and as the root user, execute
the given make install- command. . .

Change to what directory?

I've downloaded the blfs-systemd file to $LFS/sources and to
$LFS/sources/cyrus-sasl-2.1.27, switched to those directories,
and executed "make install-saslauthd". It fails with the
message:

make: *** No rule to make target 'install-saslauthd'.  Stop.

I've done this hundreds of times with no problems when I last
built LFS several years ago, with no issues.

What am I missing?

The section also states:

It is advisable to peruse each systemd unit before installation
to determine whether the installed files meet your needs.

I've looked at the "blfs-systemd-units-20191026" file, but
vim indicates nothing useful inside.

Alan

Place the blfs-systemd-units tarball in the same place as the other 
tarballs. Extract it using the tar command like you would normally, 
and then cd into it (example: tar -xf 
blfs-systemd-units-20191026.tar.xz && cd blfs-systemd-units-20191026)


You can then run a "vi blfs/units/saslauthd.service" for example and 
make sure that it fits your needs. In the majority of cases, it should 
meet the needs of the user by default. Since you're specifically 
mentioning Cyrus SASL, make sure you view blfs/default/saslauthd just 
to make sure that it meets the needs that you're looking for.


Thank you,

- Doug


Thanks! That worked.

Alan

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Scott Andrews


On 1/4/20 1:45 PM, Flareon Zulu wrote:


On January 4, 2020, at 09:47, Scott Andrews 
 wrote:


>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
>m-regex.o mbrlen.o regex.o
>ranlib libgrep.a
>make[3]: Leaving directory
>'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
>Making all in src
>here=`pwd`; \
>cd ../../libtextstyle/lib && \
>  /usr/bin/make install-nobase_includeHEADERS
>install-nobase_nodist_includeHEADERS includedir="$here"
>make[3]: *** No rule to make target 'install-nobase_includeHEADERS'.  
Stop.

>make[2]: *** [Makefile:3955: textstyle.h] Error 2
>make[1]: *** [Makefile:2173: all-recursive] Error 1
>make: *** [Makefile:2041: all] Error 2
>Didn't see anything on the list about this
>Gettext-0.19.8.1 is ok
>--
>http://lists.linuxfromscratch.org/listinfo/lfs-support
>FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>Unsubscribe: See the above information page
>Do not top post on this list.
>A: Because it messes up the order in which people normally read text.
>Q: Why is top-posting such a bad thing?
>A: Top-posting.
>Q: What is the most annoying thing in e-mail?
>http://en.wikipedia.org/wiki/Posting_style

Especially in light of this: https://savannah.gnu.org/bugs/?56333

It seems there could be an issue with build order, essentially. I 
didn't have an issue, but some people online have had this happen, 
they're just not on this list.


Flareon Zulu

Could very well be,  I will follow up on the link you posted and see if 
I caqn make sense in it.




Thanks

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Scott Andrews


On 1/4/20 1:38 PM, Flareon Zulu wrote:


On January 4, 2020, at 09:47, Scott Andrews 
 wrote:


>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o
>m-regex.o mbrlen.o regex.o
>ranlib libgrep.a
>make[3]: Leaving directory
>'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
>Making all in src
>here=`pwd`; \
>cd ../../libtextstyle/lib && \
>  /usr/bin/make install-nobase_includeHEADERS
>install-nobase_nodist_includeHEADERS includedir="$here"
>make[3]: *** No rule to make target 'install-nobase_includeHEADERS'.  
Stop.

>make[2]: *** [Makefile:3955: textstyle.h] Error 2
>make[1]: *** [Makefile:2173: all-recursive] Error 1
>make: *** [Makefile:2041: all] Error 2
>Didn't see anything on the list about this
>Gettext-0.19.8.1 is ok
>--
>http://lists.linuxfromscratch.org/listinfo/lfs-support
>FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>Unsubscribe: See the above information page
>Do not top post on this list.
>A: Because it messes up the order in which people normally read text.
>Q: Why is top-posting such a bad thing?
>A: Top-posting.
>Q: What is the most annoying thing in e-mail?
>http://en.wikipedia.org/wiki/Posting_style

What was the command this failed on? I didn't get it before when I was 
compiling my base or my main systems.


Also, were you testing anything else on the package? That might be a 
place to start looking, cause I'm curious now.


Flareon Zulu



The make command after the configure ran

Never got to make install

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Where to place downloaded "blfs-systemd-units-20191026" ?

2020-01-04 Thread Douglas R. Reno


On 1/4/20 12:41 PM, Alan Feuerbacher wrote:


I'm at the end of the LFS book and installing a few helpful
BLFS programs, using
Beyond Linux® From Scratch (systemd Edition) - Version 2020-01-03

At the end of installing Cyrus SASL-2.1.27 you're supposed to
run "make install-saslauthd" after downloading the file in
"blfs-systemd-units-20191026". The question is where this
should be downloaded to.

The section BLFS Systemd Units states:

. . . When a systemd unit is requested from BLFS Systemd Units,
simply change to the directory, and as the root user, execute
the given make install- command. . .

Change to what directory?

I've downloaded the blfs-systemd file to $LFS/sources and to
$LFS/sources/cyrus-sasl-2.1.27, switched to those directories,
and executed "make install-saslauthd". It fails with the
message:

make: *** No rule to make target 'install-saslauthd'.  Stop.

I've done this hundreds of times with no problems when I last
built LFS several years ago, with no issues.

What am I missing?

The section also states:

It is advisable to peruse each systemd unit before installation
to determine whether the installed files meet your needs.

I've looked at the "blfs-systemd-units-20191026" file, but
vim indicates nothing useful inside.

Alan

Place the blfs-systemd-units tarball in the same place as the other 
tarballs. Extract it using the tar command like you would normally, and 
then cd into it (example: tar -xf blfs-systemd-units-20191026.tar.xz && 
cd blfs-systemd-units-20191026)


You can then run a "vi blfs/units/saslauthd.service" for example and 
make sure that it fits your needs. In the majority of cases, it should 
meet the needs of the user by default. Since you're specifically 
mentioning Cyrus SASL, make sure you view blfs/default/saslauthd just to 
make sure that it meets the needs that you're looking for.


Thank you,

- Doug

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Failure Building Cyrus and OpenLDAP

2020-01-04 Thread Xi Ruoyao
On 2020-01-04 10:56 -0700,Alan Feuerbacher wrote:
> I'm not sure if this should go to the lfs or blfs support list,
> since I'm still in the chroot environment at the end of the LFS
> book, but am installing several programs that are useful when
> I eventually get systemd running.
> 
> 
> I'm building some helpful BLFS programs using Beyond
> Linux® From Scratch (systemd Edition) - Version 2020-01-03
> 
> At this point I'm trying to build Cyrus SASL-2.1.27 and
> OpenLDAP-2.4.48. According to this hint:
> http://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl

This page was wrote 14 years ago!

http://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl?action=history

I believe it's outdated and we should remove this URL from the book.
(Well, back in 2006 I was using Windoge XP and didn't know Linux :)

Though I don't use OpenLDAP, I think the correct method is to build and install
Cyrus SASL w/o OpenLDAP, then build and install OpenLDAP, then rebuild Cyrus
SASL.  (Just like how we deals Freetype and Harfbuzz.)
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


[lfs-support] Building LFS for Headless Server

2020-01-04 Thread Rob
As I mentioned before, I'm working at building LFS for a headless
server whose primary purpose is for data storage.
Thanks, by the way, for the serial console suggestion. I'll be doing that.
As such, I'm wondering if any special consideration needs to be taken
particularly for kernel builds when attempting to run linux offa USB
stick.
I know the NAS distributions are designed to run as such. However
I don't want to go that route; too much junk is included which I
don't need.
Any tips appreciated.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] Glibc Localedef Problem

2020-01-04 Thread Xi Ruoyao
On 2020-01-04 10:21 -0700,Alan Feuerbacher wrote:
> I've run into a problem in building Version 20200101-systemd Section
> 6.9. Glibc-2.30.
> 
> After several repetitions of compiling, I've found that if I run
> "make check", the various localedef invocations that follow, like
> "localedef -i cs_CZ -f UTF-8 cs_CZ.UTF-8", sometimes fail with a message like
> "cannot create temporary file: /tools/lib/locale/locale-archive.J6uC5g:
> No such file or directory".
> However, if I skip "make check", all of the "localedef" commands
> run ok.

That's abnormal.  NEVER continue blindly with this kind of phenomena.  That may
be a bomb and may blow up your entire system.

> After some investigation I found the following:
> 
> The behavior is partly repeatable, in the sense that in doing about
> half a dozen builds, sometimes the problem appeared and sometimes not.
> I could see no pattern to the failures and successes. The final time
> I ran "make check", all of the "localedef ..." commands succeeded.
> So I've proceeded with the rest of Section 6 to nearly the end.
> 
> Before doing all builds again, I wiped the hard drive and started
> from scratch, installing everything in the LFS book up through
> Section 6.9.
> 
> A few details:
> 
> After all the runs of "make check", whether "localedef ..." succeeded
> or not, /tools/lib exists but /tools/lib/locale does not exist. So
> the question is: why is "localedef" sometimes looking for a
> non-existent directory?

Glibc configuration script sets up a variable named "libc_cv_complocaledir". 
It's value is defaulted to be $libdir/locale.  It's then hard-coded into
localedef binary and libc libraries.  So /tools/bin/localedef will always look
for /tools/lib/locale.

My guess: either you forgot to run "make install" after "make check" (I really
have done this stupid thing several times), or you forgot to use "+h" in section
6.4.  Without "+h" bash may remember /tools/bin/localedef and use it even if
/usr/bin/localedef is newly installed.
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Flareon Zulu
On January 4, 2020, at 09:47, Scott Andrews  
wrote:

>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o 
>m-regex.o mbrlen.o regex.o
>ranlib libgrep.a
>make[3]: Leaving directory 
>'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
>Making all in src
>here=`pwd`; \
>cd ../../libtextstyle/lib && \
>  /usr/bin/make install-nobase_includeHEADERS 
>install-nobase_nodist_includeHEADERS includedir="$here"
>make[3]: *** No rule to make target 'install-nobase_includeHEADERS'.  Stop.
>make[2]: *** [Makefile:3955: textstyle.h] Error 2
>make[1]: *** [Makefile:2173: all-recursive] Error 1
>make: *** [Makefile:2041: all] Error 2
>Didn't see anything on the list about this
>Gettext-0.19.8.1 is ok
>-- 
>http://lists.linuxfromscratch.org/listinfo/lfs-support
>FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>Unsubscribe: See the above information page
>Do not top post on this list.
>A: Because it messes up the order in which people normally read text.
>Q: Why is top-posting such a bad thing?
>A: Top-posting.
>Q: What is the most annoying thing in e-mail?
>http://en.wikipedia.org/wiki/Posting_style

Especially in light of this: https://savannah.gnu.org/bugs/?56333

It seems there could be an issue with build order, essentially. I didn't have 
an issue, but some people online have had this happen, they're just not on this 
list.

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


[lfs-support] Where to place downloaded "blfs-systemd-units-20191026" ?

2020-01-04 Thread Alan Feuerbacher

I'm at the end of the LFS book and installing a few helpful
BLFS programs, using
Beyond Linux® From Scratch (systemd Edition) - Version 2020-01-03

At the end of installing Cyrus SASL-2.1.27 you're supposed to
run "make install-saslauthd" after downloading the file in
"blfs-systemd-units-20191026". The question is where this
should be downloaded to.

The section BLFS Systemd Units states:

. . . When a systemd unit is requested from BLFS Systemd Units,
simply change to the directory, and as the root user, execute
the given make install- command. . .

Change to what directory?

I've downloaded the blfs-systemd file to $LFS/sources and to
$LFS/sources/cyrus-sasl-2.1.27, switched to those directories,
and executed "make install-saslauthd". It fails with the
message:

make: *** No rule to make target 'install-saslauthd'.  Stop.

I've done this hundreds of times with no problems when I last
built LFS several years ago, with no issues.

What am I missing?

The section also states:

It is advisable to peruse each systemd unit before installation
to determine whether the installed files meet your needs.

I've looked at the "blfs-systemd-units-20191026" file, but
vim indicates nothing useful inside.

Alan

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


Re: [lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Flareon Zulu
On January 4, 2020, at 09:47, Scott Andrews  
wrote:

>Anyone have this error?
>ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o 
>m-regex.o mbrlen.o regex.o
>ranlib libgrep.a
>make[3]: Leaving directory 
>'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'
>Making all in src
>here=`pwd`; \
>cd ../../libtextstyle/lib && \
>  /usr/bin/make install-nobase_includeHEADERS 
>install-nobase_nodist_includeHEADERS includedir="$here"
>make[3]: *** No rule to make target 'install-nobase_includeHEADERS'.  Stop.
>make[2]: *** [Makefile:3955: textstyle.h] Error 2
>make[1]: *** [Makefile:2173: all-recurs ive] Error 1
>make: *** [Makefile:2041: all] Error 2
>Didn't see anything on the list about this
>Gettext-0.19.8.1 is ok
>-- 
>http://lists.linuxfromscratch.org/listinfo/lfs-support
>FAQ: http://www.linuxfromscratch.org/blfs/faq.html
>Unsubscribe: See the above information page
>Do not top post on this list.
>A: Because it messes up the order in which people normally read text.
>Q: Why is top-posting such a bad thing?
>A: Top-posting.
>Q: What is the most annoying thing in e-mail?
>http://en.wikipedia.org/wiki/Posting_style

What was the command this failed on? I didn't get it before when I was 
compiling my base or my main systems.

Also, were you testing anything else on the package? That might be a place to 
start looking, cause I'm curious now.

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


[lfs-support] Failure Building Cyrus and OpenLDAP

2020-01-04 Thread Alan Feuerbacher

I'm not sure if this should go to the lfs or blfs support list,
since I'm still in the chroot environment at the end of the LFS
book, but am installing several programs that are useful when
I eventually get systemd running.


I'm building some helpful BLFS programs using Beyond
Linux® From Scratch (systemd Edition) - Version 2020-01-03

At this point I'm trying to build Cyrus SASL-2.1.27 and
OpenLDAP-2.4.48. According to this hint:
http://wiki.linuxfromscratch.org/blfs/wiki/cyrus-sasl
You first build Cyrus, then OpenLDAP, then Cyrus again
with some differences.

The hint says to do this:
#
./configure ... --with-ldap --enable-ldapdb

Build just the plugins and their necessary dependencies:

make -C include &&
make -C sasldb &&
make -C plugins
#

The last line fails with this message:
#
(lfs chroot) root:/sources/cyrus-sasl-2.1.27# make -C plugins
make: Entering directory '/sources/cyrus-sasl-2.1.27/plugins'
depbase=`echo sasldb.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I..  -I../include -I../lib -I../sasldb -I../common -I../include
-DOBSOLETE_CRAM_ATTR=1 -DOBSOLETE_DIGEST_ATTR=1   -Wall -W -g -O2 -MT
sasldb.lo -MD -MP -MF $depbase.Tpo -c -o sasldb.lo sasldb.c &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../lib
-I../sasldb -I../common -I../include -DOBSOLETE_CRAM_ATTR=1
-DOBSOLETE_DIGEST_ATTR=1 -Wall -W -g -O2 -MT sasldb.lo -MD -MP -MF
.deps/sasldb.Tpo -c sasldb.c  -fPIC -DPIC -o .libs/sasldb.o
depbase=`echo sasldb_init.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.
-I..  -I../include -I../lib -I../sasldb -I../common -I../include
-DOBSOLETE_CRAM_ATTR=1 -DOBSOLETE_DIGEST_ATTR=1   -Wall -W -g -O2 -MT
sasldb_init.lo -MD -MP -MF $depbase.Tpo -c -o sasldb_init.lo
sasldb_init.c &&\
mv -f $depbase.Tpo $depbase.Plo
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../lib
-I../sasldb -I../common -I../include -DOBSOLETE_CRAM_ATTR=1
-DOBSOLETE_DIGEST_ATTR=1 -Wall -W -g -O2 -MT sasldb_init.lo -MD -MP -MF
.deps/sasldb_init.Tpo -c sasldb_init.c  -fPIC -DPIC -o
.libs/sasldb_init.o
make: *** No rule to make target '../common/libplugin_common.la',
needed by 'libsasldb.la'.  Stop.
make: Leaving directory '/sources/cyrus-sasl-2.1.27/plugins'
#

I don't know what to make of this failure.

Alan


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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


[lfs-support] Glibc Localedef Problem

2020-01-04 Thread Alan Feuerbacher

I've run into a problem in building Version 20200101-systemd Section
6.9. Glibc-2.30.

After several repetitions of compiling, I've found that if I run
"make check", the various localedef invocations that follow, like
"localedef -i cs_CZ -f UTF-8 cs_CZ.UTF-8", sometimes fail with a message like
"cannot create temporary file: /tools/lib/locale/locale-archive.J6uC5g:
No such file or directory".
However, if I skip "make check", all of the "localedef" commands
run ok.

After some investigation I found the following:

The behavior is partly repeatable, in the sense that in doing about
half a dozen builds, sometimes the problem appeared and sometimes not.
I could see no pattern to the failures and successes. The final time
I ran "make check", all of the "localedef ..." commands succeeded.
So I've proceeded with the rest of Section 6 to nearly the end.

Before doing all builds again, I wiped the hard drive and started
from scratch, installing everything in the LFS book up through
Section 6.9.

A few details:

After all the runs of "make check", whether "localedef ..." succeeded
or not, /tools/lib exists but /tools/lib/locale does not exist. So
the question is: why is "localedef" sometimes looking for a
non-existent directory?

At this point everything seems to be running properly, and I've
begun installing BLFS software.

Alan

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style


[lfs-support] LFS-9.0 5.24. Gettext-0.20.1 build error

2020-01-04 Thread Scott Andrews

Anyone have this error?

ar cr libgrep.a glthread/lock.o glthread/threadlib.o kwset.o m-fgrep.o 
m-regex.o mbrlen.o regex.o


ranlib libgrep.a
make[3]: Leaving directory 
'/mnt/lfs/source/gettext-0.20.1/gettext-tools/libgrep'

Making all in src
here=`pwd`; \
cd ../../libtextstyle/lib && \
  /usr/bin/make install-nobase_includeHEADERS 
install-nobase_nodist_includeHEADERS includedir="$here"

make[3]: *** No rule to make target 'install-nobase_includeHEADERS'.  Stop.
make[2]: *** [Makefile:3955: textstyle.h] Error 2
make[1]: *** [Makefile:2173: all-recursive] Error 1
make: *** [Makefile:2041: all] Error 2

Didn't see anything on the list about this

Gettext-0.19.8.1 is ok

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

Do not top post on this list.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

http://en.wikipedia.org/wiki/Posting_style