Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] wide-dhcpv6 crash when built in buildroot version 2014.05 using a cross toolchain arm-buildroot-linux-gnueabihf with gcc version 4.8.3
Date: Tue, 14 Apr 2015 15:54:16 -0300	[thread overview]
Message-ID: <552D6258.708@zacarias.com.ar> (raw)
In-Reply-To: <620A1A0EF5A8FD49AAB6076B610B85DD45C34E42@LTX-EXCH03.int.lantronix.com>

On 04/14/2015 03:25 PM, Srinivasan R wrote:

> Hi All,
> I am using the latest version of buildroot (2014.05) for my project, I happen to port the wide-dhcpv6 package which I had in the previous version(buildroot-2010.05) to the current buildroot version(2014.05).

Hi.
Well, the package hasn't been ported to any modern package format, so
debugging an old (very old) package just thrown into a new buildroot
version is generally a no-go since the old style hasn't been accepted or
used for a long time.
Otherwise there are many things that could go wrong.
Also you don't specify the precise target or a defconfig to check.
I suggest you convert the package to a generic one (look at the manual),
try again and see if it still fails.
Alternatively if you're in such a rush you could use dibbler which is a
far more modern/maintained DHCPv6 client/server/relay.
Regards.

  reply	other threads:[~2015-04-14 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 18:25 [Buildroot] wide-dhcpv6 crash when built in buildroot version 2014.05 using a cross toolchain arm-buildroot-linux-gnueabihf with gcc version 4.8.3 Srinivasan R
2015-04-14 18:54 ` Gustavo Zacarias [this message]
     [not found] <620A1A0EF5A8FD49AAB6076B610B85DD45C35001@LTX-EXCH03.int.lantronix.com>
2015-04-15 12:23 ` Gustavo Zacarias

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=552D6258.708@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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