From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>, werner@almesberger.net
Cc: Alexander Aring <alex.aring@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-wpan@vger.kernel.org
Subject: Re: [PATCH atusb/fw v2 2/3] atusb: fw: Update toolchain instructions
Date: Wed, 12 Oct 2022 19:54:49 +0200 [thread overview]
Message-ID: <44a98eb6-e8bb-3065-4c6d-9ffb801182ae@datenfreihafen.org> (raw)
In-Reply-To: <20220906082104.1338694-2-miquel.raynal@bootlin.com>
Hello Miquel.
On 06.09.22 10:21, Miquel Raynal 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.
I can see that it was a frustrating process to get this working. :/
Sorry to hear. The truth is only a handful of people did ever build the
firmware themself, I think. Even I have not done it in a while. (ugh, 5
years ago most likely judging from the git log).
regards
Stefan Schmidt
next prev parent reply other threads:[~2022-10-12 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 8:21 [PATCH atusb/fw v2 1/3] Add .gitignore Miquel Raynal
2022-09-06 8:21 ` [PATCH atusb/fw v2 2/3] atusb: fw: Update toolchain instructions Miquel Raynal
2022-10-12 17:54 ` Stefan Schmidt [this message]
2022-10-15 8:58 ` Miquel Raynal
2022-10-16 1:02 ` Alexander Aring
2022-10-19 19:46 ` Miquel Raynal
2022-10-20 14:17 ` Miquel Raynal
2022-10-20 23:32 ` Alexander Aring
2022-10-21 6:53 ` Miquel Raynal
2022-10-21 12:13 ` Alexander Aring
2022-10-21 13:33 ` Miquel Raynal
2022-09-06 8:21 ` [PATCH atusb/fw v2 3/3] atusb: fw: Provide TRAC status Miquel Raynal
2022-10-12 17:57 ` Stefan Schmidt
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=44a98eb6-e8bb-3065-4c6d-9ffb801182ae@datenfreihafen.org \
--to=stefan@datenfreihafen.org \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--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