Re: Bug#917794: racket: FTBFS building for armel,armhf on arm64

40 views
Skip to first unread message

David Bremner

unread,
Jan 5, 2019, 5:46:40 AM1/5/19
to Steve McIntyre, 917...@bugs.debian.org, racke...@googlegroups.com
Steve McIntyre <st...@einval.com> writes:

>
> I'd be happy to help debug as much as I can here, but the lack of info
> in the core file is a bit of a hurdle up-front!
>

I tried configuring with

./configure --enable-sgcdebug --enable-backtrace --disable-strip

I don't get core dumps anymore, but there is some debugging output from
the crash. The build log is attached.

For folks on racket-dev, the context is build failures building
armel/armhf on arm64 hardware. [1]

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917794

build.log

David Bremner

unread,
Jan 7, 2019, 1:11:44 PM1/7/19
to Steve McIntyre, 917...@bugs.debian.org, racke...@googlegroups.com
Steve McIntyre <st...@einval.com> writes:

> On Sat, Jan 05, 2019 at 06:46:33AM -0400, David Bremner wrote:
>>Steve McIntyre <st...@einval.com> writes:
>>
>>> I'd be happy to help debug as much as I can here, but the lack of info
>>> in the core file is a bit of a hurdle up-front!
>>
>>I tried configuring with
>>
>>./configure --enable-sgcdebug --enable-backtrace --disable-strip
>>
>>I don't get core dumps anymore, but there is some debugging output from
>>the crash. The build log is attached.
>
> ACK. Not very enlightening to me, I'm afraid. Could you maybe try this
> on the arm64 porter box, amdahl? That has armhf and armel chroots
> available too.

That's where the log comes from, in the armel chroot. I guess I'll try
some other subsets of options if get a chance.

d
Reply all
Reply to author
Forward
0 new messages