On 12/19/2013 09:32 AM, Frans de Boer wrote:
> On 12/18/2013 05:06 PM, William Harrington wrote:
>>
>> On Dec 18, 2013, at 4:07 AM, Frans de Boer wrote:
>>
>>> The output of ulimit -a is:
>>> root:/sources/glibc-2.18# ulimit -a
>>> core file size          (blocks, -c) 0
>>> data seg size           (kbytes, -d) unlimited
>>> scheduling priority             (-e) 0
>>> file size               (blocks, -f) unlimited
>>> pending signals                 (-i) 63196
>>> max locked memory       (kbytes, -l) 64
>>> max memory size         (kbytes, -m) unlimited
>>> open files                      (-n) 1024
>>> pipe size            (512 bytes, -p) 8
>>> POSIX message queues     (bytes, -q) 819200
>>> real-time priority              (-r) 0
>>> stack size              (kbytes, -s) 8192
>>> cpu time               (seconds, -t) unlimited
>>> max user processes              (-u) 63196
>>> virtual memory          (kbytes, -v) unlimited
>>> file locks                      (-x) unlimited
>>>
>>> My default host shell is bash.
>>
>> Yes, and what was in sources/glibc-2.18/build/nptl/tst-pthread-
>> getattr.out
>> How about optimizations?
>>
>> In which case why do you have sources/glibc-2.18/build and not /
>> sources/glibc-build?
>>
>> GCC will definitely error when you put the build directory into the
>> gcc source tree. Glibc may very well, too.
>>
>> Any other deviations you don't mention?
>>
>> Sincerely,
>>
>> William Harrington
>>
> @William: Sorry, but using a separate build directory within the source
> tree has never caused me any trouble, not with gcc, glibc or any other
> package where it was recommended to use a separate build directory.
>
> Thus, I indeed recreated the tool chain again without the --libexec
> directive and had only the predicted errors - see below. So, somehow
> libexec did matter. I hope that in the final system this is not a problem.
>
> --------------
> make[1]: Target 'check' not remade because of errors.
> make[1]: Leaving directory '/sources/glibc-2.18'
> Makefile:9: recipe for target 'check' failed
> make: *** [check] Error 2
>
> Display errors
> make[2]: *** [/sources/glibc-2.18/build/posix/tst-getaddrinfo4.out] Error 1
> make[2]: [/sources/glibc-2.18/build/posix/annexc.out] Error 1 (ignored)
> make[1]: *** [posix/tests] Error 2
> make[2]: *** [/sources/glibc-2.18/build/rt/tst-cpuclock2.out] Error 1
> make[1]: *** [rt/tests] Error 2
> make[2]: [/sources/glibc-2.18/build/conform/run-conformtest.out] Error 1
> (ignored)
> make: *** [check] Error 2
>
> Enter key to install...
> ---------------
>
> So, I just continue to build the base system.
>
> Regards, Frans.

Dear all,

I have found the real cause of the errors I initially reported. It has 
nothing to do with libexec and/or creating a build directory within the 
source tree.

In fact, I placed 6.2.1 (making nodes) and 6.3.2/3 into one bash script. 
It works the first time until I stopped and logout for a backup and then 
rerun that script again to prepare the build of glibc. That script 
crashed upon making the console node, thus skipping the mount commands.
I now enhanced that script with tests for the nodes and now all gets 
mounted well. It also cause the building of glibc to run as expected.

Hope this helps. I also will look deeper now into the 'Error 2' at the 
end of the glibc tests. The reason is that it stops jhalfs from proceeding.

Regards, Frans.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to