[LLVMbugs] [Bug 13757] New: An Xcode project that can't be built from scan-build
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Mon Sep 3 07:01:21 PDT 2012
http://llvm.org/bugs/show_bug.cgi?id=13757
Bug #: 13757
Summary: An Xcode project that can't be built from scan-build
Product: clang
Version: trunk
Platform: Macintosh
OS/Version: MacOS X
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
AssignedTo: kremenek at apple.com
ReportedBy: iamleeg at gmail.com
CC: llvmbugs at cs.uiuc.edu
Classification: Unclassified
I'm using Xcode Version 4.4.1 (4F1003) and svn r163115 of clang/scan-build.
Problem Description: my iOS app target can be built from Xcode against either
the iOS 5.1 simulator or device SDK. When I try to build it with "scan-build
xcodebuild" from the command line it won't build against either SDK.
Steps to reproduce:
MyProjectFolder $ /path/to/llvm/tools/clang/tools/scan-build/scan-build
--use-analyzer=Xcode xcodebuild -sdk iphonesimulator5.1
Expected results:
project builds successfully. It can be built in Xcode, and using Xcode's
built-in analyzer with Cmd-Shift-B also works.
Actual results:
build failure depending on the platform chosen:
iphonesimulator5.1:
ld: file not found: /usr/lib/arc/libarclite_iphonesimulator.a
clang: error: linker command failed with exit code 1 (use -v to see invocation)
iphoneos5.1:
clang: error: unsupported option '--serialize-diagnostics'
clang: error: no such file or directory:
'/path/to/MyProject/build/MyProject.build/Release-iphoneos/MyProject.build/Objects-normal/armv7/SourceFileBasename.dia'
Command /path/to/llvm/tools/clang/tools/scan-build/ccc-analyzer failed with
exit code 1
Regression:
This was working under Mac OS X 10.7 and Xcode 4.3, unfortunately I don't know
which upgrade (of what) caused it to break.
Notes: the same failures occur if I --use-analyzer=/usr/local/bin/clang, the
version built from svn r163115.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list