Re: [Xen-users] might XenSpecificGlibc help me?

[Chris Fanning <christopher.fanning@xxxxxxxxx>]

ok. I edited /usr/local/incluse/fuse/fuse_common.h
and added
#define _FILE_OFFSET_BITS 64

now it makes ok. no warnings.
I'll have a look about to see if this has any nasty secondary effects.

thanks all.
Chris.

On 2/14/06, Petersson, Mats <Mats.Petersson@xxxxxxx> wrote:
>
>
> > -----Original Message-----
> > From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> > Chris Fanning
> > Sent: 14 February 2006 15:19
> > To: Anthony Liguori
> > Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-users] might XenSpecificGlibc help me?
> >
> > > (have you installed the fuse development package?).
> > I installed it from source
> >
> > > > checking fuse.h usability... no
> > > > checking fuse.h presence... no
> > > > checking for fuse.h... no
> > > I think this is a pretty clear indication that fuse.h is not present
> >
> > It does seem that fuse.h and family are found.
> > compile.log says:
> > > > /usr/local/include/fuse/fuse_common.h:30:2: error: #error
> > Please add
> > > > -D_FILE_OFFSET_BITS=64 to your compile flags!
> >
> > and /usr/local/include/fuse/fue_common.h incluse this code.
> >
> > /* This interface uses 64 bit off_t */
> > #if _FILE_OFFSET_BITS != 64
> > #error Please add -D_FILE_OFFSET_BITS=64 to your compile flags!
> > #endif
> >
> > what does that mean?
>
> It means just what it says: _FILE_OFFSET_BITS=64 should be the value set
> in the build environment. For some reason, it appears that it's not [or
> the compiler is utterly broken - but that's unlikely]. Adding it as you
> suggested originaly may well help - or it may not. I don't know enough
> about the fuse project to say for sure - but it's almost certainly not
> to do with which version of glibc that you're using.
>
> And I would examine why it says there's no fuse.h in the configuration
> output - if you say that you've installed the fuse devel package, fuse.h
> should be found. Try something like "find / -name fuse.h -print" and see
> if it lists it - if not, you're missing something important, I would
> think.
>
> --
> Mats
> >
> > Chris.
> >
> >
> > On 2/14/06, Anthony Liguori <aliguori@xxxxxxxxxx> wrote:
> > > Chris Fanning wrote:
> > > > Hi,
> > > >
> > > > I'm trying to compile a fs -LTSPFS- that is based on the
> > FUSE project.
> > > >
> > > > I have compiled and installed FUSE on dom0.
> > > > the fuse/examples/hello test works.
> > > >
> > > > Now, when I attempt to compile LTSPFS ltspfs# ./configure
> > checking
> > > > fuse.h usability... no checking fuse.h presence... no
> > checking for
> > > > fuse.h... no
> > > >
> > > I think this is a pretty clear indication that fuse.h is
> > not present
> > > (have you installed the fuse development package?).
> > >
> > > Moreover, depending on which version of Xen you're using,
> > fuse is more
> > > than likely not present and not a compile option in the kernel.
> > > You'll need to compile fuse against Xen.
> > >
> > > FWIW, I've done this before it Ubuntu so you shouldn't have any
> > > problems with it in Debian.
> > >
> > > Regards,
> > >
> > > Anthony Liguori
> > > > and config.log says
> > > > configure:3827: checking fuse.h usability
> > > > configure:3839: gcc -c -g -O2  conftest.c >&5 In file
> > included from
> > > > /usr/local/include/fuse/fuse.h:23,
> > > >                 from /usr/local/include/fuse.h:9,
> > > >                 from conftest.c:65:
> > > > /usr/local/include/fuse/fuse_common.h:30:2: error: #error
> > Please add
> > > > -D_FILE_OFFSET_BITS=64 to your compile flags!
> > > >
> > > > so I thought
> > > > /configure CFLAGS=-D_FILE_OFFSET_BITS=64
> > > >
> > > > but the author of the ltspfs says that -D_FILE_OFFSET_BITS=64 is
> > > > already done in the config script.
> > > >
> > > > I'm at a loss. :(
> > > >
> > > > Might XenSpecificGlibc help me here?
> > > >
> > > Nope.  The Xen glibc is only for performance with TLS emulation.
> > > > and if so,
> > > >
> > > > Any instructions to install it on a debain testing?
> > > >
> > > > Thanks in advance.
> > > > Chris.
> > > >
> > > > _______________________________________________
> > > > Xen-users mailing list
> > > > Xen-users@xxxxxxxxxxxxxxxxxxx
> > > > http://lists.xensource.com/xen-users
> > > >
> > > >
> > >
> > >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> >
>
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users