On 15 August 2010 18:32, Dan Tsafrir wrote:
>> I've done exactly this, then tried to install some X stuff and got:
>>
>> Package: xinit
>> xinit.sh exit code 8
>> Package: No package
>> xinit.sh exit code 8
>>
>
> It turns out that the above error message is generated by
On Sun, Aug 15, 2010 at 04:03, Dan Tsafrir wrote:
>
> I've done exactly this, then tried to install some X stuff and got:
>
> Package: xinit
> xinit.sh exit code 8
> Package: No package
> xinit.sh exit code 8
>
It turns out that the above error message is generated by
On Tue, Aug 10, 2010 at 15:12, Jon TURNEY wrote:
> On 10/08/2010 00:19, Bob Kline wrote:
>>
>> I finally had to replace my ancient Windows XP box, and ended up with a
>> Windows 7 Home Premium 64-bit system. If I run setup.exe to install a
>> fresh
>> cygwin, it succeeds as long as I don't touch t
On Wed, 11 Aug 2010, Bob Kline wrote:
On 8/10/2010 8:12 AM, Jon TURNEY wrote:
I'm a bit surprised that gcc4 is a dependency of X.
It's a dependency of imake, which is a member of the XWin set.
imake uses the C preprocessor...
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-
On 8/10/2010 8:12 AM, Jon TURNEY wrote:
I'm a bit surprised that gcc4 is a dependency of X.
It's a dependency of imake, which is a member of the XWin set.
--
Bob Kline
mailto:bkl...@rksystems.com
http://www.rksystems.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Pro
On 8/10/2010 11:49 AM, Jon TURNEY wrote:
and since all xinit.sh does is run mkshortcut to create a start menu
shortcut, I'd guess this is the same issue as [1], assuming we don't
have a cygutils release with that fixed yet.
[1] http://sourceware.org/ml/cygwin/2010-03/msg00357.html
Right. As
On 10/08/2010 13:12, Jon TURNEY wrote:
On 10/08/2010 00:19, Bob Kline wrote:
I finally had to replace my ancient Windows XP box, and ended up with a
Windows 7 Home Premium 64-bit system. If I run setup.exe to install a fresh
cygwin, it succeeds as long as I don't touch the X11 set, leaving it at
On 8/10/2010 11:16 AM, Jim Reisert AD1C wrote:
Bob, FYI, I've been running Cygwin 1.7x and latest X on Win 7 Pro
64-bit and not problems setting up or running. In other words, it
works right out of the box.
Thanks for the data point, Jim. The two possible explanations that come
to mind f
On 8/10/2010 8:12 AM, Jon TURNEY wrote:
gcc4-core.sh exit code 126
This one is already reported at [1], and the workaround given
there,i.e.
Thanks for your reply. I had seen that report, but was dismayed to see
that the poster had received no response to his questions about whether
t
On 10/08/2010 00:19, Bob Kline wrote:
I finally had to replace my ancient Windows XP box, and ended up with a
Windows 7 Home Premium 64-bit system. If I run setup.exe to install a fresh
cygwin, it succeeds as long as I don't touch the X11 set, leaving it at
Default (which is to say, don't install
I finally had to replace my ancient Windows XP box, and ended up with
a Windows 7 Home Premium 64-bit system. If I run setup.exe to install a
fresh cygwin, it succeeds as long as I don't touch the X11 set, leaving
it at Default (which is to say, don't install anything in the set). If
I chang
11 matches
Mail list logo
