From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libxml-parser-perl: make host build use correct compiler
Date: Sun, 7 Jun 2020 10:53:15 +0200 [thread overview]
Message-ID: <20200607105315.5488ddf4@windsurf> (raw)
In-Reply-To: <CADYdroM-KRu5foedcafU8WogfgEJCmMQbk5XYgMv2dDrkf2y7g@mail.gmail.com>
On Sun, 7 Jun 2020 00:29:59 +0200
Norbert Lange <nolange79@gmail.com> wrote:
> > How is it possible for the host and target compilers to have the same
> > file name ?
>
> I use crosstool for a x86_64 target compiler, same architecture as my
> desktop pc.
That is still weird: the native compiler on your system is normally
called "gcc", while the compiler in your toolchain is generally named
x86_64-linux-gcc or some variation on that.
Even though your patch is definitely correct, I'd like to understand
how you fall into this situation. Indeed, I'm pretty sure several other
host packages might be affected, and if this is a valid situation, we
should see if there's a way to test it in our autobuilders.
> On an not entirely unrelated note, I got troubles getting into patchwork,
> did reset my PW 2-3 time, still can't log in. Is there some hidden 8
> letter limit or similar?
I don't think there is such a limitation. This patchwork instance is
not always super stable, yesterday we had 500 errors for a few moments
for example. If you have issues, we can contact the admins of the
instance and see if they can have a look.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-06-07 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 22:58 [Buildroot] [PATCH] package/libxml-parser-perl: make host build use correct compiler Norbert Lange
2020-06-06 20:04 ` Thomas Petazzoni
2020-06-06 22:29 ` Norbert Lange
2020-06-07 8:53 ` Thomas Petazzoni [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=20200607105315.5488ddf4@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.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