Hi,
I recently updated Xcode to the last available version (2.4.1) on our
Intel Mac Mini (Mac OS 10.4.8).
Now when I compile a C program with gcc 4.0.3 provided with R-2.4.1.dmg,
the output I get contains several lines like this:
/var/tmp//ccUlRH08.s:2232:indirect jmp without `*'
For example, the "hello world" program produces 1 line like this but
there can be dozens of them even for a small (< 1000 lines) program.
It looks like 'as' is complaining about the output produced by
gcc 4.0.3. Could this affect the stability of the resulting
executable? How can this be fixed? Thanks!
System: Intel Mac Mini with Mac OS 10.4.8
Xcode: 2.4.1 (or 2.4.0)
gcc: 4.0.3 provided with R-2.4.1.dmg
How to reproduce: try to compile
#include <stdio.h>
main() {printf("hello world\n");}
No problem when compiling with /usr/bin/gcc (Apple gcc, version 4.0.1).
Cheers and Happy New Year!
H.
PS: This problem affects many Bioconductor packages.
Pb with gcc 4.0.3 (from R-2.4.1.dmg) and last Xcode
5 messages · Byron Ellis, Simon Urbanek, Hervé Pagès
Yeah, it's really annoying isn't it? It affects basically all packages with C code, but it doesn't seem to be harmful.
On 1/3/07, Herve Pages <hpages at fhcrc.org> wrote:
Hi,
I recently updated Xcode to the last available version (2.4.1) on our
Intel Mac Mini (Mac OS 10.4.8).
Now when I compile a C program with gcc 4.0.3 provided with R-2.4.1.dmg,
the output I get contains several lines like this:
/var/tmp//ccUlRH08.s:2232:indirect jmp without `*'
For example, the "hello world" program produces 1 line like this but
there can be dozens of them even for a small (< 1000 lines) program.
It looks like 'as' is complaining about the output produced by
gcc 4.0.3. Could this affect the stability of the resulting
executable? How can this be fixed? Thanks!
System: Intel Mac Mini with Mac OS 10.4.8
Xcode: 2.4.1 (or 2.4.0)
gcc: 4.0.3 provided with R-2.4.1.dmg
How to reproduce: try to compile
#include <stdio.h>
main() {printf("hello world\n");}
No problem when compiling with /usr/bin/gcc (Apple gcc, version 4.0.1).
Cheers and Happy New Year!
H.
PS: This problem affects many Bioconductor packages.
_______________________________________________ R-SIG-Mac mailing list R-SIG-Mac at stat.math.ethz.ch https://stat.ethz.ch/mailman/listinfo/r-sig-mac
Byron Ellis (byron.ellis at gmail.com) "Oook" -- The Librarian
Hi Byron, Yes it's annoying. Hope it is not harmful as you say. Thanks! H.
Byron Ellis wrote:
Yeah, it's really annoying isn't it? It affects basically all packages with C code, but it doesn't seem to be harmful. On 1/3/07, Herve Pages <hpages at fhcrc.org> wrote:
Hi,
I recently updated Xcode to the last available version (2.4.1) on our
Intel Mac Mini (Mac OS 10.4.8).
Now when I compile a C program with gcc 4.0.3 provided with R-2.4.1.dmg,
the output I get contains several lines like this:
/var/tmp//ccUlRH08.s:2232:indirect jmp without `*'
For example, the "hello world" program produces 1 line like this but
there can be dozens of them even for a small (< 1000 lines) program.
It looks like 'as' is complaining about the output produced by
gcc 4.0.3. Could this affect the stability of the resulting
executable? How can this be fixed? Thanks!
System: Intel Mac Mini with Mac OS 10.4.8
Xcode: 2.4.1 (or 2.4.0)
gcc: 4.0.3 provided with R-2.4.1.dmg
How to reproduce: try to compile
#include <stdio.h>
main() {printf("hello world\n");}
No problem when compiling with /usr/bin/gcc (Apple gcc, version 4.0.1).
Cheers and Happy New Year!
H.
PS: This problem affects many Bioconductor packages.
_______________________________________________ R-SIG-Mac mailing list R-SIG-Mac at stat.math.ethz.ch https://stat.ethz.ch/mailman/listinfo/r-sig-mac
1 day later
Herve,
On Jan 3, 2007, at 11:31 PM, Herve Pages wrote:
I recently updated Xcode to the last available version (2.4.1) on our Intel Mac Mini (Mac OS 10.4.8). Now when I compile a C program with gcc 4.0.3 provided with R-2.4.1.dmg, the output I get contains several lines like this: /var/tmp//ccUlRH08.s:2232:indirect jmp without `*'
This is harmless, merely a warning and stems from the fact that Apple changed the behavior of the assembler on Intel Macs (for better - it is now more compatible with other assemblers - but consequently incompatible with its previous behavior). Although the most recent Xcode fixed the fatal bugs that forced us to use our own compiler, we can't switch to Apple's gcc until R 2.5.0 due to binary incompatibility between the two (see R for Mac FAQ). If you build you own R, feel free to use Xcode's gcc. Cheers, Simon
Hi Simon,
Simon Urbanek wrote:
Herve, On Jan 3, 2007, at 11:31 PM, Herve Pages wrote:
I recently updated Xcode to the last available version (2.4.1) on our Intel Mac Mini (Mac OS 10.4.8). Now when I compile a C program with gcc 4.0.3 provided with R-2.4.1.dmg, the output I get contains several lines like this: /var/tmp//ccUlRH08.s:2232:indirect jmp without `*'
This is harmless, merely a warning and stems from the fact that Apple changed the behavior of the assembler on Intel Macs (for better - it is now more compatible with other assemblers - but consequently incompatible with its previous behavior).
Thanks for the details!
Although the most recent Xcode fixed the fatal bugs that forced us to use our own compiler, we can't switch to Apple's gcc until R 2.5.0 due to binary incompatibility between the two (see R for Mac FAQ). If you build you own R, feel free to use Xcode's gcc.
That's good to know but no thanks :-) I like being able to update my R devel in less than 1 min. by downloading the last universal build from http://r.research.att.com/ (thanks a lot for providing this). Also, I like being able to use the other universal stuff provided there (like graphviz-2.8.dmg and glibgtk-bin-1.2.10-univ.tar.gz) that would then become incompatible with my home made R (compiled with Xcode's gcc). Is that correct? Besides, Apple still does not provide a Fortran compiler, do they? Cheers, H.
Cheers, Simon