pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Rust still broken on 9.0-STABLE i386



Havard Eidnes <he%NetBSD.org@localhost> writes:

>> Attached is a diff which caused my attempted mostly-static cross
>> build for i386 to succeed.  This is an optional thing, not
>> enabled by default, ref. the commented-out remark, and only works
>> in conjunction with the modified gcc-wrap script, which is only
>> used when cross-building.  I'm currently uploading the build
>> result, it'll be a while till it's there.
>
> The bootstrap is now mostly-static:

You say "is" but I am having a hard time following.

Can you explain in terms of:

  is this mostly-static bootstrap creation according to what is checked
  in now?

  is the i386 bootstrap the result of what was checked in earlier, or
  what is checked in now, or basically the same?

  have you arrived, with uncommitted patches, at a way to produce a
  bootstrap that runs on 9 and current without needing openssl?

  do you think what you have done is stable enough to commit during the freeze?

> However...
>
> running: /usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/cargo build --manifest-path /usr/pkgsrc/lang/rust/work/rustc-1.45.2-src/src/bootstrap/Cargo.toml --frozen
> /usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/cargo: text relocations
> /usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/cargo: text relocations
> /usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/cargo: text relocations
> error: process didn't exit successfully: `/usr/pkgsrc/lang/rust/work/rust-bootstrap/bin/rustc -vV` (signal: 6, SIGABRT: process abort signal)
>
> and
>
> : {47} setenv LD_LIBRARY_PATH `pwd`/work/rust-bootstrap/lib
> : {48} work/rust-bootstrap/bin/rustc
> /usr/pkgsrc/lang/rust/work/rust-bootstrap/lib/librustc_driver-c4aa8c2d5ae1470c.so: text relocations
> Abort (core dumped)
> : {49} readelf -a /usr/pkgsrc/lang/rust/work/rust-bootstrap/lib/librustc_driver-c4aa8c2d5ae1470c.so | grep TEXTREL
>  0x00000016 (TEXTREL)                    0x0
>  0x0000001e (FLAGS)                      TEXTREL BIND_NOW STATIC_TLS
> : {50} 
>
> Dang!  Any advice?  Was it a bad idea to try to do libstdc++
> statically, or is this perhaps something else entirely?

So it seems like this is not ready :-(

Attachment: signature.asc
Description: PGP signature



Home | Main Index | Thread Index | Old Index