[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2009-05-13 Thread fxcoudert at gcc dot gnu dot org 


--- Comment #8 from fxcoudert at gcc dot gnu dot org  2009-05-13 19:48 
---
As far as I know, this one has disappeared a long time ago.


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||WORKSFORME


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382

[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2008-02-05 Thread fxcoudert at gcc dot gnu dot org 


--- Comment #7 from fxcoudert at gcc dot gnu dot org  2008-02-05 12:03 
---
This problem is not seen on 4.3.0.


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

  Known to work||4.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382

[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2006-03-08 Thread fxcoudert at gcc dot gnu dot org 


--- Comment #5 from fxcoudert at gcc dot gnu dot org  2006-03-08 09:29 
---
Confirmed on gcc mailing-list.


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2006-03-08 09:29:10
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382

[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2006-03-08 Thread rmathew at gcc dot gnu dot org 


--- Comment #6 from rmathew at gcc dot gnu dot org  2006-03-08 11:40 ---
(In reply to comment #5)
 Confirmed on gcc mailing-list.

Reconfirmed with the GCC 4.1.0 release tarballs for C (core)
and C++ (g++). In addition to using --with-ld, one has to
also use a relative path to the configure script instead of
an absolute path for the bootstrap to work.


-- 

rmathew at gcc dot gnu dot org changed:

   What|Removed |Added

   Last reconfirmed|2006-03-08 09:29:10 |2006-03-08 11:40:22
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382

[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2005-12-11 Thread sherpya at netfarm dot it 


--- Comment #3 from sherpya at netfarm dot it  2005-12-11 08:09 ---
looking at gcc/Makefile
ORIGINAL_LD_FOR_TARGET =
./j:/mingw/bin/../lib/gcc/mingw32/4.0.2/../../../../mingw32/bin/ld.exe
ORIGINAL_NM_FOR_TARGET = /mingw/bin/nm

so LD path takes a : that interfers with make,
on gcc 402 it works fine, so I think the problem is how configure finds the
path of ld, somehow changed


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382

[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2005-12-11 Thread sherpya at netfarm dot it 


--- Comment #4 from sherpya at netfarm dot it  2005-12-11 20:41 ---
My latest build unaffected from this bug is 4.1.0 cvs 20051013 (now I've
switched to svn), anyway fixing the ld path compiles fine.


-- 

sherpya at netfarm dot it changed:

   What|Removed |Added

 CC||sherpya at netfarm dot it


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382

[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2005-10-17 Thread bonzini at gcc dot gnu dot org 


--- Comment #1 from bonzini at gcc dot gnu dot org  2005-10-17 06:59 ---
Since when?  I can't make sense of this.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382

[Bug bootstrap/24382] ORIGINAL_LD_FOR_TARGET has bizarre value

2005-10-17 Thread fxcoudert at gcc dot gnu dot org 


--- Comment #2 from fxcoudert at gcc dot gnu dot org  2005-10-17 07:07 
---
I don't know when it appeared, since I only make monthly builds on mingw32. I
think it wasn't there on 2005-09-02, but that's all I can say.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24382