Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Suhaib M. Siddiqi]

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


----- Original Message -----
From: Sebastien Barre <Sebastien.Barre@utc.fr>
To: <automake@gnu.org>
Cc: <cygwin@sourceware.cygnus.com>
Sent: Tuesday, February 23, 1999 1:41 AM
Subject: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?


>Here are some excerpts of a problem discussed in the cywin32 mailing
list.
>I thought it might be interesting for the automake people too (this
message
>is also crossposted CC: to the cywin32 list for information).
>
> http://www.cygnus.com/ml/gnu-win32/
> http://sourceware.cygnus.com/ml/cygwin/1999-02/msg00702.html
>
>It seems related to the way configure script handles path (many of use
>encoutered the pb with different configure scripts) :
>
> Alex <alexl@i-france.com> :
>
>>i tried to compile CILK ( http://supertech.lcs.mit.edu/cilk/ )
>>and i got this error message:
>>
>>checking for ld used by GCC... no
>>configure: error: no acceptable ld found in $PATH
>>
>>though ld.exe is in the bin directory, what can i do to solve this
>>problem ?
>
>
>Tolj <tolj@uni-duesseldorf.de> :
>
>>check out the configure script itself where the test is performed,
i.e.
>>search for "checking for ld used by" and you may see that you'll need
to
>>add Win32 path style to match certain conditions within the configure
>>script so ld is recognized.
>>
>>At least for some configure scripts this has been the problem for not
>>recognizing ld in my experience.
>
>
>Julian Kinraid <jkinraid@clear.net.nz>
>
>>I had the same problem, but if you just set the LD enviroment
variable,
>>you mightn't need to change the configure script -
>>
>>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>>
>>Just make sure the path is correct.
>
>
>"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :
>
>>>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>>>
>>>Just make sure the path is correct.
>>>
>>
>>Theoretically it supposed to work.  But; it does not awlays by doing
>>export... before using configure script.  Many Configure scripts
apprantly
>>ignore it and seach for LD="$..." whatever.  Hardcoding the ld.exe
path in
>>configure works at least always in my hands.
>
>
>"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :
>
>>This problem also occurs with LessTif and many other codes.  It is
because
>>Cygwin has a different style.
>>
>>I usually search the configure script for something like "LD="$...."
and
>>replace all those occurances with
>>LD="/usr/cygwin-b20/H-i586-cywgin32/bin/ld.exe"  This hard codes the
ld.exe
>>path and also include at your ./configure --with-gnu-ld if this option
is
>>available (check with ./configure --help).  Hard coding ld.exe path in
>>configure script always has worked at least in my hands.
>
>
>Any help frop the automake people would be really appreciated, sorry if
it
>has been discussed before...
>
>Thanks a lot
>
>
>______________________________________________________________
>Sebastien Barre                  http://www.hds.utc.fr/~barre/
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>



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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

"Suhaib M. Siddiqi" wrote:
> 
> 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.

Cheers,
	Gary.

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Mumit Khan]

"Gary V. Vaughan" <gvaughan@oranda.demon.co.uk> writes:
> "Suhaib M. Siddiqi" wrote:
> > 
> > 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.

EGCS-1.1.1 (from my site) produce forward slashes, albeit with a drive
specifier. EGCS-1.1.2 will do the same, and the changes are now in the 
dev branch. Does this still pose a problem for libtool (other than the
issue of executable file extensions, which I believe you've fixed
already)?

I've lobbied unsuccessfully to get GCC et al to use POSIX-only pathnames.
The only rationale for using the current scheme is if GCC execs a native 
program, but currently that's not the case and will not be in the near 
foreseeable future.

Regards,
Mumit


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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

Mumit Khan wrote:
> 
> "Gary V. Vaughan" <gvaughan@oranda.demon.co.uk> writes:
> > "Suhaib M. Siddiqi" wrote:
> > >
> > > 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.
> 
> EGCS-1.1.1 (from my site) produce forward slashes, albeit with a drive
> specifier. EGCS-1.1.2 will do the same, and the changes are now in the
> dev branch. Does this still pose a problem for libtool (other than the
> issue of executable file extensions, which I believe you've fixed
> already)?
> 
> I've lobbied unsuccessfully to get GCC et al to use POSIX-only pathnames.
> The only rationale for using the current scheme is if GCC execs a native
> program, but currently that's not the case and will not be in the near
> foreseeable future.
> 
> Regards,
> Mumit

