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] Xtensa in the autobuilders, first build failures
Date: Sun, 18 Nov 2012 23:25:18 +0100	[thread overview]
Message-ID: <20121118232518.091b6154@skate> (raw)

Hello Chris,

As you have probably noticed, we merged your Xtensa support in
Buildroot a few days ago. I'm really happy that your patches came in,
as it means that the removal of the Xtensa architecture will not be
visible (we removed it during this development cycle, and later
re-introduced it thanks to your patches).

I have also added one Xtensa toolchain configuration in our
autobuilder, and we are therefore starting to see a few Xtensa-related
build issues. Note that this is not at all a blocking issue for now:
when a new architecture is introduced, we expect to have build
failures. I'm listing below the failures we had, in case you have some
time to look at them:

 * Failure to build gdbserver for the target, and gdb for the target as
   well, both for the same reason: PTRACE_GETXTREGS and
   PTRACE_SETXTREGS are not defined by the kernel headers apparently.
   I'm not sure if they are just missing from the kernel headers, of
   the ptrace support is missing in the kernel. See:

   http://autobuild.buildroot.org/results/1d2f307b2aa59bebca3bcb9ea854839f4b1d14fb/build-end.log
   http://autobuild.buildroot.org/results/ec58e302030b8f72b19e9bada16dabb076c60261/build-end.log

   It would be nice if you could have a look at this.

 * Xtensa apparently does not have libffi support. However, it is quite
   a bit of work to get libffi support, so maybe we should just mark
   libffi as not available on Xtensa (which is quite annoying because
   libffi is a dependency for a huge number of packages, but we have
   the same problem with other architectures as well). See:

   http://autobuild.buildroot.org/results/e097c27d38e49d4bf4e07f95c52e995709c08aa8/build-end.log

Besides those issues, I'm just reminding you that we are still very
interested in having a Qemu Xtensa configuration to be able to run the
Xtensa systems we generate with Buildroot.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

             reply	other threads:[~2012-11-18 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 22:25 Thomas Petazzoni [this message]
2012-11-19 21:45 ` [Buildroot] Xtensa in the autobuilders, first build failures Chris Zankel
2012-11-19 22:46   ` Thomas Petazzoni
2012-11-21  0:35     ` Chris Zankel
2012-11-21 12:30       ` Thomas Petazzoni

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=20121118232518.091b6154@skate \
    --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