From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: werner@almesberger.net,
Stefan Schmidt <stefan@datenfreihafen.org>,
Alexander Aring <alex.aring@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-wpan - ML <linux-wpan@vger.kernel.org>
Subject: Re: [PATCH atusb/fw 1/2] atusb: fw: Update toolchain instructions
Date: Tue, 6 Sep 2022 09:56:58 +0200 [thread overview]
Message-ID: <20220906095658.492ff6cd@xps-13> (raw)
In-Reply-To: <CAK-6q+hM5_uVurQL3ctrWcpF6EozcNSkC0uZF3n5AxispSM8uQ@mail.gmail.com>
Hi Alexander,
aahringo@redhat.com wrote on Mon, 5 Sep 2022 19:33:47 -0400:
> Hi,
>
> On Mon, Sep 5, 2022 at 4:43 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > Those instructions do not work anymore for several reaons:
> > - Two out of the three files to download return a 404 error:
> > * The binutils version does not exist, it was 2.21.1 or 2.21.1a
> > instead of just 2.21.
> > * The avr-libc is no longer hosted on the pointed website, I've
> > found an alternate.
> > - The binutils version mentioned is not able to compile the firmware on
> > a recent distribution, the Internet advised to update its version and
> > it worked.
> > - Most of these compilations will throw warnings if you use a recent
> > gcc. Sometimes -Werror is set and it fails the build. To avoid that,
> > just use --disable-werror in the ./configure options.
> > - I had issues building the gcc doc but those issues are trivial to
> > fix inline.
> >
> > Update the instructions for building the toolchain and while at it,
> > start the file by mentioning that this is maybe not useful anymore, and
> > provide the packets to install.
> >
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > ---
> > atusb/fw/README | 18 ++++++++++--------
> > 1 file changed, 10 insertions(+), 8 deletions(-)
> >
> > diff --git a/atusb/fw/README b/atusb/fw/README
> > index 99ceb22..44f65f5 100644
> > --- a/atusb/fw/README
> > +++ b/atusb/fw/README
> > @@ -1,4 +1,6 @@
> > -Requires a very recent toolchain, because ATmega32U2 is relatively new.
> > +- Toolchain:
> > +
> > + apt install avr-gcc libc-avr
> >
>
> grml, it's just the other name around... but I think an important
> notice is here "use the debian packages".
>
> gcc-avr avr-libc
>
> I know it was swapped and was not checking it... it was a 50/50 chance.
Haha I blindly trusted you, I should have double checked.
Thanks,
Miquèl
prev parent reply other threads:[~2022-09-06 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 20:43 [PATCH atusb/fw 1/2] atusb: fw: Update toolchain instructions Miquel Raynal
2022-09-05 20:43 ` [PATCH atusb/fw 2/2] atusb: fw: Provide TRAC status Miquel Raynal
2022-09-06 0:16 ` Alexander Aring
2022-09-06 0:19 ` Alexander Aring
2022-09-06 8:08 ` Miquel Raynal
2022-09-05 23:33 ` [PATCH atusb/fw 1/2] atusb: fw: Update toolchain instructions Alexander Aring
2022-09-06 7:56 ` Miquel Raynal [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=20220906095658.492ff6cd@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=aahringo@redhat.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=werner@almesberger.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).