Not a problem as such, just a change.  The current libtool converts to
UNC paths which I understand are no longer supported in winsup
snapshots, so I need to rejig the code a bit more.

The main problem is that libtool is trying to support b18->b20.2, and
the only way to do that with a single mechanism is to convert to
<drive>:/forward/slash/separated/path/to/ld and hope that all the other
tools in the chain (for all supported versions of cygwin) will
understand the <drive>: part of the path.

Cheers,
	Gary.

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[DJ Delorie]

> I've lobbied unsuccessfully to get GCC et al to use POSIX-only pathnames.

No, you were successful.  We submitted a patch to do that a while ago,
and it should have gotten into egcs by now.  Please let me know if it
isn't in the recent egcs snapshots.


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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Mumit Khan]

On Tue, 23 Feb 1999, DJ Delorie wrote:

> No, you were successful.  We submitted a patch to do that a while ago,
> and it should have gotten into egcs by now.  Please let me know if it
> isn't in the recent egcs snapshots.

Only partially. Geoffrey's patch simply turns the directory separator
from '\' to '/', but only after translating the path to win32 native, 
which now looks like 'c:/tmp/foo/bar' etc. Btw, I have a followup to 
the patch, committed to the egcs dev branch, that fixes a small oversight 
in Geoffrey's patch.

Out of the two possible extremes -- win32 only and POSIX only -- this is 
a reasonable compromise, but it does defeat some of my mounting strategies.

We'll still have occasional problems in dealing with configuration tools
that have trouble with ':' in pathnames (I have a few home-grown ones that
do have this problem), and these will get fixed over time.

Regards,
Mumit




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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Geoffrey Noer]

On Tue, Feb 23, 1999, Gary V. Vaughan wrote:
[...]
> Not a problem as such, just a change.  The current libtool converts to
> UNC paths which I understand are no longer supported in winsup
> snapshots, so I need to rejig the code a bit more.

This shouldn't be the case.  //<drive-letter>/ support (which
conflicts with UNC support for machine names of one letter) will be
going away but we definitely intend to continue to support UNC path
names.

If UNC support is broken in current snapshots, please let me know...

-- 
Geoffrey Noer		Email: noer@cygnus.com
Cygnus Solutions

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Mumit Khan]

On Tue, 23 Feb 1999, DJ Delorie wrote:

> No, you were successful.  We submitted a patch to do that a while ago,
> and it should have gotten into egcs by now.  Please let me know if it
> isn't in the recent egcs snapshots.

Only partially. Geoffrey's patch simply turns the directory separator
from '\' to '/', but only after translating the path to win32 native, 
which now looks like 'c:/tmp/foo/bar' etc. Btw, I have a followup to 
the patch, committed to the egcs dev branch, that fixes a small oversight 
in Geoffrey's patch.

Out of the two possible extremes -- win32 only and POSIX only -- this is 
a reasonable compromise, but it does defeat some of my mounting strategies.

We'll still have occasional problems in dealing with configuration tools
that have trouble with ':' in pathnames (I have a few home-grown ones that
do have this problem), and these will get fixed over time.

Regards,
Mumit




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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

Mumit Khan wrote:
> 
> "Gary V. Vaughan" <gvaughan@oranda.demon.co.uk> writes:
> > "Suhaib M. Siddiqi" wrote:
> > >
> > > 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.
> 
> EGCS-1.1.1 (from my site) produce forward slashes, albeit with a drive
> specifier. EGCS-1.1.2 will do the same, and the changes are now in the
> dev branch. Does this still pose a problem for libtool (other than the
> issue of executable file extensions, which I believe you've fixed
> already)?
> 
> I've lobbied unsuccessfully to get GCC et al to use POSIX-only pathnames.
> The only rationale for using the current scheme is if GCC execs a native
> program, but currently that's not the case and will not be in the near
> foreseeable future.
> 
> Regards,
> Mumit

Not a problem as such, just a change.  The current libtool converts to
UNC paths which I understand are no longer supported in winsup
snapshots, so I need to rejig the code a bit more.

