Re: rust problem

2017-07-29 Thread Jochen Neumeister


Am 29.07.2017 um 14:01 schrieb Christoph Moench-Tegeder:
> ## Christoph Moench-Tegeder (c...@burggraben.net):
>
>>> I mailed it the maintainer. He said it is a local problem.
>> I'd like to disagree: the problem is caused by this:
> I have to retract this: a poudriere build (10.3 again) completes.
> That shows that the rust build suffers from some environmental
> poisoning... damn.
>
> Regards,
> Christoph
>
I open a PR for this problem:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221088

Cheers
Jochen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: rust problem

2017-07-29 Thread Walter Schwarzenfeld
But you are right. I got it to compile in the port with 
WITHOUT_FBSD10_FIX=yes (I think this unlogical, but it seems to work).


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: rust problem

2017-07-29 Thread Christoph Moench-Tegeder
## Christoph Moench-Tegeder (c...@burggraben.net):

> > I mailed it the maintainer. He said it is a local problem.
> 
> I'd like to disagree: the problem is caused by this:

I have to retract this: a poudriere build (10.3 again) completes.
That shows that the rust build suffers from some environmental
poisoning... damn.

Regards,
Christoph

-- 
Spare Space
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: rust problem

2017-07-29 Thread Christoph Moench-Tegeder
## Walter Schwarzenfeld (w.schwarzenf...@utanet.at):

> Rust does not compile in the port on 10.3 amd64.

I'm just debugging the very same problem.

> I mailed it the maintainer. He said it is a local problem.

I'd like to disagree: the problem is caused by this:

===>  Configuring for rust-1.19.0
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/rustc-1.19.0-src/src/vendor/libssh2-sys/libssh2/config.rpath
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/rustc-1.19.0-src/src/vendor/lzma-sys/xz-5.2.3/build-aux/config.rpath
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/.cargo/registry/src/github.com-1ecc6299db9ec823/libssh2-sys-0.2.6/libssh2/config.rpath
===>   FreeBSD 10 autotools fix applied to 
/wrkdirs/usr/ports/lang/rust/work/.cargo/registry/src/github.com-1ecc6299db9ec823/lzma-sys-0.1.4/xz-5.2.3/build-aux/config.rpath

and that comes from bsd.port.mk line 3091 ff.

But I can't figure out why this shouldn't happen on FreeBSD 11 - as far
as I can figure out right now WITHOUT_FBSD10_FIX isn't set automatically,
nor will the run-autotools-fixup be overridden (but I've limited access
to FreeBSD 11 right now).

Regards,
Christoph

-- 
Spare Space
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


rust problem

2017-07-29 Thread Walter Schwarzenfeld

Rust does not compile in the port on 10.3 amd64.

error: the listed checksum of 
`/usr/ports/lang/rust/work/rustc-1.19.0-src/src/vendor/lzma-sys/xz-5.2.3/build-aux/config.rpath` 
has changed:

expected: c8b4c017079da9dfb3086a0583e60ffe736184d89005dc5973f0bb0fd17c04bb
actual: 561b00eb30ecaef2c9da17bc195e7d2a7ea63facea38ea9849fbb0ed340bebba

directory sources are not intended to be edited, if modifications are 
required then it is recommended that [replace] is used with a forked 
copy of the source



command did not execute successfully: 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/build/x86_64-unknown-freebsd/stage0/bin/cargo" 
"build" "-j" "4" "--target" "x86_64-unknown-freebsd" "-v" "--release" 
"--frozen" "--manifest-path" 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/tools/rust-installer/Cargo.toml"

expected success, got: exit code: 101


Traceback (most recent call last):
  File "/usr/ports/lang/rust/work/rustc-1.19.0-src/x.py", line 20, in 


bootstrap.main()
  File 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/bootstrap/bootstrap.py", 
line 678, in main

bootstrap()
  File 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/bootstrap/bootstrap.py", 
line 670, in bootstrap

run(args, env=env, verbose=rb.verbose)
  File 
"/usr/ports/lang/rust/work/rustc-1.19.0-src/src/bootstrap/bootstrap.py", 
line 142, in run

raise RuntimeError(err)
RuntimeError: failed to run: 
/usr/ports/lang/rust/work/rustc-1.19.0-src/build/bootstrap/debug/bootstrap 
install --verbose --config ./config.toml --jobs 4

*** Error code 1

Stop.
make[1]: stopped in /usr/ports/lang/rust
*** Error code 1

Stop.
make: stopped in /usr/ports/lang/rust


I mailed it the maintainer. He said it is a local problem.


So my question: Does anybody know this error?

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"