Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Krach <mailinglists@blueSpirit.la>
To: buildroot@busybox.net
Subject: [Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented
Date: Tue, 10 Mar 2009 07:43:20 +0100	[thread overview]
Message-ID: <kga2o8.4opixu@webmail.variomedia.de> (raw)

Will Newton <will.newton@gmail.com> schrieb:
> >
> > Hello,
> >
> > I have an arm handheld device with kernel 2.4.19 and am working
> > with qt 3.3, gcc version 2.95 and glibc.
> >
> > [...]
> >
> > brk(0x137f4) ? ? ? ? ? ? ? ? ? ?= 0x137f4
> > brk(0x14000) ? ? ? ? ? ? ? ? ? ?= 0x14000
> > socket(PF_FILE, SOCK_STREAM, 0) = -1 ENOSYS
> >                                  (Function not implemented)
> > stat64("/root/Settings/Trolltech.conf", 0xbffff2d8) = -1 ENOENT
> >
> > [...]
> >
> 
> It looks as if the kernel headers you built uClibc with do not match
> your kernel.
> 
Yes, of course - you re right. I'm using the kernel headers which are
downloaded and installed by buildroot (2.5.28.x). Provides the buildroot
configuration a way to used custom kernel headers? What do you think, is there
a chance to get it working with a 2.4 kernel?

Now I'm going to fix it manually (by replacing the kernel header files in
"toolchain_build_arm/linux") and will report how far I get.

Charly

             reply	other threads:[~2009-03-10  6:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  6:43 Karl Krach [this message]
2009-03-10  6:59 ` [Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented Peter Korsgaard
  -- 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=kga2o8.4opixu@webmail.variomedia.de \
    --to=mailinglists@bluespirit.la \
    --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