On Tuesday 22 August 2006 22:30 Julien TOUCHE wrote:
> one step more.
>
> why there is so much path in -idirafter ... ?
> would it be better to have configure options to set lib/include path ?
I use -idirafter instead of -I to let gcc know that I don't want these include
files listed as dependencies.
You are right, using autoconf/configure would probably be better, but I don't
really know autoconf ... what I have is pasted together from examples.
Can you help?
> est_ops.c: In function `ops__string_to_dev':
> est_ops.c:81: error: `__S_IFLNK' undeclared (first use in this function)
> est_ops.c:81: error: (Each undeclared identifier is reported only once
> est_ops.c:81: error: for each function it appears in.)
> est_ops.c:95: error: `__S_IFCHR' undeclared (first use in this function)
> est_ops.c:95: error: `__S_IFBLK' undeclared (first use in this function)
> est_ops.c:99: error: `__S_IFMT' undeclared (first use in this function)
I use these macros to get a correct unix-mode for devices and symlinks. If I
get "symlink /path/to/target" from the repository and svn:special-file is
set, I try to "fake" a correct unix-mode internally.
And as for __S_IFMT:
#define __S_IFMT 0170000 /* These bits determine file type. */
I use that to mask the needed bits.
Is there something like this on BSD? If not, I'll have to do that some other
way.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
