From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented
Date: Tue, 10 Mar 2009 07:59:27 +0100 [thread overview]
Message-ID: <87y6vdamnk.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <kga2o8.4opixu@webmail.variomedia.de> (Karl Krach's message of "Tue\, 10 Mar 2009 07\:43\:20 +0100")
>>>>> "Karl" == Karl Krach <mailinglists@blueSpirit.la> writes:
Hi,
Karl> Yes, of course - you re right. I'm using the kernel headers which are
Karl> downloaded and installed by buildroot (2.5.28.x). Provides the buildroot
Karl> configuration a way to used custom kernel headers? What do you think, is there
Karl> a chance to get it working with a 2.4 kernel?
I've recently removed 2.4.31 kernel headers, but you could try
checking out r25435, then you should be able to select it after you
enable build options->Show package that are deprecated.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-03-10 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 6:43 [Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented Karl Krach
2009-03-10 6:59 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-09 17:18 Karl Krach
2009-03-09 17:36 ` Will Newton
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=87y6vdamnk.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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