X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Message-ID:	<BAY139-W19808358F507B7930E7F6EE6940@phx.gbl>
X-Originating-IP:	[71.112.20.48]
From:	Jay <jayk123 AT hotmail DOT com>
To:	<djgpp AT delorie DOT com>
Subject:	libstdc++ writev/2.04/patches upstream?
Date:	Mon, 7 Jul 2008 19:01:56 +0000
Importance:	Normal
In-Reply-To:	<200807070405.m67451dZ010910@delorie.com>
References:	<200807070405 DOT m67451dZ010910 AT delorie DOT com>
MIME-Version:	1.0
X-OriginalArrivalTime:	07 Jul 2008 19:01:57.0377 (UTC) FILETIME=[EDA9C710:01C8E063]
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id m67JELhp030391
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Multiple rude/half-lazy questions:


I'm trying to build cygwin-host, djgpp-target v2.03.
If I can do that, I'll then cross-build native djgpp.
binutils and gcc at least.
If I'm really ambitious, I'll try to build "everything"
 very automated, but that is way out there.


binutils-2.18 seems to build right out of the box.


I was able to build gcc on another system that I don't have access to at the moment,
but am hitting problems on a second system. The first was XP/x86, the second XP/AMD64.


rude:
 What is the status of 2.04?
   It seems it was last discussed around 2006.
 Ok, well, my answer would be, once I build it, maybe I can help.
 "It" being 2.03/2.04/current cvs, not sure.
 Should be easier to start with a "release" and move to "current" ?


 What is the status of getting diffs propagated upstream?
 Specifically, I can build binutils-2.18 cygwin-host djgpp-target, no patches.
 But gcc the patches don't appear present in 4.3.1.
   I checked just one or two.
 I understand there is no obligation to submit or accept diffs.
 But it would be nice.


half-lazy -- I did a fair amount of investigation here:


 What is the story on writev and building djgpp-patched 4.23? (i.e. gcc423s.zip, gcc423s2.zip) 
 libstdc++-v3 fails due to __iov being incomplete.
 It has something to do with 
   GLIBCXX_CHECK_WRITEV
 vs.


  *djgpp)
...
D:\djgpp\gnu\gcc-4.23\libstdc++-v3\crossconfig.m4(61):    AC_DEFINE(HAVE_WRITEV)


crossconfig.m4 is hardcoded for 2.04?
I see current cvs has writev, but that 2.03 does not.
I'm trying to build cygwin-host djgpp-target gcc.


Someone else on the web hit this problem and they #undefed _GLIBCXX_HAVE_WRITEV in libstdc++-v3\config\io\basic_file_stdio.cc, but that is not the right fix.


It seems the second should be replaced by the first. ?
I'll try that later.


I suspect if I setup an LFN-aware native DJGPP, this would configure correctly,
but that cross builds avoid the probe, but that probing would work, since
by now there is a cross-ld and I do get a gcc.exe.
I'm on AMD64 XP and DOS is DosBox currently, so no LFN.


I have no real need for djgpp, but it seems neat, and like everyone
else I have the hardware/software to run it, and I like to build
things myself.


(Sure is slow, e.g. building zip/unzip with gcc under DosBox.
Will try native and VMware/VirtualPC later..)


 Thanks,
  - Jay

- Raw text -