On Jul 23 01:38, Kris Thielemans wrote:
> Kris Thielemans writes:
>
> > I'm using gdb-7.6.50-2 on cygwin 1.7.22-1. All freshly updated today.
> >
> > Further investigation shows that
> > - this file exists in cygwin as /usr/include/tcl8.5/generic/tclInt.h
> > - /usr/lib/tclConfig.sh sets TCL_INC
On 2013-07-23 02:22, Corinna Vinschen wrote:
On Jul 23 17:47, Ryan Johnson wrote:
On 07/22/2013 05:38 PM, Yaakov (Cygwin/X) wrote:
gcc is only a source-only meta-package; you want to install
gcc-core, gcc-g++, etc.
Oh, that's a little different than (a) the name suggests and (b)
historical pre
On 2013-07-23 02:21, Corinna Vinschen wrote:
On Jul 22 23:40, Yaakov (Cygwin/X) wrote:
On 2013-07-22 19:52, Kenneth Wolcott wrote:
Postinstall errors:
Thanks for the feedback; remarks inline.
Package: bash
bash.sh exit code 1
I think the problem is that virtual /dev is a read-only fi
On Jul 23 03:27, Yaakov (Cygwin/X) wrote:
> On 2013-07-23 02:21, Corinna Vinschen wrote:
> >On Jul 22 23:40, Yaakov (Cygwin/X) wrote:
> >>On 2013-07-22 19:52, Kenneth Wolcott wrote:
> >>>Postinstall errors:
> >>
> >>Thanks for the feedback; remarks inline.
> >>
> >>>Package: bash
> >>> bash.sh
On Jul 23 03:20, Yaakov (Cygwin/X) wrote:
> On 2013-07-23 02:22, Corinna Vinschen wrote:
> >On Jul 23 17:47, Ryan Johnson wrote:
> >>On 07/22/2013 05:38 PM, Yaakov (Cygwin/X) wrote:
> >>>gcc is only a source-only meta-package; you want to install
> >>>gcc-core, gcc-g++, etc.
> >>Oh, that's a little
Corinna Vinschen cygwin.com> writes:
> >
> > > I'm using gdb-7.6.50-2 on cygwin 1.7.22-1. All freshly updated today.
>
> Here's my cygport file from the 64 bit GDB package:
>
> CYGCONF_ARGS="--disable-gdbtk --with-system-readline"
Hi Corinna
excellent! This worked for me (on 32bit cygwin) :
Hi...
Due to some odd hangs in some past versions of cywin1.dll (1.7.18 -
1.7.21) I was still using 1.7.17. Now I gave 1.7.22 a new try. The
blocks seem to be resolved but well it appears that cygwin can now no
longer break running standard windows/mingw tools.
I am using 1.7.22 (32bit) with
I've wiped my old version of Cygwin and installed it fresh on my computer
and 1.7.21 doesn't work for me, either 32 or 64 bit. I have tried a Win
7 x86
virtual machine and it worked, on a Win 8 x86 virtual machine though I see
the same error. Therefore I guess it is a Windows 8 issue unless you
On 7/23/2013 07:51, Richard H Lee wrote:
> I'm trying to compile the following basic program on cygwin64:
>
> int main() {
> ;
> return 0;
> }
>
> But I get the following errors:
>
> $ gcc test.c
> /usr/lib/gcc/x86_64-pc-cygwin/4.8.1/../../../../x86_64-pc-cygwin/bin/ld:
> cannot find -ladvap
I have had problems with file permissions myself - in my case editing
a file that is part of a fairly large project may cause build errors
later on, when such a file is copied during the build process, because
the Windows permissions are translated into "---". It may very
well be that you are d
On 23/07/2013 13:35, JonY wrote:
Try rerunning setup again, there was a mistake in the w32api-runtime -1
release. -2 should have this fixed.
Yeah, I just installed xxd 5 mins ago and I saw w32api-runtime flash up
on the download bar. I figured that was the package and gave gcc another
shot. I
On Jul 23 12:51, Roland Schwingel wrote:
> Hi...
>
> Due to some odd hangs in some past versions of cywin1.dll (1.7.18 -
> 1.7.21) I was still using 1.7.17. Now I gave 1.7.22 a new try. The
> blocks seem to be resolved but well it appears that cygwin can now
> no longer break running standard wind
On 7/23/2013 8:28 AM, Daniel Brown wrote:
I've wiped my old version of Cygwin and installed it fresh on my computer
and 1.7.21 doesn't work for me, either 32 or 64 bit. I have tried a Win
7 x86
virtual machine and it worked, on a Win 8 x86 virtual machine though I see
the same error. Therefore I
On Jul 23 13:28, Daniel Brown wrote:
> I've wiped my old version of Cygwin and installed it fresh on my computer
> and 1.7.21 doesn't work for me, either 32 or 64 bit. I have tried a
> Win 7 x86
> virtual machine and it worked, on a Win 8 x86 virtual machine though I see
> the same error. Therefore
I've wiped my old version of Cygwin and installed it fresh on my computer and
1.7.21 doesn't work for me, either 32 or 64 bit. I have tried a Win 7 x86
virtual machine and it worked, on a Win 8 x86 virtual machine though I see the
same error. Therefore I guess it is a Windows 8 issue unless you
On Jul 23 15:08, Corinna Vinschen wrote:
> On Jul 23 13:28, Daniel Brown wrote:
> > and that still had the fork error. I have also tried running in safe
> > mode and
> > stopping all my anti-virus software just incase that was interfering
> > somehow.
> > So I get as an output now...
> >
> > Danie
> Hello!
> I have successfully tested it on i386. Really, just remove PREFIX
> completely and it's okay. GetProcAddress() appears to be "clever" and adds
> the leading underscope by itself on i386. I don't know what you did wrong
> and why you could not reproduce the solution.
> However, i have
On Jul 23 16:18, Corinna Vinschen wrote:
> On Jul 23 15:08, Corinna Vinschen wrote:
> > On Jul 23 13:28, Daniel Brown wrote:
> > > and that still had the fork error. I have also tried running in safe
> > > mode and
> > > stopping all my anti-virus software just incase that was interfering
> > > som
On 7/11/2013 10:11 AM, Corinna Vinschen wrote:
On Jul 11 09:34, J. David Boyd wrote:
Ken Brown writes:
On 7/10/2013 5:10 PM, Christopher Faylor wrote:
Thanks. It's also possible that this isn't a Cygwin problem. There
are known race conditions between emacs-24.3 and glib, which have been
f
I just updated Cygwin to the latest version from one that had been
installed in maybe 2009... old.
During the update process there was a note to go to cygwin.com to see
what had changed in the new version that might affect me, but in the
"upgrade" or the "faq" area I could find nothing warning
On 22/07/2013 16:23, Christopher Faylor wrote:
> We have updated the setup.exe executables on cygwin.com in preparation
> for the upcoming release of Cygwin 1.7.22.
> ...
I hit a couple of problems using the new 32-bit setup yesterday -
during which it managed to break my installation.
System is
On Tue, Jul 23, 2013 at 03:20:11AM -0500, Yaakov (Cygwin/X) wrote:
>On 2013-07-23 02:22, Corinna Vinschen wrote:
>> On Jul 23 17:47, Ryan Johnson wrote:
>>> On 07/22/2013 05:38 PM, Yaakov (Cygwin/X) wrote:
gcc is only a source-only meta-package; you want to install
gcc-core, gcc-g++, etc.
On 7/23/2013 12:40 AM, Yaakov (Cygwin/X) wrote:
On 2013-07-22 19:52, Kenneth Wolcott wrote:
Postinstall errors:
Package: xinit
xinit.sh exit code 134
This is from a SIGABRT in mkshortcut. Chuck?
From xinit.sh:
/usr/bin/mkshortcut $CYGWINFORALL -P .
where $CYGWINFORALL is p
On Jul 23 14:14, Charles Wilson wrote:
> On 7/23/2013 12:40 AM, Yaakov (Cygwin/X) wrote:
> >On 2013-07-22 19:52, Kenneth Wolcott wrote:
> >>Postinstall errors:
> >>
> >>Package: xinit
> >> xinit.sh exit code 134
> >
> >This is from a SIGABRT in mkshortcut. Chuck?
>
> From xinit.sh:
> /u
Ken Brown writes:
> On 7/11/2013 10:11 AM, Corinna Vinschen wrote:
>> On Jul 11 09:34, J. David Boyd wrote:
>>> Ken Brown writes:
>>>
On 7/10/2013 5:10 PM, Christopher Faylor wrote:
Thanks. It's also possible that this isn't a Cygwin problem. There
are known race conditions
On 7/23/2013 2:46 PM, Corinna Vinschen wrote:
On Jul 23 14:14, Charles Wilson wrote:
I believe your report has to do with error handling when attempting
to modify the All User's Desktop, when you don't actually retain the
elevated permissions necessary to do so.
Is there are way for setup.exe
On Jul 23 15:08, Charles Wilson wrote:
> On 7/23/2013 2:46 PM, Corinna Vinschen wrote:
> >On Jul 23 14:14, Charles Wilson wrote:
> >>>I believe your report has to do with error handling when attempting
> >>>to modify the All User's Desktop, when you don't actually retain the
> >>>elevated permissio
da...@adboyd.com (J. David Boyd) writes:
> Ken Brown writes:
>
>>> http://cygwin.com/snapshots/
>>
>> Dave,
>>
>> This should be fixed now in the latest snapshot (2013-07-23). See
>>
>> http://cygwin.com/ml/cygwin/2013-07/msg00481.html
>>
>> Ken
>
> Great, thanks. I'll get it right away and t
On 2013-07-23 03:59, Corinna Vinschen wrote:
On Jul 23 03:27, Yaakov (Cygwin/X) wrote:
On 2013-07-23 02:21, Corinna Vinschen wrote:
On Jul 22 23:40, Yaakov (Cygwin/X) wrote:
echo letter > /etc/papersize
I'd prefer `echo a4 > /etc/papersize' ;)
I suppose you would. :-) Any idea how to prov
On 2013-07-23 11:16, Christopher Faylor wrote:
On Tue, Jul 23, 2013 at 03:20:11AM -0500, Yaakov (Cygwin/X) wrote:
This is one case where IMO genini is better than upset: genini-generated
setup.ini's don't list source-only packages in setup's package selector,
while still being available through
Stefan Lisowski writes:
> I just updated Cygwin to the latest version from one that had been
> installed in maybe 2009... old.
>
> During the update process there was a note to go to cygwin.com to see
> what had changed in the new version that might affect me, but in the
> "upgrade" or the "faq"
The following packages have been updated for both arches:
* libpaper1-1.1.24-2
* libpaper-common-1.1.24-2
* libpaper-devel-1.1.24-2
* paperconf-1.1.24-2 (replaces libpaper-bin)
The libpaper paper-handling library automates recognition of many
different paper types and sizes for programs that nee
Christopher Faylor cygwin.com> writes:
> There is no reason to be nervous about installing snapshots if you think
> a new release will solve a problem. A snapshot potentially always
> equals a new release. Snapshots never break things so severely that you
> can't recover by just reinstalling cy
On Jul 22 23:40, Yaakov (Cygwin/X) wrote:
> On 2013-07-22 19:52, Kenneth Wolcott wrote:
> >Postinstall errors:
>
> Thanks for the feedback; remarks inline.
>
> >Package: bash
> > bash.sh exit code 1
>
> I think the problem is that virtual /dev is a read-only filesystem,
> but if you make a r
On Jul 23 17:47, Ryan Johnson wrote:
> On 07/22/2013 05:38 PM, Yaakov (Cygwin/X) wrote:
> >On 2013-07-23 16:26, Ryan Johnson wrote:
> >>If I select the gcc-4.8.1-1 package from setup-64, it downloads and
> >>installs the gcc-4.8.1-src package
> >
> >gcc is only a source-only meta-package; you want
I wanted to compile the WWW::Mechanize Perl library, which looked for
crypt.h then could not find it. I installed the crypt-1.1-1 library
but it was not there either. I ended up copying crypt.h from
/usr/include in my 32-bit Cygwin installation to the same directory in
my 64-bit Cygwin installati
How can I cycle through my fonts in rxvt (non-X11 version) if I don't
have a numeric keypad? The manpage mentions bigfont_key and
smallfont_key "if enabled", but I haven't been successful getting them
to do anything. Perhaps I need to recompile rxvt and enable that
option?
Thanks for any suggest
On 2013-07-23 19:09, Jim Reisert AD1C wrote:
I wanted to compile the WWW::Mechanize Perl library, which looked for
crypt.h then could not find it. I installed the crypt-1.1-1 library
but it was not there either.
The crypt package provides just crypt(1); you need libcrypt-devel for
the header
Greetings, Josh Litherland!
> How can I cycle through my fonts in rxvt (non-X11 version) if I don't
> have a numeric keypad? The manpage mentions bigfont_key and
> smallfont_key "if enabled", but I haven't been successful getting them
> to do anything. Perhaps I need to recompile rxvt and enable
On Tue, Jul 23, 2013 at 02:54:29PM -0500, Yaakov (Cygwin/X) wrote:
>On 2013-07-23 11:16, Christopher Faylor wrote:
>> On Tue, Jul 23, 2013 at 03:20:11AM -0500, Yaakov (Cygwin/X) wrote:
>>> This is one case where IMO genini is better than upset: genini-generated
>>> setup.ini's don't list source-onl
> The crypt package provides just crypt(1); you need libcrypt-devel for the
> header and link library, and libcrypt0 for the DLL.
Thanks, Yaakov. I don't see that package. In 64-bit setup, I found:
cygwin64-crypt
cygwin64-libgcrypt
libgcrypt-devel
libmcrypt-devel
Which of these packages most
Greetings, Jim Reisert AD1C!
>> The crypt package provides just crypt(1); you need libcrypt-devel for the
>> header and link library, and libcrypt0 for the DLL.
> Thanks, Yaakov. I don't see that package. In 64-bit setup, I found:
64-bit Cygwin isn't ready for wide deployment, it is in test s
On Wed, Jul 24, 2013 at 09:56:25AM +0400, Andrey Repin wrote:
>Greetings, Jim Reisert AD1C!
>
>>> The crypt package provides just crypt(1); you need libcrypt-devel for the
>>> header and link library, and libcrypt0 for the DLL.
>
>> Thanks, Yaakov. I don't see that package. In 64-bit setup, I fo
On 2013-07-24 00:14, Jim Reisert AD1C wrote:
The crypt package provides just crypt(1); you need libcrypt-devel for the
header and link library, and libcrypt0 for the DLL.
Thanks, Yaakov. I don't see that package. In 64-bit setup, I found:
cygwin64-crypt
cygwin64-libgcrypt
libgcrypt-devel
li
Hello!
> Sorry, this was my fault. I accidentally mangled your patch when I
> took PREFIX out. I fixed that, and it works fine in x86 now.
Good.
Please don't forget that packages which make use of libargp (if there are
any) have to be recompiled against new argp.h in order to take advantage
45 matches
Mail list logo