The main problem is that libtool is trying to support b18->b20.2, and
the only way to do that with a single mechanism is to convert to
<drive>:/forward/slash/separated/path/to/ld and hope that all the other
tools in the chain (for all supported versions of cygwin) will
understand the <drive>: part of the path.

Cheers,
	Gary.

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

"Suhaib M. Siddiqi" wrote:
> 
> 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.

Cheers,
	Gary.

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Suhaib M. Siddiqi]

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


----- Original Message -----
From: Sebastien Barre <Sebastien.Barre@utc.fr>
To: <automake@gnu.org>
Cc: <cygwin@sourceware.cygnus.com>
Sent: Tuesday, February 23, 1999 1:41 AM
Subject: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?


>Here are some excerpts of a problem discussed in the cywin32 mailing
list.
>I thought it might be interesting for the automake people too (this
message
>is also crossposted CC: to the cywin32 list for information).
>
> http://www.cygnus.com/ml/gnu-win32/
> http://sourceware.cygnus.com/ml/cygwin/1999-02/msg00702.html
>
>It seems related to the way configure script handles path (many of use
>encoutered the pb with different configure scripts) :
>
> Alex <alexl@i-france.com> :
>
>>i tried to compile CILK ( http://supertech.lcs.mit.edu/cilk/ )
>>and i got this error message:
>>
>>checking for ld used by GCC... no
>>configure: error: no acceptable ld found in $PATH
>>
>>though ld.exe is in the bin directory, what can i do to solve this
>>problem ?
>
>
>Tolj <tolj@uni-duesseldorf.de> :
>
>>check out the configure script itself where the test is performed,
i.e.
>>search for "checking for ld used by" and you may see that you'll need
to
>>add Win32 path style to match certain conditions within the configure
>>script so ld is recognized.
>>
>>At least for some configure scripts this has been the problem for not
>>recognizing ld in my experience.
>
>
>Julian Kinraid <jkinraid@clear.net.nz>
>
>>I had the same problem, but if you just set the LD enviroment
variable,
>>you mightn't need to change the configure script -
>>
>>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>>
>>Just make sure the path is correct.
>
>
>"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :
>
>>>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>>>
>>>Just make sure the path is correct.
>>>
>>
>>Theoretically it supposed to work.  But; it does not awlays by doing
>>export... before using configure script.  Many Configure scripts
apprantly
>>ignore it and seach for LD="$..." whatever.  Hardcoding the ld.exe
path in
>>configure works at least always in my hands.
>
>
>"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :
>
>>This problem also occurs with LessTif and many other codes.  It is
because
>>Cygwin has a different style.
>>
>>I usually search the configure script for something like "LD="$...."
and
>>replace all those occurances with
>>LD="/usr/cygwin-b20/H-i586-cywgin32/bin/ld.exe"  This hard codes the
ld.exe
>>path and also include at your ./configure --with-gnu-ld if this option
is
>>available (check with ./configure --help).  Hard coding ld.exe path in
>>configure script always has worked at least in my hands.
>
>
>Any help frop the automake people would be really appreciated, sorry if
it
>has been discussed before...
>
>Thanks a lot
>
>
>______________________________________________________________
>Sebastien Barre                  http://www.hds.utc.fr/~barre/
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>



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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Geoffrey Noer]

On Tue, Feb 23, 1999, Gary V. Vaughan wrote:
[...]
> Not a problem as such, just a change.  The current libtool converts to
> UNC paths which I understand are no longer supported in winsup
> snapshots, so I need to rejig the code a bit more.

This shouldn't be the case.  //<drive-letter>/ support (which
conflicts with UNC support for machine names of one letter) will be
going away but we definitely intend to continue to support UNC path
names.

If UNC support is broken in current snapshots, please let me know...

-- 
Geoffrey Noer		Email: noer@cygnus.com
Cygnus Solutions

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[DJ Delorie]

> I've lobbied unsuccessfully to get GCC et al to use POSIX-only pathnames.

No, you were successful.  We submitted a patch to do that a while ago,
and it should have gotten into egcs by now.  Please let me know if it
isn't in the recent egcs snapshots.


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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Mumit Khan]

"Gary V. Vaughan" <gvaughan@oranda.demon.co.uk> writes:
> "Suhaib M. Siddiqi" wrote:
> > 
> > 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.

