On Thu, Oct 16, 2014 at 3:54 PM, Ilya Dmitrichenko
<[email protected]> wrote:
> Thanks Ben, I was just about to reply with the link:
> https://github.com/rust-lang/rust/pull/16156/
>
> Cody, you are welcome to test out the branch, as you are to compile rust
> with OE anyway ;)
>
> On 16 Oct 2014 20:52, "Ben Harris" <[email protected]> wrote:
>>
>> This will be available very soon. There is a pull request in the final
>> stages of review that will allow you to define custom targets with custom
>> linkers, link args, PIC options, etc.
>>
>> That is for building binaries using rustc. I'm not sure what the solution
>> would be for building rustc itself.
>>
Ok I'm trying out this branch with the following in
/home/cody/arm-cody-linux-gnueabihf.json (all contents cribbed from
the rust code specifying the arm-unknown-linux-gnueabihf triple):
----
{
"data_layout" :
"e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:64:128-a0:0:64-n32",
"llvm_target" : "arm-unknown-linux-gnueabi",
"target_endian" : "little",
"target_word_size" : "32",
"arch" : "arm",
"target_os": "linux",
"options" : {
"features" : "+v6,+vfp2"
},
"linker" : "arm-cody-linux-gnueabihf-gcc"
}
----
Unfortunately, it doesn't appear that configure has been updated to
allow non-"supported" targets, so after doing:
$ ../configure --prefix=$HOME/foo --target=$HOME/arm-cody-linux-gnueabihf.json
it complains:
configure: error: unsupported target triples
"/home/cody/arm-cody-linux-gnueabihf.json" found
Is there something I'm missing about configuring here?
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
