public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com>
To: "Gary V. Vaughan" <gvaughan@oranda.demon.co.uk>
Cc: <automake@gnu.org>, "Sebastien Barre" <Sebastien.Barre@utc.fr>,
	"cygwin" <cygwin@sourceware.cygnus.com>
Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?
Date: Sun, 28 Feb 1999 23:02:00 -0000	[thread overview]
Message-ID: <009801be5f2e$6dc82480$29acdfd0@InspirePharm.Com> (raw)
Message-ID: <19990228230200.vFrGYdJXODAzastrYzjvKFsVnXEwKBupg4APFVQm8zo@z> (raw)

>>
>> If I remember correctly; Geoffrey Noer mentioned last month, that it
was
>> a Cgywin issue not automake.  Perhaps the problem will be fixed in
the
>> next release of Cygwin.
>>
>> Suhaib
>
>Yes,  the root of the problem is that 'gcc --print-prog-path=ld' gives
a
>win32 path (under cygwin), and I think it is this that the cygwin folks
>plan to fix.
>


Yes, you are correct.  That is what Geof also mentioned. For now
hard-coding the ld path
in configure scripts work.

Suhaib

>Cheers,
> Gary.
>


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


             reply	other threads:[~1999-02-28 23:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-23  5:01 Suhaib M. Siddiqi [this message]
1999-02-28 23:02 ` Suhaib M. Siddiqi
  -- strict thread matches above, loose matches on Subject: below --
1999-02-26  2:32 Bernard Dautrevaux
1999-02-26  3:51 ` Gary V. Vaughan
1999-02-28 23:02   ` Gary V. Vaughan
1999-02-28 23:02 ` Bernard Dautrevaux
1999-02-23  4:11 Suhaib M. Siddiqi
1999-02-23  4:56 ` Gary V. Vaughan
     [not found]   ` < 36D2A59D.603BF54E@oranda.demon.co.uk >
1999-02-23  8:39     ` Mumit Khan
1999-02-23  8:54       ` Gary V. Vaughan
     [not found]         ` < 36D2DCFF.54E5B41F@oranda.demon.co.uk >
1999-02-25 23:04           ` Geoffrey Noer
1999-02-28 23:02             ` Geoffrey Noer
1999-02-28 23:02         ` Gary V. Vaughan
     [not found]       ` < 199902231639.KAA04761@modi.xraylith.wisc.edu >
1999-02-23  9:13         ` DJ Delorie
     [not found]           ` < 199902231713.MAA11397@envy.delorie.com >
1999-02-23 14:16             ` Mumit Khan
1999-02-28 23:02               ` Mumit Khan
1999-02-28 23:02           ` DJ Delorie
1999-02-28 23:02       ` Mumit Khan
1999-02-28 23:02   ` Gary V. Vaughan
1999-02-28 23:02 ` Suhaib M. Siddiqi
     [not found] <Bob>
     [not found] ` <Friesenhahn's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Mon,>
     [not found]         ` <22>
     [not found]           ` <Feb>
     [not found]             ` <1999>
     [not found]               ` <21:28:12>
     [not found]                 ` <-0600>
     [not found]                   ` <(CST)>
     [not found]                     ` <Pine.SO4.4.05.9902222125010.25431-100000@scooby.simple.dallas.tx.us>
     [not found]                       ` <d9btilixqo.fsf@han.cs.umn.edu>
1999-02-22 22:41                         ` Sebastien Barre
1999-02-23  3:06                           ` Gary V. Vaughan
1999-02-28 23:02                             ` Gary V. Vaughan
1999-02-28 23:02                           ` Sebastien Barre

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='009801be5f2e$6dc82480$29acdfd0@InspirePharm.Com' \
    --to=ssiddiqi@inspirepharm.com \
    --cc=Sebastien.Barre@utc.fr \
    --cc=automake@gnu.org \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=gvaughan@oranda.demon.co.uk \
    /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.
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).