EGCS-1.1.1 (from my site) produce forward slashes, albeit with a drive
specifier. EGCS-1.1.2 will do the same, and the changes are now in the 
dev branch. Does this still pose a problem for libtool (other than the
issue of executable file extensions, which I believe you've fixed
already)?

I've lobbied unsuccessfully to get GCC et al to use POSIX-only pathnames.
The only rationale for using the current scheme is if GCC execs a native 
program, but currently that's not the case and will not be in the near 
foreseeable future.

Regards,
Mumit


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

RE: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Bernard Dautrevaux]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]

> -----Original Message-----
> From: Geoffrey Noer [ mailto:noer@cygnus.com ]
> Sent: Friday, February 26, 1999 8:04 AM
> To: Gary V. Vaughan
> Cc: Mumit Khan; cygwin; Libtool List
> Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win
> path ?
> 
> 
> On Tue, Feb 23, 1999, Gary V. Vaughan wrote:
> [...]
> > Not a problem as such, just a change.  The current libtool 
> converts to
> > UNC paths which I understand are no longer supported in winsup
> > snapshots, so I need to rejig the code a bit more.
> 
> This shouldn't be the case.  //<drive-letter>/ support (which
> conflicts with UNC support for machine names of one letter) will be
> going away but we definitely intend to continue to support UNC path
> names.
> 
> If UNC support is broken in current snapshots, please let me know...
> 

Gary, I think you were saying that libtool converts drive:/path to
//drive/path? this is not UNC, but some a bit crazy (because it forbids
one letter machine names, and cause network timeouts if you refer to an
unexisting drive, like //A/ if the floppy is not inserted) cygwin
convention. This convention is now becoming obsolete and is no more
supported in current snapshot, and replaced by /cygdrive/drive/path
(with cygdrive configurable in the registry).

HTH

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingéniérie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Suhaib M. Siddiqi]

>>
>> 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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

I should have cross-posted this to the cygwin list:

	http://egcs.cygnus.com/ml/egcs/1999-02/msg00707.html

Cheers,
	Gary V. Vaughan

Sebastien Barre wrote:
> 
> Here are some excerpts of a problem discussed in the cywin32 mailing list.
> I thought it might be interesting for the automake people too (this message
> is also crossposted CC: to the cywin32 list for information).
> 
> http://www.cygnus.com/ml/gnu-win32/
> http://sourceware.cygnus.com/ml/cygwin/1999-02/msg00702.html
> 
> It seems related to the way configure script handles path (many of use
> encoutered the pb with different configure scripts) :

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

Bernard Dautrevaux <DAUTREVAUX@microprocess.com> writes:

> > -----Original Message-----
> > From: Geoffrey Noer [ mailto:noer@cygnus.com ]
> > Sent: Friday, February 26, 1999 8:04 AM
> > To: Gary V. Vaughan
> > Cc: Mumit Khan; cygwin; Libtool List
> > Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win
> > path ?
> > 
> > 
> > On Tue, Feb 23, 1999, Gary V. Vaughan wrote:
> > [...]
> > > Not a problem as such, just a change.  The current libtool 
> > converts to
> > > UNC paths which I understand are no longer supported in winsup
> > > snapshots, so I need to rejig the code a bit more.
> > 
> > This shouldn't be the case.  //<drive-letter>/ support (which
> > conflicts with UNC support for machine names of one letter) will be
> > going away but we definitely intend to continue to support UNC path
> > names.
> > 
> > If UNC support is broken in current snapshots, please let me know...
> > 
> 
> Gary, I think you were saying that libtool converts drive:/path to
> //drive/path? this is not UNC, but some a bit crazy (because it forbids
> one letter machine names, and cause network timeouts if you refer to an
> unexisting drive, like //A/ if the floppy is not inserted) cygwin
> convention. This convention is now becoming obsolete and is no more
> supported in current snapshot, and replaced by /cygdrive/drive/path
> (with cygdrive configurable in the registry).

Yes, my bad.  Thanks for the clarification.  I plan to use
drive:/path/to/executable before the next libtool release.

Cheers,
	Gary.


-- 
  ___              _   ___   __              _             
 / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___ 
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
 \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
PGP Key from/___/                      /___/               
http://www.cl.cam.ac.uk/PGP/pks-commands.html#extract      
http://pgp.ai.mit.edu/~bal/pks-commands.html#extract       


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

[PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Sebastien Barre]

