All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Orling" <ticotimo@gmail.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Khem Raj <raj.khem@gmail.com>,
	 "Orling, Timothy T" <timothy.t.orling@intel.com>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>,
	 Trevor Gamblin <trevor.gamblin@windriver.com>,
	Vinay Kumar <vinay.m.engg@gmail.com>,
	 anbelski@linux.microsoft.com, cardoe@cardoe.com,
	derek@asterius.io,  dev@codyps.com, johan.anderholm@gmail.com,
	martin.jansa@gmail.com,  paul@pbarker.dev,
	saul.wold@windriver.com, steven@stevenwalter.org,
	 tylerwhall@gmail.com, vinay.kumar@blackfigtech.com
Subject: Re: [OE-core] [v4] [RFC] Merge meta-rust to oe-core - Aug 19 update
Date: Fri, 27 Aug 2021 13:09:20 -0700	[thread overview]
Message-ID: <CANx9H-BMdX=J9dHiHUOFg9C9sYpbnmkjybmdHUy5vChWaudPDg@mail.gmail.com> (raw)
In-Reply-To: <23bc2196-4f7c-4958-e191-bd6f47223da2@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 6248 bytes --]

On Thu, Aug 26, 2021 at 9:05 PM Randy MacLeod <randy.macleod@windriver.com>
wrote:

> On 2021-08-24 12:48 p.m., Randy MacLeod wrote:
> > Add Steven Walter in hopes that he or someone else
> > who uses meta-rust will help out.
> >
> > On 2021-08-23 5:21 a.m., Richard Purdie wrote:
> >> On Sun, 2021-08-22 at 08:45 -0400, Randy MacLeod wrote:
> >>> On 2021-08-22 7:19 a.m., Richard Purdie wrote:
> >>>> On Sat, 2021-08-21 at 23:12 -0400, Randy MacLeod wrote:
> >>>>> On 2021-08-20 10:48 p.m., Randy MacLeod wrote:
> >>>>> With a patch from Richard, and the http_proxy check removed,
> >>>>> $ git diff | grep "^[+-]"
> >>>>>    --- a/meta/lib/oeqa/selftest/cases/sstatetests.py
> >>>>>    +++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
> >>>>>    -http_proxy = "http://example.com/"
> >>>>>    +http_proxy = ""
> >>>>> we have fixed the oe-selftest that was failing.
> >>>>>    Any volunteers to stub out the http[s]_proxy code in cargo ?
> >>>>> I've written up a commit log that could use some review and pushed
> >>>>> an update
> >>>>> to:
> >>>>>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=rmacleod/rust-redo-aug-17-2021-a
> >>>>>
> >>>>>
> >>>>
> >>>> I'm not sure you need to change cargo, I think if you remove the bit
> >>>> in the
> >>>> bbclass that injects http_proxy, the tests are ok. That will perhaps
> >>>> break
> >>>> anyone using proxies but for now, I think that is a reasonable step
> >>>> of getting
> >>>> this moved forward?
> >>> That's what I hoped for as well but not what my testing showed.
> >>>
> >>> I removed (commented out actually) the http_proxy injection here:
> >>>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=rmacleod/rust-redo-aug-17-2021-a&id=a4808f787caf8d0b44cf3946cf204164f24f91d4
> >>>
> >>>
> >>> but the test still fails unless I mangle the test:
> >>>
> >>>      meta/lib/oeqa/selftest/cases/sstatetests.py
> >>>
> >>>
> >>>      -http_proxy = "http://example.com/"
> >>>
> >>>
> >>>      +http_proxy = ""
> >> Right, my point is that doesn't remove it. You need to delete it, not
> >> comment it
> >> out.
> >>
> >> The issue is that bitbake does variable expansion on the scripts
> >> before running
> >> them.
> >>
> >> It can't tell that this is a comment, just that the script differs after
> >> variable expansion.
> >>
> >> Cheers,
> >>
> >> Richard
> >>
> >>
> >>
> > Richard has fixed several new issues and is testing this in master-next:
> > http://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=master-next
> >
> > using the YP autobuilder.
> >
> > We're seeing some odd intermittent build failures especially when using
> > the uninative class (used by default in poky) perhaps on older hosts but
> > we're not 100% sure of that correlation yet. See below and:
> >
> >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/116/builds/581/steps/13/logs/stdio
> >
> >
> > If we can't get this fixed in the next day or two, we'll miss the fall
> > release.
> >
> > ../Randy
>
>
> Thanks to Richard's dogged determination and Herculean efforts,
> the Rust recipes are now merged to the oe-core master branch.
>
>     https://git.openembedded.org/openembedded-core/log/?qt=range&q=master
>

Thank you Richard, Randy and everyone else involved.

>
>
> There are still some known problems, such as:
>
> 1. Tim Orling finding that Rust fails to build python-cryptography:
>
>
>
> https://git.openembedded.org/meta-openembedded-contrib/log/?h=timo/rust_python3-cryptography
>

With the patch below, this branch now builds the latest
pyhton3-cryptography 3.4.8. There are some ptest warnings and errors that
are still in progress. Also the recipes in this branch need a final scrub
before submitting.

Happy to have anyone test the branch if you use python3-cryptography.

>
> Tim says that this change helps:
>
>
> https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=timo/rustc-print-cfg-fix


Patch sent to ML for this.

<https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=timo/rustc-print-cfg-fix>


>
> and:
>
> 2. a reproducible build failure on CentOS-7:
>
>     https://autobuilder.yoctoproject.org/typhoon/#/builders/115/builds/597
>
> where, we see:
>     = note: /bin/sh: /lib64/libc.so.6: version `GLIBC_2.33' \
>     not found (required by \
>     /home/pokybuild/yocto-worker/reproducible-centos/build/\
>     build-st/reproducibleB/tmp/work/x86_64-linux/cargo-native/\
>     1.54.0-r0/recipe-sysroot-native/usr/lib/libtinfo.so.5)
>
>
>
>
>
>     error: linking with `\
>     /home/pokybuild/yocto-worker/reproducible-centos/build/\
>     build-st/reproducibleB/tmp/work/x86_64-linux/cargo-native/\
>     1.54.0-r0/wrapper/target-rust-ccld` failed: exit status: 1
>
>
> ---
>
>
> Please test, send patches and/or let me know about any other problems by
> email or by opening  a defect in the YP bugzilla:
>     https://bugzilla.yoctoproject.org/
>
>
> I'll work on a commit for meta-rust to remove the components
> that have been moved to oe-core. I'm not sure what the
> meta-rust developers and users want to do as far as what will
> remain in meta-rust but the short list that I have so far is:
> 1. scripts
> 2. Jenkins tests
> 3. Rust version 1.51.0 ?
>
>
> ../Randy
>
> >
> >
> > error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found
> > (required by
> >
> /home/pokybuild/yocto-worker/reproducible-debian/build/build-st/reproducibleA/tmp/work/x86_64-linux/rust-native/1.54.0-r0/rustc-1.54.0-src/build/bootstrap/debug/deps/libproc_macro_error_attr-9c7a09885c50c72e.so)
>
> >
> >      -->
> >
> /home/pokybuild/yocto-worker/reproducible-debian/build/build-st/reproducibleA/tmp/work/x86_64-linux/rust-native/1.54.0-r0/rustc-1.54.0-src/vendor/proc-macro-error/src/lib.rs:284:9
>
> >
> >   284 | pub use proc_macro_error_attr::proc_macro_error;
> >       |         ^^^^^^^^^^^^^^^^^^^^^
> >
> >   error: aborting due to previous error
> >   error: could not compile `proc-macro-error`
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> # Randy MacLeod
> # Wind River Linux
>
> 
>
>

[-- Attachment #2: Type: text/html, Size: 9826 bytes --]

  parent reply	other threads:[~2021-08-27 20:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  0:22 [v3] [RFC] Merge meta-rust to oe-core Randy MacLeod
2021-08-11 13:14 ` Randy MacLeod
2021-08-11 15:18   ` Randy MacLeod
2021-08-13 15:19   ` [OE-core] [v4] " Vinay Kumar
2021-08-13 15:22     ` Vinay Kumar
2021-08-17 14:52       ` Randy MacLeod
     [not found]       ` <169C1FA457B99CA0.23238@lists.openembedded.org>
2021-08-20 10:06         ` [OE-core] [v4] [RFC] Merge meta-rust to oe-core - Aug 19 update Randy MacLeod
2021-08-21  2:48           ` Randy MacLeod
2021-08-21  8:46             ` Richard Purdie
     [not found]           ` <169D3274AAECC435.19323@lists.openembedded.org>
2021-08-22  3:12             ` Randy MacLeod
2021-08-22 11:19               ` Richard Purdie
2021-08-22 12:45                 ` Randy MacLeod
2021-08-23  9:21                   ` Richard Purdie
2021-08-24 16:48                     ` Randy MacLeod
     [not found]                     ` <169E4C0C80951608.1595@lists.openembedded.org>
2021-08-27  4:05                       ` Randy MacLeod
2021-08-27  9:03                         ` Richard Purdie
     [not found]                           ` <7A95231E-0879-46D6-8653-85338E9BDDFA@amazon.com>
2021-09-01  8:44                             ` Richard Purdie
     [not found]                             ` <16A0A6483A22DE64.7229@lists.openembedded.org>
2021-09-01  9:15                               ` Richard Purdie
     [not found]                         ` <169F1E62C63E8EDC.31425@lists.openembedded.org>
2021-08-27 12:04                           ` Richard Purdie
     [not found]                           ` <169F2844BF9C5B85.31425@lists.openembedded.org>
2021-09-01  8:38                             ` Richard Purdie
2021-08-27 14:31                         ` Armin Kuster
2021-08-27 20:09                         ` Tim Orling [this message]
     [not found]               ` <169D9CED4738B0BB.18298@lists.openembedded.org>
2021-08-22 12:38                 ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANx9H-BMdX=J9dHiHUOFg9C9sYpbnmkjybmdHUy5vChWaudPDg@mail.gmail.com' \
    --to=ticotimo@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=anbelski@linux.microsoft.com \
    --cc=cardoe@cardoe.com \
    --cc=derek@asterius.io \
    --cc=dev@codyps.com \
    --cc=johan.anderholm@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    --cc=raj.khem@gmail.com \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@windriver.com \
    --cc=steven@stevenwalter.org \
    --cc=timothy.t.orling@intel.com \
    --cc=trevor.gamblin@windriver.com \
    --cc=tylerwhall@gmail.com \
    --cc=vinay.kumar@blackfigtech.com \
    --cc=vinay.m.engg@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.