> Sorry, nope. For me that has always worked fine, Cygwin has never mistaken me
> to be superuser if I use my normally powered Windows account.
>
> What does your /etc/passwd and /etc/group files look like?
My entry in /etc/passwd is:
Martin:unused_by_nt/2000/xp:1004:513:U-ATOMISER\Martin,S-1-5-
>>> I was going to patch it to do a 'tar --same-owner' instead,
>> Hmm, you mean --no-same-owner?
> Same thing, no?
No. If you are (or Cygwin *thinks* you are) root (have uid=0), tar will chown
files after extraction unless you specified --no-same-owner. If you aren't
root, tar will chown if y
I was going to patch it to do a 'tar --same-owner' instead,
Hmm, you mean --no-same-owner?
Same thing, no?
This is mostly a guess, but are you running the build as Administrator
(you shouldn't), or does Cygwin for some other reason (broken Cygwin
/etc/passwd file?) think you are root (in
On Mon, 2010-10-25 at 09:09 -0600, Tor Lillqvist wrote:
> This is mostly a guess, but are you running the build as Administrator (you
> shouldn't)
If this is the problem - we should probably detect in configure and
fail early, if we don't already ;-)
Regards,
Mi
> I was going to patch it to do a 'tar --same-owner' instead,
Hmm, you mean --no-same-owner?
> but since
> I'm not the first person to hit this, was wondering what the official
> work-around is?
This is mostly a guess, but are you running the build as Administrator (you
shouldn't), or does Cygw
I saw someone posted about this before, but didn't see the response -
I was going to patch it to do a 'tar --same-owner' instead, but since
I'm not the first person to hit this, was wondering what the official
work-around is?
Thanks,
Martin
Copying Microsoft VC9.0 CRT Merge Modules
Looking for /
