[Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented

[Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented

[Karl Krach]

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

[Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented

[Will Newton]

On Mon, Mar 9, 2009 at 5:18 PM, Karl Krach <mailinglists@bluespirit.la> wrote:
>
> 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?

It looks as if the kernel headers you built uClibc with do not match
your kernel.

[Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented

[Karl Krach]

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

[Buildroot] socket(PF_FILE, SOCK_STREAM, 0) not implemented

[Peter Korsgaard]

>>>>> "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