hi,
[cc'ing this to a wider audience in case it bites anyone else]
On Jul 18, 4:27am, Thomas Duffy wrote:
> Subject: Re: xfs cmd spec/tarball
> After installing the devel package, I tried to build and got the following
> error:
>
> gcc -DXFS_BIG_FILES=1 -DXFS_BIG_FILESYSTEMS=1 -D_KMEMUSER -DSTATIC=static
> -DSIM -I../sim/src -I.. -I../../../linux/include -I../../../linux/fs/xfs/
> -I../../../linux/fs/xfs/pseudo-inc -D_KERNEL -funsigned-char -o mkfs_xfs
> nonsim.o xfs_mkfs.o ../sim/src/libsim_linux_rep.a
> ../sim/src/libsim_linux_rep.a(libdisk.o): In function `write_log_footer':
> /build4/tduffy/2.4.0-test1-xfs/cmd/xfs/sim/src/libdisk.c:331: undefined
> reference to `__constant_memcpy'
> /build4/tduffy/2.4.0-test1-xfs/cmd/xfs/sim/src/libdisk.c:331: undefined
> reference to `__memcpy'
> collect2: ld returned 1 exit status
> make[1]: *** [mkfs_xfs] Error 1
> make: *** [default] Error 2
>
> am I doing something wrong here or is the build broken?
>
> -tduffy
...[time passes, head scratching occurs]...
On Jul 19, 9:53am, Thomas Duffy wrote:
> Subject: Re: xfs cmd spec/tarball
> [snip]
> b) log in as me...
>
thanks mate, I've found the problem using your workarea...
[dbear]/build4/tduffy/2.4.0-test1-xfs/linux/include -> ls -l asm
ls: asm: No such file or directory
[dbear]/build4/tduffy/2.4.0-test1-xfs/linux/include ->
It turns out, you need to have done a "make [x|menu|]config"
in the top level linux subdir before compiling the user tools
... this sets up the "asm" symlink in the linux/include directory
for the architecture which you are going to be building for
(you don't actually have to configure XFS on, just have to have
run and exited the make config, which always creates the symlink).
Without this link, the user tools end up using asm headers from
/usr/include/asm/xxx.h rather than from linux/include/asm/xxx.h,
and strange things start to happen.
Needless to say, I'll be adding a check for this in the user
tool build process shortly... =)
cheers.
--
Nathan
|