From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] trouble with FUSE (Filesystem in Userspace)
Date: Sun, 24 May 2009 22:47:22 +0200 [thread overview]
Message-ID: <871vqefcth.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1240326220.8272.4.camel@sven> (Sven Neumann's message of "Tue\, 21 Apr 2009 17\:03\:40 +0200")
>>>>> "Sven" == Sven Neumann <s.neumann@phase-zero.de> writes:
Sven> Hi,
Sven> we are using buildroot on an ARM platform with uCLibC 0.9.30.1
Sven> and Linux 2.6.30rc2 and can't get FUSE to work. I tried the
Sven> simple hello.c example from the fuse-2.7.3 sources and
Sven> everything seems to work fine until I try to read from the
Sven> filesystem. This read blocks forever. Now I wonder if anyone on
Sven> this list has ever got FUSE and uCLibC to work on an ARM or if
Sven> there are known problems with this combination? Any help would
Sven> be much appreciated as I am running out of ideas here...
Not on ARM, but I'm using it on PPC without any problems.
Are you using EABI or OABI?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-05-24 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 15:03 [Buildroot] trouble with FUSE (Filesystem in Userspace) Sven Neumann
2009-05-24 20:47 ` Peter Korsgaard [this message]
2009-05-24 21:53 ` Sven Neumann
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=871vqefcth.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 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.