On Fri, Apr 12, 2013 at 11:13 AM, Alexander Stavonin
<[email protected]>wrote:
> Looks like same flag (if the reason if missed flag) also have to be passed in
> case of Rust developed programs compilation. I've made simple test:
>
> fn main() {
> io::println("Hellow world")
> }
>
> Compiled it on 10.8 and runed on 10.7. The result is:
>
> Illegal instruction: 4
>
In (Obj-)C(++) world, the flag is passed to the compiler for every object
file compilation, in addition to the final link. I do believe if the
target min version is inconsistent during any part of the process, the
result will be these types of load errors.
>
>
> 2013/4/12 Jarred Nicholls <[email protected]>
>
>> On Thu, Apr 11, 2013 at 2:58 PM, Alexander Stavonin <[email protected]
>> > wrote:
>>
>>> Hi!
>>> I'm going to create Rust installation package for Mac OS X. Right now
>>> you can find the installer there:
>>> http://www.sysdev.me/public/RustInstaller.pkg.zip
>>> But... I've build the installer on 10.8 and when I'm running it on 10.7
>>> result is:
>>>
>>> Segmentation fault: 11
>>>
>>> Is it possible to build Rust on 10.8 and run it on other 10.x systems?
>>>
>>
>> That's a fair question. A Mach-O binary has a load command that
>> specifies the minimum version of OS X it supports, and is settable by
>> Apple's gcc/clang front end by passing the flag -mmacosx-version-min. I
>> don't know what level of control we are given by rustc for such things, so
>> I'm interested in the answer to this as well.
>>
>>
>>>
>>> Regards,
>>> Alexander
>>> _______________________________________________
>>> Rust-dev mailing list
>>> [email protected]
>>> https://mail.mozilla.org/listinfo/rust-dev
>>>
>>
>>
>
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
