Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas <andreasembbuild@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Support for lapack
Date: Mon, 7 Aug 2023 16:06:35 +0200	[thread overview]
Message-ID: <20230807160635.0c4da553@windsurf> (raw)
In-Reply-To: <CAOLWrZ8p5g6xSYjXrDYseTDz_wW0MqWQ81EpeiHf788NnwhN8Q@mail.gmail.com>

Hello,

On Mon, 7 Aug 2023 15:41:53 +0200
Andreas <andreasembbuild@gmail.com> wrote:

> Thanks for the hint. I followed this patch. I think from the errors I saw
> my problem is most likely the toolchain. This dependency
> respectively depends on BR2_TOOLCHAIN_HAS_FORTRAN # python-scipy. Since I
> am migrating from an old buildroot to a recent version of it might also be
> part of the problem. I know the toolchain menu in the menu config but like
> to set it programatically in the build config.

Not sure to understand what you mean here by "set it programmatically".

> But I don't know how exactly
> and which options depend on what. Basically I think I need a toolchain with
> support for c++, wchar, threads, fortran, openblas and arch.

Then use a toolchain that provides all of this, or ask Buildroot to
build its own toolchain with those features enabled.

> I found this
> resource:
> http://underpop.online.fr/b/buildroot/en/dependencies-target-toolchain-options.htm.gz

Not sure why you go to some random website. This content comes from the
Buildroot manual, see section 18.2.4 at
https://buildroot.org/downloads/manual/manual.html.

> but
> still don't know how to set it properly in the config. Can you point me to
> an example?

I don't quite understand what problem you're trying to solve, so it's
quite difficult to help.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-08-07 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 21:36 [Buildroot] Support for lapack Andreas
2023-08-06 21:58 ` Thomas Petazzoni via buildroot
2023-08-07 13:41   ` Andreas
2023-08-07 14:06     ` Thomas Petazzoni via buildroot [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=20230807160635.0c4da553@windsurf \
    --to=buildroot@buildroot.org \
    --cc=andreasembbuild@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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