From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xtensa in the autobuilders, first build failures
Date: Mon, 19 Nov 2012 23:46:01 +0100 [thread overview]
Message-ID: <20121119234601.6274d4a6@skate> (raw)
In-Reply-To: <50AAA88E.3090603@zankel.net>
Dear Chris Zankel,
On Mon, 19 Nov 2012 13:45:50 -0800, Chris Zankel wrote:
> However, I noticed that it was not the most recent version where I
> incorporated suggestions from Arnout, so will provide a small patch on
> top of it.
Ah, sorry, my bad. Don't hesitate to send a follow-up patch that fixes
the remaining problems.
> > * 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
> Yes, I do have a patch for gdb. There are actually two ways to fix it,
> either in uClibc or gdb. I'm also working with Tensilica to get those
> changes upstream, so I have to avoid providing additional patches.
Great!
> > 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
> Thanks, I will look into it.
Adding support for one architecture in libffi is not very simple, so if
you don't need it for your own projects, I don't think you'll have the
energy to work on this.
> > 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.
> I'm juggling between kernel, uClibc, and buildroot, so, please allow me
> some more time.
Sure, no problem!
> Regarding patches, should I send them to you and cc buildroot, or only
> to the mailing list? What's the best path to get them looked at and
> integrated into the tree?
Just send them to the list. You can Cc: me as well if you want, but I'm
basically reading everything that goes on the Buildroot list, so I
should catch them even if you don't Cc: me.
Thanks again!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-19 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 22:25 [Buildroot] Xtensa in the autobuilders, first build failures Thomas Petazzoni
2012-11-19 21:45 ` Chris Zankel
2012-11-19 22:46 ` Thomas Petazzoni [this message]
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=20121119234601.6274d4a6@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 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.