Here are some excerpts of a problem discussed in the cywin32 mailing list.
I thought it might be interesting for the automake people too (this message
is also crossposted CC: to the cywin32 list for information).

http://www.cygnus.com/ml/gnu-win32/
http://sourceware.cygnus.com/ml/cygwin/1999-02/msg00702.html

It seems related to the way configure script handles path (many of use
encoutered the pb with different configure scripts) :

 Alex <alexl@i-france.com> :

>i tried to compile CILK ( http://supertech.lcs.mit.edu/cilk/ )
>and i got this error message:
>
>checking for ld used by GCC... no
>configure: error: no acceptable ld found in $PATH
>
>though ld.exe is in the bin directory, what can i do to solve this
>problem ?


Tolj <tolj@uni-duesseldorf.de> :

>check out the configure script itself where the test is performed, i.e.
>search for "checking for ld used by" and you may see that you'll need to
>add Win32 path style to match certain conditions within the configure
>script so ld is recognized.
>
>At least for some configure scripts this has been the problem for not
>recognizing ld in my experience.


Julian Kinraid <jkinraid@clear.net.nz>

>I had the same problem, but if you just set the LD enviroment variable,
>you mightn't need to change the configure script -
>
>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>
>Just make sure the path is correct.


"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :

>>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>>
>>Just make sure the path is correct.
>>
>
>Theoretically it supposed to work.  But; it does not awlays by doing
>export... before using configure script.  Many Configure scripts apprantly
>ignore it and seach for LD="$..." whatever.  Hardcoding the ld.exe path in
>configure works at least always in my hands.


"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :

>This problem also occurs with LessTif and many other codes.  It is because
>Cygwin has a different style.
>
>I usually search the configure script for something like "LD="$...." and
>replace all those occurances with
>LD="/usr/cygwin-b20/H-i586-cywgin32/bin/ld.exe"  This hard codes the ld.exe
>path and also include at your ./configure --with-gnu-ld if this option is
>available (check with ./configure --help).  Hard coding ld.exe path in
>configure script always has worked at least in my hands.


Any help frop the automake people would be really appreciated, sorry if it
has been discussed before...

Thanks a lot


______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

Bernard Dautrevaux <DAUTREVAUX@microprocess.com> writes:

> > -----Original Message-----
> > From: Geoffrey Noer [ mailto:noer@cygnus.com ]
> > Sent: Friday, February 26, 1999 8:04 AM
> > To: Gary V. Vaughan
> > Cc: Mumit Khan; cygwin; Libtool List
> > Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win
> > path ?
> > 
> > 
> > On Tue, Feb 23, 1999, Gary V. Vaughan wrote:
> > [...]
> > > Not a problem as such, just a change.  The current libtool 
> > converts to
> > > UNC paths which I understand are no longer supported in winsup
> > > snapshots, so I need to rejig the code a bit more.
> > 
> > This shouldn't be the case.  //<drive-letter>/ support (which
> > conflicts with UNC support for machine names of one letter) will be
> > going away but we definitely intend to continue to support UNC path
> > names.
> > 
> > If UNC support is broken in current snapshots, please let me know...
> > 
> 
> Gary, I think you were saying that libtool converts drive:/path to
> //drive/path? this is not UNC, but some a bit crazy (because it forbids
> one letter machine names, and cause network timeouts if you refer to an
> unexisting drive, like //A/ if the floppy is not inserted) cygwin
> convention. This convention is now becoming obsolete and is no more
> supported in current snapshot, and replaced by /cygdrive/drive/path
> (with cygdrive configurable in the registry).

Yes, my bad.  Thanks for the clarification.  I plan to use
drive:/path/to/executable before the next libtool release.

Cheers,
	Gary.


-- 
  ___              _   ___   __              _             
 / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___ 
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
 \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
PGP Key from/___/                      /___/               
http://www.cl.cam.ac.uk/PGP/pks-commands.html#extract      
http://pgp.ai.mit.edu/~bal/pks-commands.html#extract       


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

RE: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Bernard Dautrevaux]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

