From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] clapack: musl patches
Date: Tue, 18 Aug 2015 22:59:38 +0300 [thread overview]
Message-ID: <20150818195938.GB27921@vostro> (raw)
In-Reply-To: <20150817224326.0e40b56f@free-electrons.com>
Mon, Aug 17, 2015 at 10:43:26PM +0200, Thomas Petazzoni wrote:
> To be honest, I was a bit hesitant to add the patch that removes
> uninit.c from the build, as the entire clapack thing looks a bit
> complicated, and doing such a change without upstream's opinion is
> dangerous. However, clapack is not that widely used I believe, so let's
> see if that proposal breaks anything for anyone.
Well, I think it should be ok as long as standalone f2c is not involved.
With standalone f2c things will break, not because of this patch, but
because there will be conflict over libf2c.a. But f2c is not something
I would expect to see in buildroot any time soon.
> Alex, could you submit the two patches you have written to the upstream
> clapack project?
Patches sent upstream, let's see what they will reply.
prev parent reply other threads:[~2015-08-18 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 16:15 [Buildroot] [PATCH] clapack: musl patches Alex Suykov
2015-08-15 17:36 ` Yann E. MORIN
2015-08-17 20:43 ` Thomas Petazzoni
2015-08-18 19:59 ` Alex Suykov [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=20150818195938.GB27921@vostro \
--to=alex.suykov@gmail.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