Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-11
Date: Sun, 14 May 2017 19:45:06 +0200	[thread overview]
Message-ID: <20170514174506.GA16283@itchy> (raw)
In-Reply-To: <20170512062950.23CF0220A8@mail.free-electrons.com>

Hi!

On 17-05-12 08:29:50, Thomas Petazzoni wrote:

>        sparc |                skalibs-2.4.0.2 | NOK | http://autobuild.buildroot.net/results/85062b5f9dbe74d7d1c6edfeda085268ecaef4c2 |

This one is puzzling. The configure steps ends with the following error:

```
Checking whether system has auto-close after fd-passing...
  ... test crashed, aborting.
  make: ***
  [/accts/mlweber1/instance-2/output/build/skalibs-2.4.0.2/.stamp_configured]
  Error 111
  make: Leaving directory `/accts/mlweber1/instance-2/buildroot'
```

The configure script tries to cross-compile and execute a program
(tryancilautoclose). The cross-compilation succeeds and of course the
execution fails, as it means running a program compiled for the
SPARC architecture on a x86 machine. Normally, the shell which executes
the program should return the code 126, as mentioned in the list of Bash
exit codes with special meaning [1].

Here the exit code is 111. When looking at tryancilautoclose.c, we can
see that 111 may be returned.

So this error means that either the shell managed to execute the
cross-compiled program or the shell does not follow the convention [1].

Which are the architecture of the build machine and the shell used?

[1] http://tldp.org/LDP/abs/html/exitcodes.html

--
ELB

  reply	other threads:[~2017-05-14 17:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12  6:29 [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-11 Thomas Petazzoni
2017-05-14 17:45 ` Eric Le Bihan [this message]
2017-05-14 19:19   ` Thomas Petazzoni
2017-05-15  1:09     ` Matthew Weber
2017-05-15  2:53       ` Matthew Weber
2017-05-15  3:03         ` Matthew Weber
2017-05-15  7:23           ` Thomas Petazzoni
2017-05-24  1:54             ` Matthew Weber

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=20170514174506.GA16283@itchy \
    --to=eric.le.bihan.dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox