Re: [Ltib] Cannot build e2fsprogs using ./ltib --force

[James E. Chargin Jr.]

Stuart,

Manually appending --disable-nls to the config command in 
e2fsprogs.spec, deleting .../rpm/BUILD/e2fs* and rerunning ./ltib has 
been successful when e2fsprogs is included in the package list.

Thanks again for you help, I am very grateful. Please let me know if I 
can be of help to you someday.

Jim
---


Stuart Hughes wrote:
> On Fri, 2008-06-06 at 06:53 -0700, James E. Chargin Jr. wrote:
> > Stuart,
> >
> > When I first installed LTIB from the ISO image onto my 7.10 system, my 
> > builds worked without problems, whether e2fsprogs was included or not. 
> > It was during my first attempt at "./ltib --force" that I had e2fsprogs 
> > build problems. I did the --force build because I was curious about what 
> > a "from-scratch" build looked like (its pretty long).
>
> Okay, that explains it.  When you install an iso it has (to save time)
> pre-built binary rpms.  Unless you force or change some config it will
> use these.
>
> > I have also discovered that my system does not have msgfmt; apparently, 
> > the gettext-base package, which is installed on my system, does not 
> > include it. I installed the gettext package, which does include msgfmt, 
> > but the build still fails to complete, in the same manner. I'm unsure 
> > now that msgfmt is really related to my problem as I first thought.
>
> I'm not sure either other than the hinted out version dependency thing
> on the link I sent.
>
>
> > A kind poster on the Ubuntu forums has also sent google links indicating 
> > that building without nls might fix my problem. I'm new enough to kernel 
> > builds that I don't understand what nls is and so I haven't tried to 
> > disable this yet. Your instructions for patching the spec file should be 
> > helpful here, but I would benefit from more explicit instructions about 
> > how this patch is applied; what command(s) will apply the patch correctly?
>
> The easiest thing is just to append: --disable-nls to the end of the
> configure line in dist/lfs-5.1/e2fsprogs/e2fsprogs.spec. 
>
> Then remove the failed build (just to be sure) in rpm/BUILD/e2fs*
> Re-run: ./ltib
>
>
> > I will try your suggestion a bit later today and reply with my results.
> >
> > Thank you very much for your help.
> >
> > Jim
>
> Okay, I've also found an Ubuntu 6.10 I'm trying a build on (it's very
> slow as it's a VMware), I'll let you know if/when I get results from
> that.
>
> Regards, Stuart
>
>
> > Stuart Hughes wrote:
> > > Hi James,
> > >
> > > I got a copy of LTIB from that release date and I've not been able to
> > > reproduce the problem.  That's probably because I don't have the same
> > > distro to test on, for Ubuntu's I've only got 8.04.
> > >
> > > I did a bit of googling and this looks relevant:
> > > http://www.linuxarkivet.se/mlists/ext3-users/0404/msg00006.html
> > >
> > > When you say it works the first time but after a re-build, did you mean
> > > that it worked when you first installed (e.g. using the pre-built rpms
> > > from the ISO image)?
> > >
> > > Can you try patching the spec file with this:
> > >
> > > --- dist/lfs-5.1/e2fsprogs/e2fsprogs.spec.orig  2008-06-06 12:02:11.000000000 
> > > +0100
> > > +++ dist/lfs-5.1/e2fsprogs/e2fsprogs.spec       2008-06-06 14:02:09.000000000 
> > > +0100
> > > @@ -36,7 +36,7 @@
> > >  # cp: cannot create regular file `libintl.h': Permission denied
> > >  chmod +w intl/libintl.h
> > >  CC="gcc" BUILD_CC="$BUILDCC" \
> > > -./configure --enable-dynamic-e2fsck --enable-elf-shlibs --prefix=%{_prefix} 
> > > --host=$CFGHOST --mandir=%{_mandir}
> > > +./configure --enable-dynamic-e2fsck --enable-elf-shlibs --prefix=%{_prefix} 
> > > --host=$CFGHOST --mandir=%{_mandir}  --disable-nls
> > >  make -j1 libs progs docs
> > >
> > >  %Install
> > >
> > > It turns of nls which I think should fix your problem.
> > >
> > > Regards, Stuart
> > >
> > >
> > > On Thu, 2008-06-05 at 13:31 -0700, James E. Chargin Jr. wrote:
> > > > Stuart,
> > > >
> > > > Thanks for helping out.
> > > >
> > > > As you requested, I have run the several commands you provided. The 
> > > > first four command completed without complaint, but the final "./ltib" 
> > > > failed, with the same symptom as before. Part of the output follows:
> > > > ----
> > > > ...
> > > > make[1]: Leaving directory 
> > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/tests/progs'
> > > > making all in po
> > > > make[1]: Entering directory 
> > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/po'
> > > > : --update cs.po e2fsprogs.pot
> > > > rm -f cs.gmo && : -c --statistics -o cs.gmo cs.po
> > > > mv: cannot stat `t-cs.gmo': No such file or directory
> > > > mane[1]: *** [cs.gmo] Error 1
> > > > make[1]: Leaving directory 
> > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/po'
> > > > make: *** [all-progs-recursive] Error 1
> > > > error: Bad exit status from 
> > > > /home/jimc/.../ltib-mpc8315erdb-20071129/tmp/rpm-tmp.95834 (%build)
> > > >
> > > > RPM build errors:
> > > >      Bad exit status from 
> > > > /home/jimc/.../ltib-mpc8315erdb-20071129/tmp/rpm-tmp.95834 (%build)
> > > > Build time for e2fsprogs: 45 seconds
> > > >
> > > > Failed building e2fsprogs
> > > >
> > > >
> > > > f_buildrpms() returned an error, exiting
> > > >
> > > > Started: Thu Jun  5 12:07:30 2008
> > > > Ended:   Thu Jun  5 13:08:19 2008
> > > > Elapsed: 49 seconds
> > > >
> > > > These packages failed to build:
> > > > e2fsprogs
> > > > Build Failed
> > > >
> > > > Exiting on error or interrupt
> > > > ----
> > > >
> > > > Because this command failed, I didn't even run the "./ltib -p e2fsprogs 
> > > > -f" you requested.
> > > >
> > > > Again, thanks for the help. What more can I do to help determine what 
> > > > the problem might be?
> > > >
> > > > Regards,
> > > > Jim
> > > > ---
> > > > James E. Chargin Jr.
> > > > Sierra Design Associates            (530) 478-6689
> > > > 117 New Mohawk Rd, Suite H          address@hidden
> > > > Nevada City, CA 95959  USA          http:\\www.sdateam.com
> > > >
> > > >
> > > > Stuart Hughes wrote:
> > > > > Hi Jim,
> > > > >
> > > > > The most likely explanation is that is built after e2fsprogs is detected
> > > > > on subsequent rebuilds of e2fsprogs, thus causing a failure.  I may need
> > > > > to exclude this using an explicity ac_cv_...=no
> > > > >
> > > > > Can you try this for me:
> > > > >
> > > > > $ ./ltib -m clean
> > > > > $ rm -rf rpm/BUILD/e2fs*
> > > > > $ touch dist/lfs-5.1/e2fsprogs/e2fsprogs.spec
> > > > > $ ./ltib
> > > > >
> > > > > If this works but a subsequent: ./ltib -p e2fsprogs -f fails then I'll
> > > > > have something to hunt down.
> > > > >
> > > > > Regards, Stuart
> > > > >
> > > > > On Wed, 2008-06-04 at 11:36 -0700, James E. Chargin Jr. wrote:
> > > > > > I'm building for the 8513erdb, on Ubuntu 7.10.
> > > > > >
> > > > > > Previous attempts to build via ltib have succeeded.
> > > > > >
> > > > > > Out of curiosity, I ran ltib with the --force option. Now, 
> > > > > > e2fsprogs-1.34 will not build. The only way I can get a successful build 
> > > > > > is by excluding e2fsprogs, which is not acceptable for the long term.
> > > > > >
> > > > > > The following is among the output generated during the build failure
> > > > > > ----
> > > > > > make[1]: Leaving directory 
> > > > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/resize'
> > > > > > making all in tests/progs
> > > > > > make[1]: Entering directory 
> > > > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/tests/progs'
> > > > > > gcc  -o test_icount test_icount.o test_icount_cmds.o 
> > > > > > ../../lib/libext2fs.so ../../lib/libss.so ../../lib/libcom_err.so
> > > > > > make[1]: Leaving directory 
> > > > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/tests/progs'
> > > > > > making all in po
> > > > > > make[1]: Entering directory 
> > > > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/po'
> > > > > > : --update cs.po e2fsprogs.pot
> > > > > > rm -f cs.gmo && : -c --statistics -o cs.gmo cs.po
> > > > > > mv: cannot stat `t-cs.gmo': No such file or directory
> > > > > > make[1]: *** [cs.gmo] Error 1
> > > > > > make[1]: Leaving directory 
> > > > > > `/home/jimc/.../ltib-mpc8315erdb-20071129/rpm/BUILD/e2fsprogs-1.34/po'
> > > > > > make: *** [all-progs-recursive] Error 1
> > > > > > error: Bad exit status from 
> > > > > > /home/jimc/.../ltib-mpc8315erdb-20071129/tmp/rpm-tmp.80089 (%build)
> > > > > >
> > > > > >
> > > > > > RPM build errors:
> > > > > >      Bad exit status from 
> > > > > > /home/jimc/.../ltib-mpc8315erdb-20071129/tmp/rpm-tmp.80089 (%build)
> > > > > > Build time for e2fsprogs: 38 seconds
> > > > > >
> > > > > > Failed building e2fsprogs
> > > > > >
> > > > > >
> > > > > > f_buildrpms() returned an error, exiting
> > > > > >
> > > > > > Started: Wed Jun  4 11:16:05 2008
> > > > > > Ended:   Wed Jun  4 11:17:01 2008
> > > > > > Elapsed: 56 seconds
> > > > > >
> > > > > > These packages failed to build:
> > > > > > e2fsprogs
> > > > > > Build Failed
> > > > > >
> > > > > > Exiting on error or interrupt
> > > > > > ----
> > > > > >
> > > > > > I think the failing line seems to want to call msgfmt, which should be a 
> > > > > > part of the gettext package. I've got gettext installed and when I 
> > > > > > previously ran ltib without --force, it built successfully.
> > > > > >
> > > > > > What am I missing here, or what should I try to get this working as 
> > > > > > expected?
> > > > > >
> > > > > > Thanks,
> > > > > > Jim