From: Alex Riesen <raa.lkml@gmail.com>
To: Christopher Faylor <me@cgf.cx>
Cc: git@vger.kernel.org
Subject: Re: cygwin-latest: compile errors related to sockaddr_storage, dirent->d_type and dirent->d_ino
Date: Thu, 19 Jan 2006 11:42:46 +0100 [thread overview]
Message-ID: <81b0412b0601190242m4792e73bg181172e478b6e0c2@mail.gmail.com> (raw)
In-Reply-To: <20060119052914.GC8121@trixie.casa.cgf.cx>
On 1/19/06, Christopher Faylor <me@cgf.cx> wrote:
> "They" probably don't like it when people treat an open source project as
> if it was some unresponsive proprietary enterprise which does not listen
> to or accept patches.
Please, accept my appologies for the sarcasm in the original post.
Sometimes I get an impression of cygwin being not maintained at
all, and that, if not justifies my behavior, but at least is an attempt
to explain it.
> >And on top of that, they removed dirent->d_ino (or probably replaced it
> >by __ino32, if at all). BTW, can we somehow avoid using d_ino? It is
> >referenced only in fsck-objects.c Anyway, to workaround this I put
> >
> >COMPAT_CFLAGS += -Dd_ino=__ino32
> >
> >It helps, but surely is not the solution.
>
> I don't see how it could help since __ino32 is not actually filled in
> with anything. In fact, I'll rename the field to __invalid_ino32 to
> make that clear.
But why keep the DT_-macros?! And why there is two fields
hinting at d_ino, and why there is 3 (!) "struct dirent"
definitions in dirent.h (sys/dirent.h)?
Some with different names (d_reserved?).
And if cygwin is aiming for posix, what would d_fd or d_version
be (Open Group Specs v6[1] mention only d_ino and d_name)?
[1] http://www.opengroup.org/onlinepubs/009695399/basedefs/dirent.h.html
next prev parent reply other threads:[~2006-01-19 10:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 13:47 cygwin-latest: compile errors related to sockaddr_storage, dirent->d_type and dirent->d_ino Alex Riesen
2006-01-19 5:29 ` Christopher Faylor
2006-01-19 8:59 ` Junio C Hamano
2006-01-19 16:10 ` Christopher Faylor
2006-01-19 20:34 ` Christopher Faylor
2006-01-19 21:16 ` Linus Torvalds
2006-01-19 21:28 ` Christopher Faylor
2006-01-19 21:44 ` Linus Torvalds
2006-01-19 21:51 ` Christopher Faylor
2006-01-20 1:13 ` [PATCH] fsck-objects: support platforms without d_ino in struct dirent Junio C Hamano
2006-01-20 3:38 ` Christopher Faylor
2006-01-19 10:42 ` Alex Riesen [this message]
2006-01-19 18:31 ` cygwin-latest: compile errors related to sockaddr_storage, dirent->d_type and dirent->d_ino Christopher Faylor
2006-01-19 22:08 ` Alex Riesen
2006-01-19 22:51 ` Christopher Faylor
2006-01-19 12:51 ` Petr Baudis
2006-01-19 15:04 ` Alex Riesen
2006-01-19 13:00 ` Petr Baudis
2006-01-19 15:07 ` Alex Riesen
2006-01-20 1:13 ` Junio C Hamano
2006-01-20 13:23 ` Alex Riesen
2006-01-20 1:13 ` [PATCH] DT_UNKNOWN: do not fully trust existence of DT_UNKNOWN Junio C Hamano
2006-01-20 15:01 ` Alex Riesen
2006-01-20 19:10 ` Junio C Hamano
2006-01-20 21:53 ` Alex Riesen
2006-01-21 8:09 ` Junio C Hamano
2006-01-23 13:07 ` Alex Riesen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0601190242m4792e73bg181172e478b6e0c2@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@cgf.cx \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).