From: "Alex Bennée" <alex.bennee@linaro.org>
To: Alessandro Di Federico <ale@rev.ng>
Cc: Brian Cain <bcain@quicinc.com>,
tsimpson@quicinc.com, Anton Johansson via <qemu-devel@nongnu.org>
Subject: Re: CI for qemu-hexagon
Date: Wed, 05 Jan 2022 18:53:50 +0000 [thread overview]
Message-ID: <87zgoahuyp.fsf@linaro.org> (raw)
In-Reply-To: <20220105185720.0d4fc159@orange>
Alessandro Di Federico <ale@rev.ng> writes:
> Hi Alex, I hope you enjoyed the holidays!
>
> We're trying to upstream idef-parser (the automatic generator of the
> Hexagon frontend). This introduces new dependencies, specifically flex
> and bison.
>
> Attached you can find our patch for that.
>
> However the CI fails:
>
> https://gitlab.com/carl.cudig/qemu/-/jobs/1939950230
>
> AFAIU the Hexagon docker image is "special" since it's the only one
> that needs the cross-compiler to be built from source and, therefore,
> it's a process that needs to be triggered manually.
It's not that special now - we have the same for microblaze and nios2
(and more are coming). There was a build that moved the hexagon
toolchain to using prebuilts hosted by QC but it ran into problems and
I'm waiting for an update to that/
> Is this correct?
>
> If so, what should we do? Make a pull request despite the failure and
> then it will be taken care of, or should I make a separate (preliminary)
> pull request just for that patch?
Just include the patch to update the docker file in the series that
introduces the feature and mention it in the cover letter. Users can
always build the container locally and we can ensure the binary image is
updated once it's merged.
--
Alex Bennée
prev parent reply other threads:[~2022-01-05 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 17:57 CI for qemu-hexagon Alessandro Di Federico via
2022-01-05 18:53 ` Alex Bennée [this message]
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=87zgoahuyp.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=ale@rev.ng \
--cc=bcain@quicinc.com \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.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.