Hello all,
Recently, I try to install cygwin under GNU/Linux + Wine.
But all version of setup.exe failed.
My system software list:
linux-kernel-2.6.25.7
binutils-2.18
glibc-2.7
gcc-4.3.1
xorg-7.3
wine-1.1.2
So I port setup.exe with winelib, it work fine.
After install cygwin under wine,
I try to
On Sun, Aug 10, 2008 at 01:31:54AM +0400, Andry wrote:
>Hello cygwin,
>
>>> Hello cygwin,
>>>
>>> I found 2 missed components which fixes postinstall errors: "ash" and
>>> "tar".
>> Yes, I noticed this bug myself just the other day when doing a completely
>>fresh install during setup.exe testi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Brian Dessent on 8/9/2008 3:30 PM:
| Dave Korn wrote:
|
|> The problem is that no matter whether bash or ash install /bin/sh,
|> terminfo is going to be installed first, and that means
|> /etc/postinstall/terminfo.sh is pretty much doom
Dave Korn wrote:
> The problem is that no matter whether bash or ash install /bin/sh,
> terminfo is going to be installed first, and that means
> /etc/postinstall/terminfo.sh is pretty much doomed to failure.
And, additionally, no postinstall is run until after all the tarballs
have been unpack
Hello cygwin,
>> Hello cygwin,
>>
>> I found 2 missed components which fixes postinstall errors: "ash" and
>> "tar".
> Yes, I noticed this bug myself just the other day when doing a completely
>fresh install during setup.exe testing.
Oh, i fixed this stupid install system problem. You guys sh
Dave Korn wrote:
> The problem is that no matter whether bash or ash install /bin/sh,
> terminfo is going to be installed first, and that means
> /etc/postinstall/terminfo.sh is pretty much doomed to failure.
Then that is a bug with terminfo's setup.hint; any package with a
postinstall should i
On Sat, Aug 09, 2008 at 09:35:35PM +0100, Dave Korn wrote:
>... Hmm, where did my post to the apps list go? Can't find a bounce
>message either... maybe the attached .png made it look like spam.
No, it was the application/msword attachment. Apparently whatever you
used to send the email interp
Brian Dessent wrote on 09 August 2008 20:55:
> Dave Korn wrote:
>
>> I'll try and think up a fix for this. In the meantime, you can work
>
> I'll repeat my previous opinion on this issue: I think the time for
> compensating for the ash -> bash upgrade is over and we should just have
> bash pr
Dave Korn wrote:
> I'll try and think up a fix for this. In the meantime, you can work
I'll repeat my previous opinion on this issue: I think the time for
compensating for the ash -> bash upgrade is over and we should just have
bash provide /bin/sh directly without the complicated postinstall
Andry wrote on 09 August 2008 13:26:
> Hello cygwin,
>
> I found 2 missed components which fixes postinstall errors: "ash" and
> "tar".
Yes, I noticed this bug myself just the other day when doing a completely
fresh install during setup.exe testing.
> If tar is used in postinstall script
Hello cygwin,
I found 2 missed components which fixes postinstall errors: "ash" and
"tar". If tar is used in postinstall scripts, but ash is not, and i
don't know why ash fixes run of "base-files-profile.sh" and etc
scripts:
2008/08/09 16:16:07 Dependency ordered install:
2008/08/09 16:16
On Aug 8 22:16, Heinz Werner Kramski-Grote wrote:
> With cygwin1.dll 1.5.24-2 I am able to
> checksum the raw floppy device successfully using md5sum:
>
>$ md5sum /dev/fd0
>f8e9627946048ac9bc3109478ef09215 */dev/fd0
>
> After upgrading to 1.5.25-15 I now get this error:
>
>$ md5sum /de
12 matches
Mail list logo
