All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Open bug overview: help wanted!
Date: Wed, 16 Jul 2014 09:31:05 +0200	[thread overview]
Message-ID: <20140716093105.79a705aa@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LU8ZkC4uk5qkq8HGN-zfL=MwAKJP4E=1sDNRDMSJwUutw@mail.gmail.com>

Dear Thomas De Schampheleire,

On Sat, 12 Jul 2014 20:50:42 +0200, Thomas De Schampheleire wrote:

> https://bugs.busybox.net/show_bug.cgi?id=7208 critical
> unassigned at buildroot.uclibc.org Glibc C++ aplications crash if they
> use exceptions.
> This problem is caused by a patch adding musl support. How to proceed?

A solution was suggested by Rich Felker in the bug report. My plan is
to work on implementing this solution, but I was hoping to fix bug
#7250 first, which also affects the toolchain.

> https://bugs.busybox.net/show_bug.cgi?id=7124 major
> thomas.petazzoni at free-electrons.com Use BR toolchain externally
> results a non-bootable root filesystem
> ThomasP: you assigned this bug to yourself, have you been able to
> reproduce/analyze this already?

Not yet.

> https://bugs.busybox.net/show_bug.cgi?id=7250 minor
> thomas.petazzoni at free-electrons.com Cannot build with -std=c++11
> ThomasP attached a patch to the bug report, and the submitter
> confirmed it to work. So I guess this patch can be submitted to the
> list now?

The patch I submitted was only for gcc 4.8.x, but I've since then
written patches for gcc 4.7, 4.8 and 4.9, I only lack the same patch
for the ARC special version. I'll work on this, but probably not this
week, since I'm taking care of merging patches this week.

> https://bugs.busybox.net/show_bug.cgi?id=6944 minor
> unassigned at buildroot.uclibc.org building toolchain for sh4 fails
> ThomasP: you discussed this patch with the submitter, but there is no
> final conclusion yet. How to proceed?

I don't know. I don't know SuperH stuff, and it builds a multilib
toolchain by default, causing some issues. Needs investigation/thoughts
to see what could be the solution. Problem is that I don't personally
care much about SuperH, and we don't have a lot of contributors/users
using this architecture, so it reduces quite a bit the incentive to
work on such issues.

> https://bugs.busybox.net/show_bug.cgi?id=4790 normal jacmet at uclibc.org
> Running udhcpc on a system with NFS root kills NFS
> We discussed this patch in the context of the last release cycle. I
> believe the end conclusion is that we shouldn't try to be too smart
> with respect to the init scripts/configuration files and instead
> document the gotchas in the manual. Any takers?

I agree with the solution.

> 6878 minor abrodkin at synopsys.com dmraid: disabled on ARC
> 7088 minor sonic.zhang at analog.com elfutils on Blackfin doesn't build
> 6872 minor unassigned at buildroot.uclibc.org gpsd: disabled on microblaze

These ones are mainly here to remind the respective architecture
maintainers that they should do something about these packages: we have
temporarily solve the situation by excluding those packages using
"depends on !<problematic architecture>", but ultimately there's no
technical reason for those packages to be disabled on those
architectures. So to not forget, I submitted those bug reports instead.
Here the intent is to distinguish packages that for some technical
reason do not support a given architecture (such as webkit, or jamvm,
that really do have some architecture-specific code) from packages
currently broken on a given architecture, but which could potentially
work.

That being said, while I'm pretty sure the dmraid issue on ARC will be
solved at some point, I have less hopes for the elfutils on Blackfin
and gpsd on Microblaze issues, since we don't receive much help to
maintain those two architectures in Buildroot...

> 7136 normal thomas.petazzoni at free-electrons.com ecryptfs-utils needs
> gettext to run when glibc/eglibc is used

Patches already sent. People were a little bit worried about the
consequences of the patches, but I don't think there's any other
solution, so I'd appreciate some review on the patches.

> 7142 normal thomas.petazzoni at free-electrons.com ecryptfs needs getent to run

Yeah, I remember this issue, it was debugged on IRC, and the bug report
is a reminder to do some work to fix it properly.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-07-16  7:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 18:50 [Buildroot] Open bug overview: help wanted! Thomas De Schampheleire
2014-07-12 20:12 ` Gustavo Zacarias
2014-07-16 17:08   ` Thomas De Schampheleire
2014-07-16 17:18     ` Gustavo Zacarias
2014-07-16 18:33       ` Thomas De Schampheleire
2014-07-12 21:53 ` Yann E. MORIN
2014-07-13  1:54   ` Mike Zick
2014-07-13  9:05     ` Yann E. MORIN
2014-07-13 13:29       ` Mike Zick
2014-07-13 14:56         ` Yann E. MORIN
2014-07-16 18:32   ` Thomas De Schampheleire
2014-07-15 19:27 ` Károly Kasza
2014-07-15 20:12   ` Thomas Petazzoni
2014-07-19  9:58     ` Károly Kasza
2014-07-16 15:00   ` Johan Oudinet
2014-07-16  7:31 ` Thomas Petazzoni [this message]
2014-07-16 18:35   ` Thomas De Schampheleire

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=20140716093105.79a705aa@free-electrons.com \
    --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.