Ticket #1019 (closed defect: fixed)

Opened 22 months ago

Last modified 22 months ago

C-level build trouble when rebuilding r15471 on OSX 10.7.5

Reported by: tfb Owned by:
Priority: minor Milestone:
Component: other Version: trunk
Keywords: Cc:

Description

I'm using a suspiciously recent Xcode (ie the app store told me a couple of days ago it had a shiny new version and I foolishly accepted). Likewise 10.7.5 is reasonably recent I think (so all of this may be random Apple changes is what I am trying to say).

I've attached the output from script.

Attachments

15471-rebuild.script Download (14.0 KB) - added by tfb 22 months ago.
Output from build failure
1019.diff Download (326 bytes) - added by tfb 22 months ago.
proposed patch

Change History

Changed 22 months ago by tfb

Output from build failure

comment:1 follow-up: ↓ 2 Changed 22 months ago by rme

I don't have a Lion system set up at the moment to try to duplicate your results.

I'll make a suggestion anyway, though: try installing the command-line tools from Xcode. You probably did this with a previous Xcode installation at some point, but don't think that subsequent Xcode upgrades properly upgrade the command-line tools.

Choose Xcode->Preferences from the menu bar, click on the Downloads icon, and then look in the Components tab. If "Command Line Tools" is not installed, click the button to install it, and then try to build the lisp again.

You can build just lisp kernel (which is the C and assembly language part of CCL) by hand with

cd ccl/lisp-kernel/darwinx8664
make clean && make

and that can be a little easier to troubleshoot (and can be useful if you accidentally delete your dx86cl64 binary).

If installing the command line tools doesn't help, please leave a comment on the ticket and I'll install a copy of Xcode onto a 10.7.5 system to troubleshoot.

comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 22 months ago by tfb

Replying to rme:

I don't have a Lion system set up at the moment to try to duplicate your results.

I'll make a suggestion anyway, though: try installing the command-line tools from Xcode. You probably did this with a previous Xcode installation at some point, but don't think that subsequent Xcode upgrades properly upgrade the command-line tools.

I thought that too. But if I run Xcode it says that the command-line stuff is installed though, and:

kingston$ xcrun -find gcc /Applications/Xcode?.app/Contents/Developer/usr/bin/gcc kingston$ /Applications/Xcode?.app/Contents/Developer/usr/bin/gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

kingston$ type -p gcc /usr/bin/gcc kingston$ /usr/bin/gcc --version i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I will have a go at building via make &c explicitly later (possibly tomorrow, it's late here now).

comment:3 in reply to: ↑ 2 Changed 22 months ago by tfb

So, building under emacs and chasing the errors down, it looks like /usr/include/mach/task_info.h wants to have /usr/include/mach/vm_statistics.h as well. I've attached a patch for that (against lisp-kernel/gc.h).

I don't know if this is really the underlying cause: I'm suspicious that somehow /usr/include is wrong on my machine. The dates on the directories correspond to the 10.7.5 upgrade, and the files themselves are all 10 April this year, so perhaps this is some change post 10.7.4, which they then later backed out for 10.8 (I don't have 10.8 and can't as it's too new for my machine) Not sure.

With this change I can build r15471 and it looks fine (on very limited testing: gets a prompt, will rebuild itself).

Changed 22 months ago by tfb

proposed patch

comment:4 Changed 22 months ago by rme

  • Status changed from new to closed
  • Resolution set to fixed

Please update to r15473 and this should be fixed.

Note: See TracTickets for help on using tickets.