Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [External] Re: Issues with cross-compiling from x86_64 to a different x86_64
Date: Wed, 20 Jul 2016 22:02:58 +0200	[thread overview]
Message-ID: <20160720220258.46331635@free-electrons.com> (raw)
In-Reply-To: <34C69F44FE4EA4498813EAECDBF40C1623A47405@GUSALE0B.na.utcmail.com>

Hello,

On Wed, 20 Jul 2016 02:49:45 +0000, Arguin, Christopher P     UTAS
wrote:

> I dug into it more and found the source of the problem, which is in
> ncftp itself. As part of the 'configure' script it actually creates a
> 'ccdv.c' file and compiles it, apparently using the wrong compiler.
> Then this 'ccdv' tool is used throughout the build process instead of
> CC. It was to make the compilation output prettier.

Thanks for the investigation!

> It's not directly AVX-related, but from the BMI instruction set...
> the actual failure is the "andn" instruction. I still need to dig
> into it more to understand what's going on there.
> 
> There is a configure option to disable use of ccdv, so I may give
> that shot. Then I have to go look at what is going on in openssl. I
> guess you can probably expect a patch or two from me this week :)

Looks like indeed passing --disable-ccdv is the best way forward.

However, I don't understand why on my system, ccdv doesn't get built,
while it does get built for you.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-07-20 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 18:13 [Buildroot] Issues with cross-compiling from x86_64 to a different x86_64 Arguin, Christopher P UTAS
2016-07-19 22:01 ` Thomas Petazzoni
2016-07-20  2:07   ` [Buildroot] [External] " Arguin, Christopher P UTAS
2016-07-20  2:49   ` Arguin, Christopher P UTAS
2016-07-20 20:02     ` Thomas Petazzoni [this message]
2016-07-20 23:12       ` Arguin, Christopher P UTAS
2016-07-21  7:22         ` Thomas Petazzoni
2016-07-21 11:28           ` Romain NAOUR
2016-07-22  0:16             ` Arguin, Christopher P UTAS

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=20160720220258.46331635@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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