Hi,
I would like to compile a python module under cygwin.
It fails with the following error:
gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
-DG_LOG_DOMAIN="BibTeX" -I/opt/gnome2/include/glib-2.0
-I/opt/gnome2/lib/glib-2.0/include -I/usr/include/python2.3 -c
bibtexmodule.c -o
> From: Brian Dessent
>
> What ever happened to the internet where netiquette actually meant
> anything? You know, that whole thing about keeping signatures to less
> than 4 lines x 72 chars, not quoting entire messages, not sending HTML
> email to public lists, and so on?
Unfortunately I have a
Hi all:
I reported this in python 2.2.2 in December, and it's still
an issue on one of my systems with python 2.3.4.
When running python -c "import sys; print sys.executable" it prints
the current working directory rather than the path to python unless
I invoke python with the full path.
I can't
* Jason Tishler (2004-06-11 20:17 +0100)
> New News:
> ===
> I have updated the version of Python to 2.3.4-1. The tarballs should be
> available on a Cygwin mirror near you shortly.
>
> The following is the only notable change since the previous release:
>
> o upgrade to Python 2.3.4
>
Is there a change in the handling of the $TMP directory in recent
Cywin?! I never set this environment variable in my .zshrc or .bashrc
and nevertheless it alway pointed to /tmp (or at at least all Cygwin
applications I used created their temp files in /tmp. Now I noticed
that $TMP points to /cygdr
At 12:31 PM 6/12/2004, you wrote:
>Is there a change in the handling of the $TMP directory in recent
>Cywin?! I never set this environment variable in my .zshrc or .bashrc
>and nevertheless it alway pointed to /tmp (or at at least all Cygwin
>applications I used created their temp files in /tmp. No
At 06:11 PM 6/11/2004, you wrote:
>Larry Hall wrote, On 6/11/2004 5:22 PM:
>>Yes, libcygwin.a is the import library. But I don't understand why you need it (or
>>-lc either for that matter). Just compiling with Cygwin's
>>gcc/g++ gets you all this, unless you're using -mno-cygwin, in which case
On Fri, Jun 11, 2004 at 06:12:05PM +0100, Dave Korn wrote:
>Now quote *that* line at the top of the snapshots page. I dare you!
Done.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwi
On Fri, Jun 11, 2004 at 02:44:52PM -0400, Volker Quetschke wrote:
>Jason Tishler wrote:
>>New News:
>>===
>>I have updated the version of Python to 2.3.4-1. The tarballs should be
>>available on a Cygwin mirror near you shortly.
>>(snip)
>>In the US,
>>ftp://mirrors.rcn.net/mirrors/sources.re
I've updated to cygwin dll 1.5.10 a few days ago.
(I'm using Cygwin with Windows XP SP1, Korean version.)
And today I found a problem with the accessing files.
I was trying to use rsync to sync some of my files to another place,
but rsync was telling me those files had vanished, like:
file has va
"John P. Rouillard" wrote:
> When running python -c "import sys; print sys.executable" it prints
> the current working directory rather than the path to python unless
> I invoke python with the full path.
>
> I can't reproduce this on a win 98 box, but on a windows 2k sp4 things
> are broken.
>
Hello from Gregg C Levine
It happens I did just that, the first few times I tried downloading my
Cygwin materials from sites here in the US. The people there ignored
my mail, or just plain deleted it unread. I don't know why.
I also reported to them the problems with downloading the materials
fr
On Sat, Jun 12, 2004 at 06:56:24PM -0400, Gregg C Levine wrote:
>I also reported to them the problems with downloading the materials
>from them, when the site would inexplicably interrupt the process.
>What do you feel about deleting them from the list of allowable
>mirrors? We can include the alt
> I did some test and found out that ``every file whose path includes
> Korean characters weren't openable.'' Still, I could move arround those
[snip]
I just installed the XP SP2 "preview" or whatever they call it. One of the
things in the very long list of things it claims to fix is some proble
I'm a newbie to databases and cygwin, and I'm having a problem with ODBC.
When I paste the path of the below script to Cygwin, to connect to a
database using Perl's DBD::PgPP module, it seems to work because I get no
error message, but when I comment-out the $dsn definition that uses PgPP
and unco
>> [unknown ...
Sorry to provide an afterthought, but this might be helpful I hope:
Summarising, as looking through any of the logfiles sorted or otherwise is a
bit of a bind, I think the explanation of the sloth must lie somewhere in
the output of
strace /bin/wish84 | grep unknown
(a
I've just updated my entire Cygwin installation, and LilyPond now
crashes inside a Python2 call -- I'm not even sure where to START
looking for how to fix this, any tips?
The crash:
$ lilypond /usr/share/doc/lilypond-2.2.2/input/test/bar-lines.ly
[MESSAGE BOX]
PYTHON2 caused an invalid page fault
17 matches
Mail list logo
