Re: Newbie question
From what I understand, you shouldn't be using _i386 as
your architecture type. This seems to indicate for a unix
kernel. The packages I built under my cygwin
environment were built with a _w32 architecture. I don't
even really like that, because I think we need to differentiate
between native windows type apps, and cygwin dependant
apps, since in my mind they also operate using a different
kernel.
I guess that's a question for the group. Does cygwin present
enough of an extension to Microsoft windows that is could be
considered and independant "flavour" of a kernel, and thus
require another kernel-type indicator?
On Wed, 12 Feb 2003 07:54:59 -0800 (PST), James Michael DuPont wrote:
>please check my packages on the debian
>http://introspector.sourceforge.net/debian/incoming/
>
>All of the ming32 packages have ming in the name,
>For example :
>http://introspector.sourceforge.net/debian/incoming/libiconv-mingw1_1.8.20020902-1_i386.deb
>
>I have created them under the Debian gnu/linux system
>
>$ dpkg -i libiconv-mingw1_1.8.20020902-1_i386.deb
>dpkg: error processing libiconv-mingw1_1.8.20020902-1_i386.deb
>(--install):
> package architecture (i386) does not match system (cygwin-i386)
>Errors were encountered while processing:
> libiconv-mingw1_1.8.20020902-1_i386.deb
>
>Ok, so forcing will produce these errors :
>
>$ dpkg --force-all -i libiconv-mingw1_1.8.20020902-1_i386.deb
>dpkg - warning, overriding problem because --force enabled:
> package architecture (i386) does not match system (cygwin-i386)
>Selecting previously deselected package libiconv-mingw1.
>(Reading database ... 0 files and directories currently installed.)
>Unpacking libiconv-mingw1 (from
>libiconv-mingw1_1.8.20020902-1_i386.deb) ...
>dpkg: error processing libiconv-mingw1_1.8.20020902-1_i386.deb
>(--install):
> error setting ownership of `./usr/share/doc/libiconv-mingw1': Invalid
>argument
>Errors were encountered while processing:
> libiconv-mingw1_1.8.20020902-1_i386.deb
>
>Any ideas?
what is libiconv-mingw1? Is it a .dll or .exe? If so, then you will have to
modify the preinst & postinst scripts to account for any windows specific
extensions, such as .dll & .exe. Painful and tedious, but necessary.
>mike
>
>
>--- Jeremie Koenig <sprite@sprite.fr.eu.org> wrote:
>> On Mon, Feb 10, 2003 at 01:11:42PM -0800, James Michael DuPont wrote:
>>
>> > As far as I know, APT is not compiled, but dpk is. I have had
>> problems
>> > with dpkg because of the setroot. It is good for unpacking things,
>> but
>> > not installing them.
>>
>> I suppose, dpkg is chroot'ing while configuring packages installed
>> with
>> --root. Anyway, don't packages expect being installed in / ? Are you
>> using a special build process or anything to avoid such problems ?
>> Just
>> by curiosity...
>>
>> --
>> Jeremie Koenig <sprite@sprite.fr.eu.org>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-win32-request@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>>
>
>
>=====
>James Michael DuPont
>http://introspector.sourceforge.net/
>
>__________________________________________________
>Do you Yahoo!?
>Yahoo! Shopping - Send Flowers for Valentine's Day
>http://shopping.yahoo.com
>
>
>--
>To UNSUBSCRIBE, email to debian-win32-request@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: