From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] flags to build Qt5 for AMD Geode LX arch ?
Date: Tue, 29 Jan 2019 19:33:48 +0100 [thread overview]
Message-ID: <20190129183348.GL7130@scaer> (raw)
In-Reply-To: <bb5b237e-ba8d-6857-f475-1960a6375112@gmx.com>
David, All,
On 2019-01-29 19:28 +0100, David Picard spake thusly:
> I can build Qt5 successfully. I tested my custom application in QEMU, with
> the same disk.img that I use on the read target (AMD Geode LX).
>
> But on the target, whenever I link one of my programs with Qt5, it
> terminates straight away with a SIGILL (illegal instruction). Including a
> simple printf("Hello world") that doesn't include nor call in Qt5.
[--SNIP--]
> I thought I could pass e.g. -march=geode when I build Qt. But I don't know
> how to do it. I noticed a arch.conf file in the build directory but it gest
> overwritten when I make qt5base-reconfigure...
Well, if even a program that is not linked to Qt failes, you won;t solve
that by only "fixing" it in Qt...
In that cas, since your processor is a geode, you have to confiugyure
Buildroot to generate code for that processor, i.e.: BR2_x86_geode=y
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-01-29 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 18:28 [Buildroot] flags to build Qt5 for AMD Geode LX arch ? David Picard
2019-01-29 18:33 ` Yann E. MORIN [this message]
2019-01-30 7:46 ` David Picard
2019-01-30 10:21 ` David Picard
2019-01-30 14:39 ` David Picard
2019-01-31 21:24 ` Arnout Vandecappelle
2019-01-31 22:49 ` Peter Seiderer
2019-02-01 6:53 ` David Picard
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=20190129183348.GL7130@scaer \
--to=yann.morin.1998@free.fr \
--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 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.