On 02/25/2013 06:30 PM, Bruce Dubbs wrote:
> Frans de Boer wrote:
>
>> Attached are two files as requested. In order to capture the warnings
>> too, I placed the 2>&1 operator at the end like make > grep-make.log
>> 2>&1, you would otherwise only get the stdout output and not stderr.
>> As you can see, the make output is exactly the same as I gave you before.
>
> I took the output of configure and your version is identical to mine.
>
> The first line of the make should be
>
> make[1]: Entering directory `/mnt/lfs/sources/grep-2.14'
>
> Looking at the Makefile, there is a command:
>
> am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
>
> and that is used later:
>
> $(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps)
> @for dep in $?; do \
> case '$(am__configure_deps)' in \
> *$$dep*) \
> echo ' cd $(srcdir) && $(AUTOMAKE) --gnu'; \
> $(am__cd) $(srcdir) && $(AUTOMAKE) --gnu \
> && exit 0; \
> exit 1;; \
> esac; \
> done; \
> echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu Makefile'; \
> $(am__cd) $(top_srcdir) && \
> $(AUTOMAKE) --gnu Makefile
>
> That shouldn't run because you should have something like:
>
> -rw-rw-r-- 1 bdubbs bdubbs 47019 Feb 25 17:11 Makefile
> -rw-r--r-- 1 bdubbs bdubbs 1795 Jul 5 2012 Makefile.am
> -rw-r--r-- 1 bdubbs bdubbs 57333 Aug 17 2012 Makefile.in
>
> The $(am__configure_deps) dependency should be the files in m4 and they
> all should have dates of 2012 before Aug 17.
>
> This indicates a possible clock problem. Is it set correctly? Also,
> you may want to try 'make -d' to see what is triggering this section of
> the Makefile.
>
> -- Bruce
>
Hi Bruce,
I found the cause of my problems. I have all the development files in a
directory I use for the host system too. There I have no problems,
because all the files have the date and time as stored in the TAR file.
For LFS I just did a copy 'cp -r <dir> $LFS/sources' and changed the
ownership to 'lfs'. This should be no problem because the contents of
the files is not altered. With your remarks about timing, I tried the cp
-rp .... approach and all troubles are gone (until the next one).
I did not see any reason to use tar files if my files are pristine too.
Alas, programs looking to the timestamps instead of the contents...?
So, I restart the whole building process, now with the -rp option to copy.
The thing is that I want to master the process of building my own
systems, using the latest versions, and not depend to much on the LFS
files. If it goes wrong I go back and try the LFS versions. For
instance, you still have file-5.11 while there is already file-5.13
available.
Anyhow, I learned a new lesson today and have a somewhat better
understanding of the used tools. Also, I will change the host system too
into using TAR files only as a base to start from - keeping accidents
like this away.
Thanks for your time,
Frans.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
