Success.
Thanks so much for your help, Volker.
Final comments...
At some point in the past, on the first or second failure to build and long
before I reached out for help, I did the following apparent no-no:
I noticed that the c++, gcc, etc. files in
/Library/Developer/CommandLineTools/usr/bin
Unfortunately there is no satisfactory uninstall process for Xcode or
Command line tools. Your efforts sound good though.
On Friday, June 19, 2015 at 4:20:36 PM UTC+2, la...@math.luc.edu wrote:
>
> On Friday, June 19, 2015 at 8:16:38 AM UTC-5, Volker Braun wrote:
>>
>> PS: Have you tried uninsta
On Friday, June 19, 2015 at 8:16:38 AM UTC-5, Volker Braun wrote:
>
> PS: Have you tried uninstalling and reinstalling Xcode (as opposed to just
> upgrading?)
>
> I'm sure a shoddy job of doing that is what got me in this mess in the
first place. Over the many osx, xcode, and commandline tools up
On Friday, June 19, 2015 at 8:15:57 AM UTC-5, Volker Braun wrote:
>
> The --switch does not change /usr/bin/clang and friends, it just does some
> afaik undocumented stuff. Whats the include search path now?
>
>
I'm not quite sure how to answer this question, so I'll just reprint every
thing you
PS: Have you tried uninstalling and reinstalling Xcode (as opposed to just
upgrading?)
On Friday, June 19, 2015 at 3:15:57 PM UTC+2, Volker Braun wrote:
>
> The --switch does not change /usr/bin/clang and friends, it just does some
> afaik undocumented stuff. Whats the include search path now?
The --switch does not change /usr/bin/clang and friends, it just does some
afaik undocumented stuff. Whats the include search path now?
On Friday, June 19, 2015 at 2:47:29 PM UTC+2, la...@math.luc.edu wrote:
>
> I forgot to do '--print-path' before doing '--switch' so can't give you
> the outp
I forgot to do '--print-path' before doing '--switch' so can't give you the
output of that command, but after running '--switch' I still get
"/usr/bin/clang++"
instead of your
"/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang"
Trying 'make' again
PS: Correct output would be something like
$ clang++ -E -x c++ - -v < /dev/null
Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn)
Target: x86_64-apple-darwin14.3.0
Thread model: posix
"/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang"
Well your header search path is seriously messed up, no wonder that you
can't find system headers. Whats the output of
xcode-select --print-path
You might want to try pointing Xcode to the right path, e.g. (assuming that
it is in /Applications/Xcode.app):
xcode-select --switch /Applications/X
On Thursday, June 18, 2015 at 5:30:14 PM UTC-5, Volker Braun wrote:
>
> There is something fishy even before the failure when I diff it with my
> log (see below): Your clang doesn't support C89 and misses ANSI C headers.
>
> Do you have anything in /usr/local installed?
>
>
lots. e.g., 'texl
There is something fishy even before the failure when I diff it with my log
(see below): Your clang doesn't support C89 and misses ANSI C headers. Do
you have anything in /usr/local installed?
@@ -70,7 +71,7 @@
checking for suffix of object files... o
checking whether we are using the GNU C co
Re: possibly needing to install Xcode:
I installed it. restarted machine. ran 'make distclean' then ran 'make'.
Same problem. two files (float.h and stdarg.h) that cannot be found, though
they exist.
'xcode-select --version' and 'gcc --version' return the same output as I
mentioned before.
He
The actual logs of whatever failed
On Thursday, June 18, 2015 at 8:56:56 PM UTC+2, la...@math.luc.edu wrote:
>
> will install Xcode and get back to you. in the meantime, did you just want
> a directory listing, or the actual logs?
>
> weehawken:sage-devel lauve$ ls logs/pkgs/
> bzip2-1.0.6.201403
will install Xcode and get back to you. in the meantime, did you just want
a directory listing, or the actual logs?
weehawken:sage-devel lauve$ ls logs/pkgs/
bzip2-1.0.6.20140317.log mpfr-3.1.2.p0.logpkgconf-0.9.7.log
config.log mpir-2.7.0-alpha12.log zlib-1.2.8.p0.log
ic
I think you need to have XCode installed, even though you shouldn't have to.
Can you also post logs (in SAGE_ROOT/logs/pkgs/)
On Thursday, June 18, 2015 at 7:29:56 PM UTC+2, la...@math.luc.edu wrote:
>
> Okay...
> I am now running 10.10.3.
> to try to get a clean version of tools, I deleted th
Okay...
I am now running 10.10.3.
to try to get a clean version of tools, I deleted the following three
directories:
* /Applications/Xcode.app
* /Library/Developer/CommandLineTools
* /usr/include/c++
I ran xcode-select --install from the command line. A pop up asked me to
install. I did.
Since Apple declined to fix the "rootpipe" bug in OSX 10.9 I would
recommend to upgrade to OSX 10.10 asap, effectively you don't receive
security fixes any more.
Even then, why did you not upgrade to command line tools 6.2? They should
still run on OSX 10.9
On Wednesday, June 10, 2015 at 7:4
Volkar:
Here's more info:
weehawken:sage-git lauve$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread mode
CommandLineTools for XCode 6.1.1 is old and buggy... Also, are you sure you
are using the compiler you think you are using? You can have multiple ones.
Output of gcc --version?
On Wednesday, June 10, 2015 at 4:37:13 PM UTC+2, Anne Schilling wrote:
>
> Hello,
>
> Aaron Lauve at Sage Days 65 is
19 matches
Mail list logo
