On Wed, Jan 02, 2013 at 01:51:09PM -0500, Alexander Spitzer wrote: > Hi Matt, > > Thanks for your reply. I've had no disk space left errors before while > building a heavy package (glibc or gcc). This was after much activity so I > believe it was due to the USB drive that the LFS is on over heating. After > a break everything was normal. > > This time however, there are no such errors and there is definitely disk > space left. Furthermore, I untarred the links package from scratch and ran > configure and sure enough, there is a valid Makefile generated. > But for packages such as less and sed, the configure just makes empty > files. There is nothing that stands out to me in the config.log. At the end > there is a line: configure: exit 0. There is a bunch of programs that fail > to compile, but those look designed to fail. At the top there are a few > commands that "equal" unknown, such as "/bin/arch = unknown" and > "/usr/bin/arch -k = unknown" but I doubt that has anything to do with the > problem. Other than that, I can't find anything in the log that shows any > signs of error. > > I am worried that something is very wrong internally. The strange thing is > that configure fails for all packages I've tried except for the links > package. Any other packages I should try that can help diagnose the > problem? Or any commands I can run that can show why configure can't write > to the Makefiles? (at least that's the problem on the surface) >
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
