You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 4078 Reporter: garymawdsley Status: closed (set by @xavierleroy on 2006-08-19T07:50:59Z) Resolution: not a bug Priority: normal Severity: major Version: 3.09.2 Category: ~DO NOT USE (was: OCaml general)
Bug description
When using ocaml on a new intel based iMac I get a warning reported when trying to compile the npict which is built atop of ocaml. The warning appears to lead to a collect2: ld returned 1 exit status
The warning issued is "libcamlrun.a archive's cputype 18 (ppc) does not match cputype 7 (intel)"
Additional information
I cannot find a specific info about intel macs at the caml site, only that it appears they are now supported?
The text was updated successfully, but these errors were encountered:
You're probably using the PowerPC version of OCaml. (The binary distribution
of OCaml for MacOSX is for the PowerPC.) That version runs on MacOSX/Intel
in emulation mode, but as you noticed the interface with C code compiled for Intel won't obviously work.
MacOSX/Intel is supported by OCaml since release 3.09.2, but currenty you have to compile OCaml from sources, there is no binary distribution yet.
Original bug ID: 4078
Reporter: garymawdsley
Status: closed (set by @xavierleroy on 2006-08-19T07:50:59Z)
Resolution: not a bug
Priority: normal
Severity: major
Version: 3.09.2
Category: ~DO NOT USE (was: OCaml general)
Bug description
When using ocaml on a new intel based iMac I get a warning reported when trying to compile the npict which is built atop of ocaml. The warning appears to lead to a collect2: ld returned 1 exit status
The warning issued is "libcamlrun.a archive's cputype 18 (ppc) does not match cputype 7 (intel)"
Additional information
I cannot find a specific info about intel macs at the caml site, only that it appears they are now supported?
The text was updated successfully, but these errors were encountered: