Correct yes when I untar there is no Makefile. After running configure, the file is created but it is empty. At least vim shows it is empty and the command make says no targets. Also empty are the other files that configure creates.
This is on a USB flash drive that is 4GB in size and the filesystem is ext3. I have already built less and sed from LFS, but I am trying to add new modules to the system from BLFS. I successfully added several modules but when I tried adding libpng I ran into this problem. Perhaps it is the new year problem? ;p I have not done any significant changes to the system at all. I backed it up by doing cp * onto a harddrive on the host system and I used the wireless network adapter. I also copied a custom script into /usr/bin and changed its permissions to 755. Other than that, I have nothing to attribute this change in behavior to. I used less and sed to try to see if the specific package is important but it appears not except that the "links" package configure script successfully populates the Makefile. All of the packages I've tried that do not work have already been installed (except for libpng) but I am almost positive this doesn't prevent configure from writing a complete Makefile, right? On Wed, Jan 2, 2013 at 2:29 PM, Ken Moffat <[email protected]> wrote: > > > Writing an empty Makefile is not the same as not being able to > write to a Makefile. Just to be clear : when you extract a package, > the Makefile does not exist, but then after you run configure it > exists but is empty ? > > Is this a solid-state "drive" ? What filesystem is on it ? > > ĸen > -- > das eine Mal als Tragödie, das andere Mal als Farce > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page >
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
