All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: stsp <stsp2@yandex.ru>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] generic code with i7 bootlin toolchain?
Date: Fri, 5 Nov 2021 22:21:08 +0100	[thread overview]
Message-ID: <20211105212108.GF2400@scaer> (raw)
In-Reply-To: <0eeb0b07-b119-8d8c-b3a1-06064c2bf2ee@yandex.ru>

Sstp, All,

On 2021-11-04 23:59 +0300, stsp spake thusly:
> 04.11.2021 23:36, Yann E. MORIN пишет:
> >>So it looks like the
> >>BR2_TARGET_OPTIMIZATION
> >>is somehow applied not to all
> >>built packages? Why can that be?
> >>Is there any other way I can
> >>utilize bootlin tool-chain for some
> >>"generic" (non-SSE3/4) CPU?
> >You will not be able to use that toolchain for the Phenom. You will have
> >to build your own toolchain.
> >
> >Note that you can build the toolchain once, and later re-use that as a
> >pre-built toolchain. See the manual on directions on how to do that:
> >     https://buildroot.org/downloads/manual/manual.html#_cross_compilation_toolchain
> Thanks, "make sdk" is an
> interesting subject to play with.
> However, any hopes bootlin
> can provide the "generic"
> tool-chain in addition to i7?

That's up to them to decide what they provide and host. Maybe you can
contract with them? ;-)

> Also the doc you mentioned,
> points to some codesourcery
> tool-chain. Where is it?

The manual is not up-to-date in this respect: there is no longer a
CodeSourcery toolchain for x86/x86-64 anymore (see commit d87e114a8ffa).

Regards,
Yann E. MORIN.

> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2021-11-05 21:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 19:52 [Buildroot] generic code with i7 bootlin toolchain? stsp
2021-11-04  1:05 ` Giulio Benetti
2021-11-04 10:02 ` stsp
2021-11-04 14:55   ` Giulio Benetti
2021-11-04 15:07     ` stsp
2021-11-04 20:36 ` Yann E. MORIN
2021-11-04 20:59   ` stsp
2021-11-05 21:21     ` Yann E. MORIN [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=20211105212108.GF2400@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=stsp2@yandex.ru \
    /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.