Cygport woes: CHOST not defined.

2011-03-17 Thread Dave Korn
Hi list, Attempting to rebuild gcc4-4.3.4-3 from source, I got a bunch of error messages during the install stage of cygport: > Fixing libtool modules: > /usr/lib/cygport/src_postinst.cygpart: line 763: test: i686-pc-cygwin: unary > operator expected [ ... snip several more ... ] > St

Re: Cygport woes: CHOST not defined.

2011-03-17 Thread Dave Korn
On 17/03/2011 19:39, Dave Korn wrote: > Looking at the context, I infer that CHOST must be undefined: Ah, it's my cygport script. For some reason I used to have a problem with the setting of CHOST by the default cygport script, so it unsets it. Hopefully I can just omit that with the newer c

Re: Cygport woes: CHOST not defined.

2011-03-17 Thread Yaakov (Cygwin/X)
On Thu, 2011-03-17 at 19:39 +, Dave Korn wrote: > Attempting to rebuild gcc4-4.3.4-3 from source, I got a bunch of error > messages during the install stage of cygport: > > [ ... snip several more ... ] > > Looking at the context, I infer that CHOST must be undefined: > ... and quite

Re: Cygport woes: CHOST not defined.

2011-03-17 Thread Dave Korn
On 18/03/2011 02:50, Yaakov (Cygwin/X) wrote: > On Thu, 2011-03-17 at 19:39 +, Dave Korn wrote: >> Attempting to rebuild gcc4-4.3.4-3 from source, I got a bunch of error >> messages during the install stage of cygport: >> >> [ ... snip several more ... ] >> >> Looking at the context, I

gcc4 outstanding issues (was Re: Cygport woes: CHOST not defined.)

2011-03-18 Thread Yaakov (Cygwin/X)
On Fri, 2011-03-18 at 05:18 +, Dave Korn wrote: > On 18/03/2011 02:50, Yaakov (Cygwin/X) wrote: > > BTW, do you need me to resend my patches for 4.5.2? > > Couldn't hurt, I know I had some stuff to dig through my inbox looking for > but if you wouldn't mind... My outstanding issues with gc

Re: gcc4 outstanding issues (was Re: Cygport woes: CHOST not defined.)

2011-03-18 Thread Charles Wilson
On 3/18/2011 5:06 AM, Yaakov (Cygwin/X) wrote: > BTW, I wonder if we can begin mitigating (2) by not shipping the .la > files with GCC. This would stop those paths from being hardcoded into > other .la files, so that eventually only the libtool scripts will need > to be fixed. Yes, please. I thi