[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: linking problem in fatfs
From: |
Thomas Schwinge |
Subject: |
Re: linking problem in fatfs |
Date: |
Sat, 31 Mar 2007 22:54:49 +0200 |
User-agent: |
Mutt/1.5.11 |
Hello!
On Sat, Mar 31, 2007 at 01:03:23PM -0700, Roland McGrath wrote:
> That only happens because something else causes node-create.o to be linked in.
> If you are overriding it, you must supply all the symbols it does.
Okay, the problem was the following one: the Debian GNU/Hurd people have
a patch included that goes like this:
#v+
--- hurd/libdiskfs/node-create.c.orig 2006-01-20 01:45:49.000000000 +0100
+++ hurd/libdiskfs/node-create.c 2006-01-20 01:46:42.000000000 +0100
@@ -20,7 +20,7 @@
/* This enables SysV style group behaviour. New nodes inherit the GID
of the user creating them unless the SGID bit is set of the parent
directory. */
-int _diskfs_no_inherit_dir_group;
+int _diskfs_no_inherit_dir_group = 1;
#v-
... moving that symbol from common storage into the data section. This
modifiction, however, was not applied to the fatfs's
`_diskfs_no_inherit_dir_group' symbol, so that one was to be ``treated as
undefined reference[s]'' according to the linker semantics, leading to
what you described above, leading to my original report. I'll find a
better way, to get that Debian patch replaced.
Regards,
Thomas
signature.asc
Description: Digital signature