Re: [gtk-osx-users] New build system (continued).
- From: John Ralls <jralls ceridwen us>
- To: Pascal <p p14 orange fr>
- Cc: gtk-osx-users-list gnome org
- Subject: Re: [gtk-osx-users] New build system (continued).
- Date: Mon, 15 Apr 2019 07:06:34 -0700
On Apr 15, 2019, at 2:19 AM, Pascal <p p14 orange fr> wrote:
Le 15 avr. 2019 à 01:38, John Ralls <jralls ceridwen us> a écrit :
On Apr 14, 2019, at 12:50 PM, Pascal <p p14 orange fr> wrote:
John,
1) Here is backtrace of crash log:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: LIBSYSTEM, [0x2]
Application Specific Information:
%%n used in a non-immutable format string: %s
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6d1eeeb6 __abort_with_payload + 10
1 libsystem_kernel.dylib 0x00007fff6d1e92b8 abort_with_payload_wrapper_internal + 89
2 libsystem_kernel.dylib 0x00007fff6d1e92e5 abort_with_payload + 9
3 libsystem_c.dylib 0x00007fff6d0ffecc _os_crash_fmt + 182
4 libsystem_c.dylib 0x00007fff6d1368a8 __vfprintf + 16526
5 libsystem_c.dylib 0x00007fff6d15b059 __v2printf + 473
6 libsystem_c.dylib 0x00007fff6d14034b _vsnprintf + 415
7 libsystem_c.dylib 0x00007fff6d1403fe vsnprintf + 80
8 libsystem_c.dylib 0x00007fff6d1700ad __sprintf_chk + 142
9 conftest 0x000000010d4b3f2f main + 79
10 libdyld.dylib 0x00007fff6d09f015 start + 1
2) Here is expat config.log:
<config_expat.log>
Pascal,
The vsnprintf assert is an Apple "feature" for security. Gtk-osx's bootstrap.modules patches bison to
avoid the bug, and I'm close to updating to the latest bison in which that's fixed. Rerun bootstrap and
when bison fails pick "wipe directory and start over" so that the patch applies.
For expat it looks like you've got both -arch i386 and -arch x86_64 somehow. That doesn't work, you have
to build libraries twice and then merge them, but you don't really want to do that; just build for x86_64.
Yes John, I suspected something like that but I haven't asked for -arch i386.
How can I prevent i386?
You need to find where it's getting added to your CFLAGS and remove it. The first place to look is
jhbuildrc-custom, but it might be in some other shell-initialization like .bashrc or .bash_profile.
Regards,
John Ralls
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]