mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Peter Mamonov <pmamonov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: sandbox: barebox executable for x86_64 is nonfunctional
Date: Thu, 2 Jul 2020 15:48:38 +0200	[thread overview]
Message-ID: <f106ed79-5a62-8118-48d4-38f2eabac03a@pengutronix.de> (raw)
In-Reply-To: <20200702113523.GA5528@localhost.localdomain>



On 7/2/20 1:35 PM, Peter Mamonov wrote:
> Hello, Ahmad,
> 
> After 54d47eb7e "sandbox: support forcing 32-bit x86" the sandbox barebox 
> executable produced on x86_64 host is nonfunctional, i.e. it exits right after 
> start. Reverting the mentioned commit does fix the problem.  The host is 
> running a bit outdated Debian bullseye/sid, gcc version is "gcc (Debian 9.2.1-19) 9.2.1 
> 20191109". Here are the commands I've used to build and run barebox:
> 
> 	$ export ARCH=sandbox
> 	$ make mrproper && make sandbox_defconfig && make -j4 -s
> 	$ ./barebox
> 	$ echo $?
> 	1

You're right. Apparently I did some last minute fix and only retested that COMPILE_TESTing
works, not that it can actually be started... Luckily there is no release with this
patch yet. I just sent a fix out.

Thanks for the the report,
Ahmad

> 
> Regards,
> Peter
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2020-07-02 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 11:35 Peter Mamonov
2020-07-02 13:48 ` Ahmad Fatoum [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=f106ed79-5a62-8118-48d4-38f2eabac03a@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=pmamonov@gmail.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