2009/3/10 Mariah :
>
> Bill,
>
> gcc-4.3.1 and gcc-4.3.2 used to be on SkyNet. In a rare moment of
> idleness, I decided to clean things up in /usr/local on SkyNet.
> Perhaps I did a little too much cleaning! If you want them back, I
> can easily restore them thanks to NetApp's .snapshot.
No, t
Bill,
gcc-4.3.1 and gcc-4.3.2 used to be on SkyNet. In a rare moment of
idleness, I decided to clean things up in /usr/local on SkyNet.
Perhaps I did a little too much cleaning! If you want them back, I
can easily restore them thanks to NetApp's .snapshot.
I am glad that you are finding SkyNet
Mariah, can I assume that gcc-4.3.1 and gcc-4.3.2 are not available on
varro. There seem to be files or something with those names in
/usr/local/bin, but they don't seem to do anything.
BTW, we all *really* appreciate your efforts in getting gcc working on
these machines for us to use.
Just to b
Got it!! __APPLE_CC__ is defined to be 1 by FSF GCC, but is defined to
be the APPLE compiler revision by a genuine APPLE GCC.
So the fix is trivial.
The number of websites and even books that have the wrong information
about this is just immense! So much damned misinformation about GCC on
the we
If FSF GCC builds on the apple system then I suppose it would need to know
which compiler is being used to bootstrap it , so somewhere in FSF GCC
code/or configure would be the recommended safe way of detecting which.
On Monday 09 March 2009 22:37:58 Bill Hart wrote:
> OK, I did some reading,
OK, I did some reading, and apparently FSF GCC defines __APPLE_CC__ on
Apple machines. So testing if this is defined does not tell you if the
compiler vendor is Apple or FSF.
The reason is that apparently Apple's include files break if this is
not defined by GCC.
I'm surprised we haven't seen th
Hi Mariah,
Perhaps I can answer your question with another.
How would I write the program so that gcc does not identify itself as Apple?
Are you saying that by including stdio.h that it defines __APPLE_CC__?
Are the standard libraries set up to tell me which compiler it is? If
so they are tell
Hi Mariah,
Perhaps I can answer your question with another.
How would I write the program so that gcc does not identify itself as Apple?
Are you saying that by including stdio.h that it defines __APPLE_CC__?
Are the standard libraries set up to tell me which compiler it is? If
so they are tell
Bill,
You claim that there is a problem with gcc-4.3.3 on varro.
I am afraid that I do not understand why you think so.
It looks like you added an include clause to a hello world
program, and then because the include clause was evaluated
you claim there is a problem with gcc. I am confused.
As
On Sat, Mar 7, 2009 at 8:34 PM, Bill Hart wrote:
>
> The problem on varro seems to be a screwed up gcc. This is what you
> get when you type gcc -v:
>
> varro:~/mpir-varro wbhart$ gcc -v
> Using built-in specs.
> Target: powerpc-apple-darwin8.11.0
> Configured with: /usr/local/gcc-4.3.3/src/gcc-4
10 matches
Mail list logo
