From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28019 invoked by alias); 13 Nov 2012 13:55:19 -0000 Received: (qmail 27811 invoked by uid 48); 13 Nov 2012 13:54:53 -0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/55289] darwin bootstrap fails due to missing libsanitizer/interception/mach_override directory and files Date: Tue, 13 Nov 2012 13:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-11/txt/msg01146.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55289 --- Comment #4 from Iain Sandoe 2012-11-13 13:54:52 UTC --- (In reply to comment #3) > > You can find these files in.. > > > > http://llvm.org/svn/llvm-project/compiler-rt/branches/release_32/lib/interception/mach_override/ > > With this files I have been able to do a clean bootstrap at revision 193472 on > x86_64-apple-darwin10. However, first, I have to supply the lib path for > libasan when using -faddress-sanitizer: -L/opt/gcc/gcc4.8w/lib -lasan; second, > the executable fails to run with: > > dyld: Symbol not found: _CFStringCreateCopy this is found in the CoreFoundation framework (CFxxxxx is a good hint). what you need is to have "-framework CoreFoundation" on the link line - and I guess the configury &c. needs to arrange this. > Looking at the web, it seems to be a known issue with darwin, but I have been > unable to understand how it can be fixed. > > Indeed I also see pr55291.