> On Sat, 26 May 2018 10:14:09 +0200
> René Nyffenegger <m...@renenyffenegger.ch> wrote:
>
>> Architecture: x86_64
>> .
>> .
>> target='x86_64-pc-linux-gnu'
>> target_alias=''
>> target_cpu='x86_64'
>> target_os='linux-gnu'
>> target_vendor='pc'
>
>
> René,
>
> That all looks OK to me. Can you trigger the illegal instruction
> error manually at the command prompt via:
>
>> What's causing the problem seems to be the ensurepip module:
>> ./python -E -m ensurepip
>
> If so, then run it through the debugger gdb and try to find out
> the specific offending instruction:
>
> gdb ./python
> run -E -m ensurepip
> display/i $pc
>
>
> There is a complication here in that you are building a LFS system
> which does not include gdb as that is a BLFS utility:
>
> http://www.linuxfromscratch.org/blfs/view/svn/general/gdb.html
>
> So, you will either have to rely in the host gdb, or also install gdb
> in your LFS system.
>
> Have you altered your optimization cflags e.g., -O3 ?
Mike
I didn't alter any optimization flags during the compilation process.
With your suggestion for gdb, I get the following result:
(gdb) run -E -m ensurepip
Starting program: /usr/lfs/sources/untarred/Python-3.6.4/python -E -m
ensurepip
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Program received signal SIGILL, Illegal instruction.
0x00007ffff3033ce4 in ffi_closure_alloc () from /usr/lib/libffi.so.6
(gdb) display/i $pc
1: x/i $pc
=> 0x7ffff3033ce4 <ffi_closure_alloc+4196>: vmovq %r13,%xmm3
(gdb)
Apparently, the problem lies with ffi. I will try to recompile that.
Rene
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
