From: Earnie B. <ea...@us...> - 2013-05-18 17:48:43
|
On Sat, May 18, 2013 at 4:06 AM, Eli Zaretskii wrote: >> Date: Fri, 17 May 2013 17:25:00 -0400 >> From: Earnie Boyd >> >> The issue I'm trying to overcome is the system on XP doesn't have some >> functions and data structures in MSVCRT that Vista/Win7/Win8 etc have >> such as the stat structure being defined in stat.h. It is quite >> maddening. > > Can you tell the details, like what functions and data structures are > involved? > The one I know off hand are the stat structures and depending on the MSVCRT whether or not certain data types such as 32bit time_t. >> The values are (MajorLinkerVersion * 100) + MinorLinkerVersion where >> LinkerVersion refers to the version of MSVC that was used to create >> MSVCRT.DLL that exists on your system. > > Beware: old versions of objdump don't show MajorLinkerVersion and > MinorLinkerVersion, so your script should probably test the version of > objdump as well, and fall back on 710 if the version is too old. My > limited testing indicates that Binutils 2.17 didn't support that, > while 2.22 does. So the cutoff version is somewhere in between. > Thanks for that bit of information. It sounds as if 710 would be a safe default. Those with less can define MSVCRT_VERSION before the configure script executes. > Anyway, I get 710 on XPSP3 and 900 on 2 different Windows 7 machines. > (Note that on a 64-bit Windows 7, we are likely getting msvcrt.dll > from syswow64, not from system32, assuming that objdump being used is > a 32-bit executable.) I just checked that and they are the same. Do you think times 100 is enough for the major version or should I go for 1000? -- Earnie -- https://sites.google.com/site/earnieboyd |