On Fri, Jun 24, 2022 at 10:39:00AM -0700, Alan Coopersmith wrote:
> What that's telling you is that it can't find which IPS package to list
> for the dependency on libLLVM-13.so - most commonly this means a missing
> entry in the REQUIRED_PACKAGES list in the Userland Makefile - which the
> first c
On Fri, Jun 24, 2022 at 06:23:18PM +0200, Friedrich Kink via oi-dev wrote:
> Oh forgot just for the sake of completeness and the brave who want test on
> the own here my current Makefile:
I'll bet you have a $HOME/.cargo directory.
> # Put the bits cargo downloads in a private directory. This co
On 6/24/22 09:19, Friedrich Kink via oi-dev wrote:
I'm making progress ;-). The only remaining problems I still have are:
builduser@userland:/usr/src/myoi-userland/components/developer/rust$ make
REQUIRED_PACKAGES
/usr/bin/python3.9 RESOLVE_DEPS=
/usr/src/myoi-userland/components/developer/r
Oh forgot just for the sake of completeness and the brave who want test
on the own here my current Makefile:
BUILD_BITS= 64
USE_OPENSSL11= yes
include ../../../make-rules/shared-macros.mk
COMPONENT_NAME= rustc
COMPONENT_VERSION= 1.61.0
COMPONENT_FMRI=
I'm making progress ;-). The only remaining problems I still have are:
builduser@userland:/usr/src/myoi-userland/components/developer/rust$
make REQUIRED_PACKAGES
/usr/bin/python3.9 RESOLVE_DEPS=
/usr/src/myoi-userland/components/developer/rust/build/.resolved-i386
/usr/bin/python3.9: can't o
Hi all,
thanks a lot for hints you shared. My current status is: I've still
exactly the same issue as mentioned below. But the build and install
process is now running and finishing as expected. During the course of
all the different tests I noticed another problem that despite the
configurat
> thanks a lot again, this helped to successfully build and install the rust
> package. Nevertheless the original issue still persists:
[...]
> /usr/bin/python3.9 RESOLVE_DEPS=
> /usr/src/myoi-userland/components/developer/rust/build/.resolved-i386
> /usr/bin/python3.9: can't open file
> '/usr/shar
Hi Till,
thanks a lot again, this helped to successfully build and install the
rust package. Nevertheless the original issue still persists:
Dist rustc-1.61.0-x86_64-unknown-illumos
finished in 46.721 seconds
Install rustc stage2 (Some(TargetSelection { triple:
"x86_64-unknown-illumos
Hello everyone
We now have support for CLONEY_MODE=hardlinks and CLONEY_MODE=copy in
the makefiles
Would be a good chance to test those.
Alternatively COMPONENT_COPY_ACTION would be the proper variable to
override instead of COMPONENT_PRE_CONFIGURE_ACTION
Greetings
Till
On 20/06/2022 17.0
On Mon, Jun 20, 2022 at 09:21:58PM +0200, Andreas Wacknitz wrote:
> We already had another guy trying to build a newer rust failing with the
> same problem.
> He found out that this is a known problem and there should already be a
> fix (as far as I understood) but it hadn't been integrated in the
Am 20.06.22 um 21:18 schrieb Friedrich Kink via oi-dev:
Hi Till,
thanks a lot this is indeed a very valuable hint. Unfortunately since
a couple of compile runs installation fails at the very end with the
following error:
...
Install analysis stage2 (Some(TargetSelection { triple:
"x86_64-unkno
Hi Till,
thanks a lot this is indeed a very valuable hint. Unfortunately since a
couple of compile runs installation fails at the very end with the
following error:
...
Install analysis stage2 (Some(TargetSelection { triple:
"x86_64-unknown-illumos", file: None }))
install: creating uninsta
Hey Fritz
That must be a syntax error in the Makefile. The resolver logic is built
into OI-userland and should not get impacted by modifications to
Makefile of a component. However for some reason 'RESOLVE_DEPS=' leaks
into the final filepath. That should not happen.
Looking at you Makefile
On Sun, Jun 19, 2022 at 11:05:48AM +0200, Friedrich Kink wrote:
> Thanks a lot for your response. Let me give some more information. This
> patch helped me to over come your issue:
>
> --- rustc-1.61.0-src/src/bootstrap/builder.rs 2022-05-18
> 03:29:36.0 +
> +++ rustc-1.61.0-src/src/
Thanks a lot for your response. Let me give some more information. This
patch helped me to over come your issue:
--- rustc-1.61.0-src/src/bootstrap/builder.rs 2022-05-18
03:29:36.0 +
+++ rustc-1.61.0-src/src/bootstrap/builder.rs.new 2022-06-06
21:25:45.179276851 +
@@ -1304,7
On Sun, 19 Jun 2022 at 03:31, Gary Mills wrote:
> On Sat, Jun 18, 2022 at 03:49:33PM +0200, Friedrich Kink via oi-dev wrote:
> > I try to prepare new rustc package with current version 1.61.0. So far
> > building and installing is already working. But publishing respectively make
> > REQUIRED_PACK
On Sat, Jun 18, 2022 at 03:49:33PM +0200, Friedrich Kink via oi-dev wrote:
>
> I try to prepare new rustc package with current version 1.61.0. So far
> building and installing is already working. But publishing respectively make
> REQUIRED_PACKAGES immediately bails out with the following error me
Dear all,
I try to prepare new rustc package with current version 1.61.0. So far
building and installing is already working. But publishing respectively
make REQUIRED_PACKAGES immediately bails out with the following error
message:
make REQUIRED_PACKAGES
/usr/bin/python3.9 RESOLVE_DEPS=
/us
18 matches
Mail list logo
