On 10/23/2013 06:24 PM, Dan McGhee wrote:
In fact, I don't think it conducted any tests.
The commands I use in the glibc-build directory come right out of the book
make -k check 2>&1 | tee glibc-check-log
grep Error glibc-check-log
I do call them from a function defined in a build.conf file ca
On Oct 23, 2013, at 6:24 PM, Dan McGhee wrote:
> make -k check 2>&1 | tee glibc-check-log
> grep Error glibc-check-log
What as the output when running make -k check?
Sincerely,
William Harrington
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/l
In fact, I don't think it conducted any tests.
The commands I use in the glibc-build directory come right out of the book
make -k check 2>&1 | tee glibc-check-log
grep Error glibc-check-log
I do call them from a function defined in a build.conf file called
check_commands, but that shouldn't m
On Sat, 2013-08-24 at 12:28 -0400, Dave wrote:
> When compiling and testing Glibc >
> I've noticed in the configure line the option
> '--enable-kernel=2.6.32'. Why this when its a 3.10.9 kernel?
Short version, because it has to work with the kernel you're running
during the build, not just the
On Aug 24, 2013, at 11:28 AM, Dave wrote:
> When compiling and testing Glibc >
> I've noticed in the configure line the option
> '--enable-kernel=2.6.32'. Why this when its a 3.10.9 kernel?
Because not everyone builds hosts running a 3.10.9 kernel. Reference
this:
http://permalink.gmane.org/
When compiling and testing Glibc >
I've noticed in the configure line the option
'--enable-kernel=2.6.32'. Why this when its a 3.10.9 kernel?
I've noticed that when it installs, I kept getting a compile error on
one of the checks. Changed HOSTTYPE to x86_64, and it compiles now.
can you provi