> -----Original Message-----
> From: Geoffrey Noer [ mailto:noer@cygnus.com ]
> Sent: Friday, February 26, 1999 8:04 AM
> To: Gary V. Vaughan
> Cc: Mumit Khan; cygwin; Libtool List
> Subject: Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win
> path ?
> 
> 
> On Tue, Feb 23, 1999, Gary V. Vaughan wrote:
> [...]
> > Not a problem as such, just a change.  The current libtool 
> converts to
> > UNC paths which I understand are no longer supported in winsup
> > snapshots, so I need to rejig the code a bit more.
> 
> This shouldn't be the case.  //<drive-letter>/ support (which
> conflicts with UNC support for machine names of one letter) will be
> going away but we definitely intend to continue to support UNC path
> names.
> 
> If UNC support is broken in current snapshots, please let me know...
> 

Gary, I think you were saying that libtool converts drive:/path to
//drive/path? this is not UNC, but some a bit crazy (because it forbids
one letter machine names, and cause network timeouts if you refer to an
unexisting drive, like //A/ if the floppy is not inserted) cygwin
convention. This convention is now becoming obsolete and is no more
supported in current snapshot, and replaced by /cygdrive/drive/path
(with cygdrive configurable in the registry).

HTH

	Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingéniérie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Suhaib M. Siddiqi]

>>
>> 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

Re: [PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Gary V. Vaughan]

I should have cross-posted this to the cygwin list:

	http://egcs.cygnus.com/ml/egcs/1999-02/msg00707.html

Cheers,
	Gary V. Vaughan

Sebastien Barre wrote:
> 
> Here are some excerpts of a problem discussed in the cywin32 mailing list.
> I thought it might be interesting for the automake people too (this message
> is also crossposted CC: to the cywin32 list for information).
> 
> http://www.cygnus.com/ml/gnu-win32/
> http://sourceware.cygnus.com/ml/cygwin/1999-02/msg00702.html
> 
> It seems related to the way configure script handles path (many of use
> encoutered the pb with different configure scripts) :

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

[PB] "no acceptable ld" : cywin32 pb, way to handle win path ?

[Sebastien Barre]

Here are some excerpts of a problem discussed in the cywin32 mailing list.
I thought it might be interesting for the automake people too (this message
is also crossposted CC: to the cywin32 list for information).

http://www.cygnus.com/ml/gnu-win32/
http://sourceware.cygnus.com/ml/cygwin/1999-02/msg00702.html

It seems related to the way configure script handles path (many of use
encoutered the pb with different configure scripts) :

 Alex <alexl@i-france.com> :

>i tried to compile CILK ( http://supertech.lcs.mit.edu/cilk/ )
>and i got this error message:
>
>checking for ld used by GCC... no
>configure: error: no acceptable ld found in $PATH
>
>though ld.exe is in the bin directory, what can i do to solve this
>problem ?


Tolj <tolj@uni-duesseldorf.de> :

>check out the configure script itself where the test is performed, i.e.
>search for "checking for ld used by" and you may see that you'll need to
>add Win32 path style to match certain conditions within the configure
>script so ld is recognized.
>
>At least for some configure scripts this has been the problem for not
>recognizing ld in my experience.


Julian Kinraid <jkinraid@clear.net.nz>

>I had the same problem, but if you just set the LD enviroment variable,
>you mightn't need to change the configure script -
>
>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>
>Just make sure the path is correct.


"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :

>>export LD=/cygwin/cygwin-b20/H-i586-cygwin32/bin/ld.exe
>>
>>Just make sure the path is correct.
>>
>
>Theoretically it supposed to work.  But; it does not awlays by doing
>export... before using configure script.  Many Configure scripts apprantly
>ignore it and seach for LD="$..." whatever.  Hardcoding the ld.exe path in
>configure works at least always in my hands.


"Suhaib M. Siddiqi" <Ssiddiqi@InspirePharm.Com> :

>This problem also occurs with LessTif and many other codes.  It is because
>Cygwin has a different style.
>
>I usually search the configure script for something like "LD="$...." and
>replace all those occurances with
>LD="/usr/cygwin-b20/H-i586-cywgin32/bin/ld.exe"  This hard codes the ld.exe
>path and also include at your ./configure --with-gnu-ld if this option is
>available (check with ./configure --help).  Hard coding ld.exe path in
>configure script always has worked at least in my hands.


Any help frop the automake people would be really appreciated, sorry if it
has been discussed before...

Thanks a lot


______________________________________________________________
Sebastien Barre                  http://www.hds.utc.fr/~barre/

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