From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E553AC001B0 for ; Mon, 7 Aug 2023 14:07:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 6D60581EB9; Mon, 7 Aug 2023 14:07:13 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 6D60581EB9 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8iYpjFpD-GW4; Mon, 7 Aug 2023 14:07:12 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp1.osuosl.org (Postfix) with ESMTP id 945B6818A1; Mon, 7 Aug 2023 14:07:11 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 945B6818A1 Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by ash.osuosl.org (Postfix) with ESMTP id 38CD31BF97A for ; Mon, 7 Aug 2023 14:07:08 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 5196660EE4 for ; Mon, 7 Aug 2023 14:06:41 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 5196660EE4 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JaH9HZyF8wq8 for ; Mon, 7 Aug 2023 14:06:40 +0000 (UTC) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by smtp3.osuosl.org (Postfix) with ESMTPS id D61FA606E6 for ; Mon, 7 Aug 2023 14:06:39 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org D61FA606E6 Received: by mail.gandi.net (Postfix) with ESMTPSA id 51665E000F; Mon, 7 Aug 2023 14:06:36 +0000 (UTC) Date: Mon, 7 Aug 2023 16:06:35 +0200 To: Andreas Message-ID: <20230807160635.0c4da553@windsurf> In-Reply-To: References: <20230806235806.307605e5@windsurf> Organization: Bootlin X-Mailer: Claws Mail 4.1.1 (GTK 3.24.38; x86_64-redhat-linux-gnu) MIME-Version: 1.0 X-GND-Sasl: thomas.petazzoni@bootlin.com X-Mailman-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1691417196; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9vES63HPOChocuTubZXUOQVCAatYd72/On0qOVjolyY=; b=IOCK1MGGI0VEmbUeYLsqlNMNtOExffDe47ID93kF3KCduAnD5wDAQ7tKohJwKuQqcr7EeB e2+9limToQH6lslnKOVG6MTCtQFQE5IbZ409Ia62MtIG7WW2wfnm/Tq/VdDvBv2KIEP87R tQhrZyMu3bOaYEuiccTI1N69jTprj80wM/9K5umh0J3DBwY6s+8YSCoUqaIaelIX+CQQpa +HiS1JlDV4BJtC6Y+jA74Z2ett/m1L51xNHlkjlnAN9/bepqA51JU68QxoT5shroz5P8qt Jlj29HPtuI2HGLU6Bxm8Q7gE7yFoWHk9uquFnrUOLfEwZWdkWndm7IKSpz16Ag== X-Mailman-Original-Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=bootlin.com header.i=@bootlin.com header.a=rsa-sha256 header.s=gm1 header.b=IOCK1MGG Subject: Re: [Buildroot] Support for lapack X-BeenThere: buildroot@buildroot.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Thomas Petazzoni via buildroot Reply-To: Thomas Petazzoni Cc: buildroot@buildroot.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: buildroot-bounces@buildroot.org Sender: "buildroot" Hello, On Mon, 7 Aug 2023 15:41:53 +0200 Andreas 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