Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <45BA125AAE48D311B03D00508B0CA96AA3D78D@itsmail.tutsys.com> From: Stephen Iribarne To: cygwin AT sourceware DOT cygnus DOT com Subject: RE: symlink created on Samba (Final Resolution) Date: Fri, 16 Jun 2000 09:21:07 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BFD7AE.E03B74DC" ------_=_NextPart_001_01BFD7AE.E03B74DC Content-Type: text/plain Hey, > Unless Metware is using cygwin > they will not, and shouldn't be expected to, understand symlinks I can wish can't I? The goal for me is to get NT users at Tut using my unix makefiles so I don't have to deal with their damn makefiles not working correctly. Long discussion about Jr. Engineers and Sr. Engineers of companies we've purchased being stuck in their ways. So I just want to force everyone to use the cygwin tools and I'm done. No more problems. :) And if anyone wants a job in sunny Northern California let me know! :) I know I know.. I'm not posting for job recruits! -stv /* Steve Iribarne Tut Systems, Inc. http://www.tutsys.com */ > -----Original Message----- > From: Chris Faylor [SMTP:cgf AT cygnus DOT com] > Sent: Friday, June 16, 2000 9:03 AM > To: 'cygwin' > Subject: Re: symlink created on Samba (Final Resolution) > > On Fri, Jun 16, 2000 at 08:41:13AM -0700, Stephen Iribarne wrote: > >Ok.. After further digging here's what I find. > > > >So symlinks work. I ran cat on the file and found that it was working > >perfectly. Thanks to everyone for the posts. > >However, when Metawares hcppc runs it doesn't deal with the symlink > >created! DUH! > > > >So.. I just wanted to let everyone else know what I found. I was > thinking > >that Make was the problem but it wasn't. > > > >I will send something to Metaware to see if they will fix this (yeah > right!, > >won't hold my breath for that one.) In the meantime, it's delete and copy > >for me. > > I wouldn't expect Metaware to fix a problem with Cygwin symlinks. Cygwin > symlinks are entirely a cygwin invention. > > cgf > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com ------_=_NextPart_001_01BFD7AE.E03B74DC Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: symlink created on Samba (Final Resolution)

Hey,

 > = Unless Metware is using cygwin
 > they will not, and = shouldn't be expected to, understand symlinks

I can wish can't = I?  The goal for me is to get NT users at Tut using my unix = makefiles so I don't have to deal with their damn makefiles not working = correctly.  Long discussion about Jr. Engineers and Sr. Engineers = of companies we've purchased being stuck in their ways.  So I just = want to force everyone to use the cygwin tools and I'm done.  No = more problems.  :)  And if anyone wants a job in sunny = Northern California let me know!  :)  I know I know.. I'm not = posting for job recruits!

-stv

/*
Steve = Iribarne          &nbs= p;           &nbs= p;           &nbs= p;         
Tut Systems, Inc.
http://www.tutsys.com
*/

    -----Original Message-----
    From:   Chris Faylor [SMTP:cgf AT cygnus DOT com]
    Sent:   Friday, June 16, 2000 9:03 AM
    To:     'cygwin'
    Subject:       = Re: symlink created on Samba (Final = Resolution)

    On Fri, Jun 16, 2000 at 08:41:13AM = -0700, Stephen Iribarne wrote:
    >Ok.. After further digging here's = what I find.
    >
    >So symlinks work.  I ran cat = on the file and found that it was working
    >perfectly.  Thanks to = everyone for the posts.
    >However, when  Metawares = hcppc runs it doesn't deal with the symlink
    >created!  DUH! 
    >
    >So.. I just wanted to let = everyone else know what I found.  I was thinking
    >that Make was the problem but it = wasn't.
    >
    >I will send something to Metaware = to see if they will fix this (yeah right!,
    >won't hold my breath for that = one.) In the meantime, it's delete and copy
    >for me.

    I wouldn't expect Metaware to fix a = problem with Cygwin symlinks.  Cygwin
    symlinks are entirely a cygwin = invention. 

    cgf

    --
    Want to unsubscribe from this = list?
    Send a message to = cygwin-unsubscribe AT sourceware DOT cygnus DOT com

------_=_NextPart_001_01BFD7AE.E03B74DC--