From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: enable CONFIG_USE_PRIVATE_LIBGCC by default (re-send to the correct address)
Date: Fri, 03 Jul 2015 11:53:25 +0200 [thread overview]
Message-ID: <20150703095325.239DB380907@gemini.denx.de> (raw)
In-Reply-To: <CAK7LNATyqVrRn_3rPtsotF5JqF16rxqV0Z9LYCUjwzB4A7AFMw@mail.gmail.com>
Dear Masahiro,
In message <CAK7LNATyqVrRn_3rPtsotF5JqF16rxqV0Z9LYCUjwzB4A7AFMw@mail.gmail.com> you wrote:
>
> > And what do you do about user space with such a broken tool chain?
> >
> > It does not help to paper over problems.
>
> Some people might want to build only U-boot from source code
> and install a pre-built distribution, maybe ?
Yes, of course. And they would be perfectly happy if they had a
_working_ tool chain which supports this.
But some do not, and instead of telling the makers of the ool chain
about our needs and wishes, each and every project works around the
issues, providing copies and copis of the same code, which is isolated
and not centrally maintained, and thus usually of poorer quality than
what you can find in recent tool chain versions.
The optimal way to fix a problem is to have it fixed at the root.
CONFIG_USE_PRIVATE_LIBGCC is a workaround, but enabling it by default
means freezing the status quo: upstream tools will never get fixed.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The price of success is hard work, dedication to the job at hand, and
the determination that whether we win or lose, we have applied the
best of ourselves to the task at hand. - Vince Lombardi
next prev parent reply other threads:[~2015-07-03 9:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 12:37 [U-Boot] [PATCH] ARM: enable CONFIG_USE_PRIVATE_LIBGCC by default Masahiro Yamada
2015-04-16 9:21 ` Albert ARIBAUD
2015-07-01 21:21 ` Albert ARIBAUD
2015-07-01 21:40 ` Albert ARIBAUD
2015-07-02 12:21 ` Masahiro Yamada
2015-07-02 12:43 ` Albert ARIBAUD
2015-07-02 12:54 ` Masahiro Yamada
2015-07-02 13:03 ` Albert ARIBAUD
2015-07-01 21:42 ` [U-Boot] [PATCH] ARM: enable CONFIG_USE_PRIVATE_LIBGCC by default (re-send to the correct address) Albert ARIBAUD
2015-07-01 21:50 ` Wolfgang Denk
2015-07-01 22:04 ` Albert ARIBAUD
2015-07-01 23:39 ` Daniel Schwierzeck
2015-07-02 5:49 ` Albert ARIBAUD
2015-07-02 7:39 ` Wolfgang Denk
2015-07-02 12:40 ` Masahiro Yamada
2015-07-03 9:53 ` Wolfgang Denk [this message]
2015-07-02 12:46 ` Daniel Schwierzeck
2015-07-03 9:59 ` Wolfgang Denk
2015-07-02 12:18 ` Masahiro Yamada
2015-07-02 12:29 ` Masahiro Yamada
2015-07-03 9:29 ` Wolfgang Denk
2015-07-02 7:34 ` Wolfgang Denk
2015-07-02 12:12 ` Masahiro Yamada
2015-07-03 9:25 ` Wolfgang Denk
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=20150703095325.239DB380907@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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