Volker,
I have not investigated this further but it looks like the mingw32 package requires a patch so that it generates cross versions for w32-i386 (GNU: i486-mingw32msvc), and not i586-mingw32msvc. The only correct CPU for Debian is AFAIK i386, which gets translated to i486 GNU CPU. So, my guess would be to add w32 to ostable and re-compile mingw32 package to use w32-i386 (and thus i486-mingw32msvc). My patch adresses a different problem of allowing CPU-ABI, CPU-LIBC, OS-CPU-LIBC, OS-CPU-ABI and CPU-CPU-LIBC-ABI schemes. Supposing that people are willing to split mingw32msvc into OS=w32, LIBC=msvc and ABI=ming, the mapping for my dpkg-architecture version would become w32-i386-msvc-ming (GNU: i486-w32-msvc-ming), which IMHO would make more sense than i586-mingw32msvc. Greetings, Pjotr Kourzanov Volker Grabsch wrote: > On Mon, Jun 12, 2006 at 03:19:51PM +0200, Pjotr Kourzanov wrote: >> Updated patch can be found here: >> >> http://www.xs4all.nl/~kurzanov/debian/patches/dpkg-1.13.16-all-1.patch. > > What about the w32 OS? > > Currently, I'm adding > > w32 mingw32msvc mingw32[^-]* > > to the ostable and use "w32-i386". This is not very nice, because this > produces: > > $ dpkg-architecture -aw32-i386 > [...] > DEB_HOST_ARCH=w32-i386 > DEB_HOST_ARCH_OS=w32 > DEB_HOST_ARCH_CPU=i386 > DEB_HOST_GNU_CPU=i486 > DEB_HOST_GNU_SYSTEM=mingw32msvc > DEB_HOST_GNU_TYPE=i486-mingw32msvc > > ... while the "mingw32" package has the GNU type "i586-mingw32msvc". > Thus, I'm adding to ~/.dpkg-cross/cross-compile: > > crossprefix = i586-mingw32msvc- > crossdir = /usr/i586-mingw32msvc > > Of course, I could now start using "w32-i586" instead. But currently, > this would require me to create an "i586" entry to the cputable. In the > long run that would mean adding "i486", "i586", "i686", "k6", ... > to the cputable, which surely isn't desireable, is it? > > Does your new dpkg-architecture system provide some "straight forward" > way for me to go? Or is my problem (using an i386-CPU other than i486) > yet another problem the dpkg-architecture doesn't care about? > > I'd be very happy if someone could add the "w32" ostype (should I > prepare a patch?) and if "w32-i586" would just work without any > additional entries to the cputable. Will your patch enable me to do > that? > > (A regex which matches i486, i586, pentium, etc. is already provided > by the i386 cputable entry.) > > > Greets, > > Volker > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
