All of 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: Mon, 09 Mar 2009 18:18:51 +0100	[thread overview]
Message-ID: <kg91ff.12vtc6@webmail.variomedia.de> (raw)


Hello,

I have a handheld device with kernel 2.4.19 and am working with qt 3.3, gcc
version 2.95 and glibc.

For evaluation purposes I try to get the latest Qt version (4.5.0) running. So
i need the uClibc 0.9.29 or greater and the gcc with at least version 4.0.1.

I have downloaded the latest buildroot sources from svn (gcc 4.3.3, uClibc
0.9.30), compiled qt and created a chroot on my board. I ve also mounted /proc
and /dev. But when using sockets (e.g. for qt's QWS), I get the error
"Function not implemented":

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

With my old environment (gcc 2.95 and glibc) the same test code is working
without problems.

When checking the uClibc code, I got stuck at a _syscall2. Do I have
incompatibilities between the uClibc and my kernel? Is my chroot not right
configured?

Thank a lot,

Charly

             reply	other threads:[~2009-03-09 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 17:18 Karl Krach [this message]
2009-03-09 17:36 ` [Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented Will Newton
  -- strict thread matches above, loose matches on Subject: below --
2009-03-10  6:43 Karl Krach
2009-03-10  6:59 ` Peter Korsgaard

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=kg91ff.12vtc6@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 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.