From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] to use DISABLE_IPV6 instead of fix seting
Date: Wed, 2 Jan 2008 14:51:05 +0200 (EET) [thread overview]
Message-ID: <56806.127.0.0.1.1199278265.squirrel@localhost> (raw)
In-Reply-To: <477A4461.70205@arcormail.de>
Hi Claus,
> while working on a new rootfile system with ipv6 support, I had problems
> with some packages.
> By the way there was an too error in the libxml2 makefile when
> installing the target-header.
>
> Is it documented how makefiles should be written to be flexible for
> differrent toolchain options like:
>
> libintl,
> largefile,
> ipv6,
Seems very few of packages honor these toolchain options. As I know, for example, Mplayer requires
largefile support. Many people are using only single toolchain and not testing with other toolchain options.
Thanks for patch - will apply soon.
regards,
Ivan
prev parent reply other threads:[~2008-01-02 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 13:47 [Buildroot] [patch] to use DISABLE_IPV6 instead of fix seting Claus Klein
2008-01-02 12:51 ` Ivan Kuten [this message]
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=56806.127.0.0.1.1199278265.squirrel@localhost \
--to=ivan.kuten@promwad.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