that.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkkrKg8ACgkQpiWmPGlmQSNn+gCggmuMeMUW/yqXAD/cis+odUUu
910AoNo1cTDNIcDF33cYJhZ1ddfywXZ0
=QgY+
-END PGP SIGNATURE-
--
Unsubscribe info: http
ghostscript depends only on a
few X libraries; it does not require an X server unless you specify an
x11* output device, nor will an X server be installed as a dependency of
ghostscript. So you can still use the ghostscript package without
running X.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE
obsolete, contents now
in ghostscript package)
- Fixed font paths
- Added shared library and corresponding devel packages
That was fast, thanks!
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Phan, Linh H wrote:
I'm trying to port OpenInventor code and using the new opengl-1.1.0 and I
am getting
undefined _glXMakeCurrent symbols:
This is not relevant to Cygwin/X and should be taken to the main list.
Yaakov
Cygwin/X
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
sowiso wrote:
cygwin seems to have a problem with current (even though from 2003)
ScrollKeeper v0.3.14.
scrollkeeper is obsolete, being replaced by rarian. Packages are
available from Cygwin Ports:
applications. You really don't
expect glX* symbols to be in a *Win32* version of OpenGL, do you?
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkk+GQUACgkQpiWmPGlmQSMaYACg
don't have to
manually setfacl each file I create in cygwin?
Help appreciated, thanks.
The cygwin-xfree list is only for X11 inquiries. Moving this to the
main list.
Yaakov
Cygwin/X
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** libxml2-2.7.2-1
*** libxml2-devel-2.7.2-1
*** libxml2-doc-2.7.2-1
*** python-libxml2-2.7.2-1
This is the latest upstream version, with a patch for CVE-2008-4225/6.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** esound-0.2.41-1
*** libesd0-0.2.41-1
*** libesd-devel-0.2.41-1
This is an upstream version bump; see NEWS for changes. The library
packages have been renamed, and will
been true until November 12. But in the last four weeks
since X11R7.4, there have been ~500 messages on cygwin-xfree, including
30 announcements (including 3 xserver revisions). Comparatively, there
have been ~660 messages on cygwin including ~45 announcements.
Yaakov
Cygwin/X
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A.R. Burgers wrote:
thanks for your reply.
It must be an interference with the ghostscript-x11
package from cygwin-ports.sf.net that I have installed.
This package is at 8.62, and update-alternatives selects
gs-x11.exe from that package.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul McFerrin wrote:
I've tried looking for a Binary distribution of PHP that will work with
Apache 1 under cygwin. I bought a program thinking I HAD PHP but
discovered later that my current server had no PHP support.
I'm resorting to binary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
The order of libs is wrong for $(pkg-config --libs gtk+-2.0)
-lgtk-x11-2.0 -lgdk-x11-2.0 should be at the end.
$ pkg-config --libs gtk+-2.0
-L/usr/X11R6/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0
something else is the matter. Are you mixing versions between
Ports and the distro, or even some self-built packages? Where is the
- -L/usr/X11R6/lib coming from?
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
René Berber wrote:
You're wrong, libraries shared or static are dealt the same way by the
compiler which looks for its list of unresolved symbols and doesn't
re-scan libraries when another symbol appears.
Since I apparently didn't make myself
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chad Gorshing wrote:
Lately I have begun using pyyaml on a few projects and when using
cygwin, I install pyyaml manually. It is trivial enough and I don't
have a problem doing this. But I started wondering why this wasn't in
cygwin to start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cygport has been updated to 0.4.3 for Cygwin 1.5, and 0.9.4 for 1.7,
with similar changes to both:
* Requires libtool-2.2 throughout.
* cygpatch() tries with and without --binary.
* lndirs() uses lndir(1) unconditionally.
* Override pushd and popd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been added to the distribution:
*** gamin-0.1.10-1
*** libfam0-0.1.10-1
*** libfam-devel-0.1.10-1
*** libgamin1_0-0.1.10-1
*** libgamin1-devel-0.1.10-1
*** python-gamin-0.1.10-1
gamin is a portable drop-in replacement
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
Anyway, it compiles with my fixed order and gives the unresolved symbols
with the original $(pkg-config --libs gtk+-2.0) order of libs.
Please try it our yourself.
Listen, I've been building GNOME for years now. pkg-config's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
M.O.D. wrote:
Thanks for your comments, Yaakov. As you suspected, the order of the link
libraries made no difference.
I downloaded all of Cygwin at one time, in about an hour. I have not done
anything I know of that would mix versions. If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell wrote:
shouldn't that be /usr/lib/pkgconfig ?
No, it shouldn't; pkg-config looks at both.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andy Koppe wrote:
Christopher Faylor wrote:
I wouldn't mind making MinTTY a regular cygwin package. It sounds
like it
would get enough votes.
That would be great. I'll need to read up on the package submission
requirements and process.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gary R. Van Sickle wrote:
- Yeah, the no color thing was solved by putting the standard bash --login
-i on the shortcut's command line. That would be a nice one to have in the
configuration dialogs, but I don't see how you avoid the registry in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andy Koppe wrote:
Thank you very much! Yep, I'm entirely new to this, so what with those
pesky New Year festivities taking away valuable hacking time it might be
a little while to familiarise myself with this packaging lark. :)
I just simplified
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andy Koppe wrote:
Just a quick note to say I've uploaded release 0.3.1 of MinTTY. It fixes
broken non-ASCII output, increases the default font size to 10, and adds
a couple of easy enhancements: support for accelerator keys in the
options dialog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It would be a helpful enhancement to have a /proc/mounts interface to
the mountpoint data, with /etc/mtab perhaps being a symlink thereto. Is
this something that could be easily added, or is this a case of PTC?
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andy Koppe wrote:
I've uploaded MinTTY release 0.3.2 to http://code.google.com/p/mintty.
Ports SVN updated accordingly. I would encourage you to ITP this, as
this would be widely beneficial, and you will get more feedback as well.
Package
, i.e., the _[ -f *.cache-2 ]_ isn't a valid arg. Any
hints on this issue?
find /path/to/directory -name '*.cache-2' -delete
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
of MinTTY when MinTTY becomes a real package?
Or just switch rxvt to the regular X11 version w/o all the libW11 hackery?
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
George Ciobanu wrote:
My run blocks at test_httpservers, but I suspect this is because I
haven't been able to compile it fully. I've traced this problem to
graminit.o which contains the missing symbol, but I haven't had the time
to look in depth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andy Koppe wrote:
I've uploaded MinTTY 0.3.4 to http://code.google.com/p/mintty. This is a
more substantial bugfix release than the previous one, which addresses
the following issues:
I updated Ports SVN accordingly. Do you intend to ITP this
this file ?
The version of gtk2-x11-devel currently in the Cygwin distro is
out-of-date. I'm working on catching up GNOME in the distro, but in the
meantime, GNOME 2.24.2 is currently available at Cygwin Ports.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul McFerrin wrote:
I'm needing an expert on building PHP5 to work on Apache 1.3.22. What
am I doing wrong?
I'm having a dickens of a time building PHP5. Here is my confugure
command line:
./configure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andy Koppe wrote:
I worked it out, I think: run cygport prep command, copy the files into
foo-x.y.z-r/CYGWIN-PATCHES, and run cygport compile, install and package
commands.
Exactly.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vincent François wrote:
In wanting to use the syntax of the text editor NANO, I noticed a
problem. In the Cygwin, regular expressions \ and \ are not
recognized. In reading the man page (7 regex) I learned that he had
used respectively for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Vincent François wrote:
That I applied the new command (diff -u), the file syntax.nanorc.patch
is now join ;-)
Excuse me for my English, I am of French origin.
Merci beaucoup.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sjors Gielen wrote:
Did you try with Cygwin coreutils or GNU coreutils? :)
Cygwin's coreutils *is* GNU coreutils, with some patches which you will
find necessary.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using
the missing font for X11R7? Thank you very
much for any help in advance.
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-where-are-my-fonts
Please ask further Cygwin/X questions in the cygwin-xfree list.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin distribution:
*** util-linux-2.14.1-1
This is an update to the latest upstream version.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been added to the Cygwin distribution:
*** bind-9.6.0-1
*** libbind9-devel-9.6.0-1
*** libbind9_50-9.6.0-1
*** libdns-devel-9.6.0-1
*** libdns50-9.6.0-1
*** libisc-devel-9.6.0-1
*** libisc50-9.6.0-1
***
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following package has been added to the Cygwin distribution:
*** python-numpy-1.2.1-1
The NumPy module contains a powerful N-dimensional array object,
sophisticated (broadcasting) functions, tools for integrating C/C++ and
Fortran code, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jason Tishler wrote:
Yaakov, did you have openssl-devel installed when you built Python
2.6.1?
Yes, that is clearly indicated in the documentation.
If so, are you able to run the regression test [2] without threading
related problems?
Testing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the distribution:
*** gamin-0.1.10-2
*** libfam0-0.1.10-2
*** libfam-devel-0.1.10-2
*** libgamin1_0-0.1.10-2
*** libgamin1-devel-0.1.10-2
*** python-gamin-0.1.10-2
gamin is a portable drop-in replacement
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
This led to a suggestion that --build=cygwin --host=mingw32 should
always be interpreted as: mingw32-gcc is a cygwin-hosted cross compiler,
NOT the native MinGW-project supported gcc (and if it IS the native
MinGW one,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Right, if I'm building a compiler. I'm not -- although that wasn't very
clear, since the only examply I gave was Danny's incantation for
building gcc, a compiler. Oops.
I'm talking about building, say, ncurses so that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** libxml1-1.8.17-3
*** libxml-devel-1.8.17-3
This is a rebuild of version 1 of the GNOME XML library. Most packages
should NOT be using this; it is provided exclusively for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** libxml2-2.7.3-1
*** libxml2-devel-2.7.3-1
*** libxml2-doc-2.7.3-1
*** python-libxml2-2.7.3-1
This is an update to the latest upstream version.
Yaakov
DOWNLOAD:
=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** libfreetype6-2.3.8-1
*** libfreetype-devel-2.3.8-1
This is an upstream version bump; see CHANGES for changes. The library
packages were renamed slightly; setup.exe will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck Wilson wrote:
This is a packaging and bugfix update of the gettext package(s). This
will most likely be the final gettext update for the cygwin-1.5
distribution; future development will continue with gettext-0.17-10 for
cygwin-1.7.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I just implemented /proc/$PID/mounts as well as the /proc/mounts
symlink to /proc/self/mounts as on Linux. We just have to add
`ln -s /proc/mounts /etc/mtab' to some base script.
Great; thank you!
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steffen Sledz wrote:
I get this error when calling dig in cygwin-1.7. :(
$ dig @192.5.6.30 cygwin.com
/usr/src/ports/net/bind/bind-9.6.0-1/src/bind-9.6.0/lib/isc/unix/socket.c:4525:
bind: Socket operation on non-socket
dig:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
rhubbell wrote:
What is everyone's favorite, full-featured term progam?
I'd like to have something with more features than rxvt.
Have you tried mintty?
Maybe something like konsole.
There aren't a lot of options in the distro, but Cygwin Ports
-To: accordingly.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkmdsrgACgkQpiWmPGlmQSOXzQCfUIB1AV8nbi7/LcYSqa03/oLz
QpYAnRMHYURc/jhRD+n/leKWj5MggQly
=hbcY
-END PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** gtypist-2.8.3-1
This is an update to the latest upstream version.
Yaakov
DOWNLOAD:
=
Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dat Head wrote:
I'm sure there is a good reason that it doesn't (or can't) display
ntfs, or fat32, etc
but was wondering what that reason is? is there another tool that could be
used
for getting that info from cygwin command line?
I looked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cygport has been updated to 0.4.4 for Cygwin 1.5, and 0.9.5 for 1.7,
with similar changes to both:
* SRC_URI accepts .tar.lzo archives.
* postinstall: doesn't strip files which aren't PE-COFF despite their
name. Fixed encodings.dir creation for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Plain C applications will, by default, be linked statically against libgcc as
previously. To link against the shared libgcc DLL, '-shared-libgcc' must be
manually specified on the command-line.
1) What exactly are the pros and
in declaration specifiers
Each of those lines read DWORD Status;.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkm5yiwACgkQpiWmPGlmQSNgbQCgy1/vocPaOtMHJ2RQyOOwuqHc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Larry Hall (Cygwin) wrote:
Since you're not building with Cygwin libs (i.e. you're using the
-mno-cygwin flag), you're really not using Cygwin so the question is
off-topic here. You'll need to inquire the MinGW folks about this
issue. However,
to not allow it.
Thanks for the help, and sorry for the noise.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkm57LkACgkQpiWmPGlmQSOy8QCfXDEMyU05WQT+DUE2thyN7Ibx
i2cAniGCVu5PCzjd+vKBdBLAC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
First, I must say, many thanks for all your hard work on gcc4!
Dave Korn wrote:
No reason that I can think of in general. The only case would be when you
really need to override intra-libstdc++ calls to operators new and delete, in
which case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Can you take this one upstream for us? LT really ought to know about these
two options, they're not even Cygwin-specific at all.
Chuck would probably be a better candidate for that, as he works with
them already.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable
interface.
This is a bugfix and feature enhancement update.
With this release I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave,
Trying gcj-4 with the standard java hello world program:
$ gcj-4 -C Hello.java
gcj-4: error trying to exec 'ecj1': execvp: No such file or directory
$ gcj-4 Hello.java
gcj-4: error trying to exec 'ecj1': execvp: No such file or directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
IIUC, GCJ accepts both java source (.java) and byte code (.class) files and
compiles them to native assembly. In order to compile .java files to
bytecode, it relies on the Eclipse Java compiler front-end.
OK, this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers:
'lzma', 'lzcat', etc,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin/X) wrote:
Charles Wilson wrote:
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Not yet, because I'm not sure that GNU tar supports --xz yet. You could
use '--use-compress-program=xz though.
GNU tar does support --xz as of 1.22. Right now though, we have 1.21,
so this patch will have to wait until
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave,
gcc4 does not provide cc-4, nor does the alternatives script provide cc.
It probably goes without saying that this breaks some (obviously
non-autotoolized) packages that assume cc's presence.
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Ah, thanks for pointing this out. (The packages are of course broken as far
as portability is concerned, as upstream GCC does not anywhere provide a 'cc'
executable; it's presence in the gcc-3 package is caused by the build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Hmm...that autoconfery might work and be blessed upstream (but I need to
add the value to a custom var, not LIBS, because I don't want the
libarchive dll linked with it; just the bsdtar and bsdcpio apps. But
that should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Ah, thanks for pointing this out. (The packages are of course broken as far
as portability is concerned, as upstream GCC does not anywhere provide a 'cc'
executable; it's presence in the gcc-3 package is caused by the build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Perhaps the nice thing to would be supply an auxiliary (optional) package
full of alternative-name helper shell scripts like these. (Apropos of
nothing, I'll point out that SUS may demand cc, c89 and/or c99, but says
nothing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
With 1.7, dlopen() no longer automatically searches /usr/bin by default.
This was definitely not the case with 1.5, but I don't see any mention
of this in the release notes or ChangeLog. Am I missing something here?
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
If a DLL can't be found in a given PATH, Cygwin 1.5.25's function
searching for the DLL (get_full_path_of_dll) just left the filename
alone. The following LoadLibrary call then used the default DLL search
order, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
It might be helpful for a transition period to retain both options.
$ i686-pc-cygwin-gcc -mcygwin - just works
$ i686-pc-cygwin-gcc -mno-cygwin- Spits out a warning
Please, NO! -mno-cygwin needs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
/usr/include/asm/byteorder.h:36: warning: inline function
'__constant_ntohs' declared but never defined
/usr/include/asm/byteorder.h:35: warning: inline function
'__constant_ntohl' declared but never defined
These are first prototyped extern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chuck,
I attached two patches for libtool for your consideration:
1) 2.2-export-all-symbols.patch:
On Cygwin, the --export-all-symbols linker flag is required;
- --export-dynamic has no effect (see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave,
gcc-4 -std=c99 appears to be treating extern inline functions as if they
were marked dllexport, leading to all sorts of linking problems. STC:
$ cat test-ntohs1.c EOF
#include netinet/in.h
extern void foo (uint32_t);
int main(void) {
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
sys/signal.h #includes sys/types.h only #ifdef _POSIX_THREADS, which
is not defined if the -ansi compiler flag is passed. STC:
$ echo '#include signal.h' test-signal.c
$ gcc-4 -ansi -c test-signal.c
In file included from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Thanks for looking in to this; this failure has always bugged me because
I know cygwin supports it, but I've never had the time to track it down.
It has bugged me for quite a while too, as libglade-based packages often
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Dave Korn wrote:
See also http://gcc.gnu.org/ml/gcc/2007-03/threads.html#01088 for
background
and a solution.
You mean like this (attached)?
Oh, but see also:
http://sourceware.org/ml/newlib/2007/msg00326.html
for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Should signal.h perhaps wrap the stuff tagged 'CX' and 'RTS' at
http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html
in #ifndef __STICT_ANSI__ ?
What about those marked 'XSI'?
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Should signal.h perhaps wrap the stuff tagged 'CX' and 'RTS' at
http://www.opengroup.org/onlinepubs/009695399/basedefs/signal.h.html
in #ifndef __STICT_ANSI__ ?
Actually, it looks like someone already thought about that, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin/X) wrote:
Actually, it looks like someone already thought about that, but never
enabled it. There is a commented-out #ifndef __STRICT_ANSI__ which
excludes about half of sys/signal.h. *UNTESTED* patch attached.
That doesn't work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
It's still newlib fodder, though.
http://cygwin.com/ml/cygwin/2009-03/msg00920.html
If the signal.h change gets applied, I change the Cygwin headers
accordingly.
This still needs more testing before I push this up to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dr. Volker Zell,
The current libgs8 package only installs the DLL, but in order to use
it, at least parts of /usr/share/ghostscript/${PN} need to be present as
well, as I found testing libspectre:
GPL Ghostscript 8.63: Can't find initialization
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave,
Building djvulibre-3.5.21 with gcc4, while linking libdjvulibre:
.libs/atomic.o:atomic.cpp:(.text+0x3b): undefined reference to
`___sync_bool_compare_and_swap_4'
.libs/atomic.o:atomic.cpp:(.text+0x65): undefined reference to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Marcel Heing-Becker wrote:
I compiled qemu 0.10.1 and linked it against the latest zlib from the
Cygwin packages and a libsdl compiled by cygwin.
However, when I try to run qemu.exe I receive an error message:
Program entry point crc32 was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
CHANGES SINCE 2.2.7a-10
=
* Removed patches derived from the msvc branch (these are not
ready for prime time)
This version still does not work with automake 1.9:
aclocal: macro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Yaakov (Cygwin/X) wrote:
1) 2.2-export-all-symbols.patch:
2) 2.2-gcc4-libs.patch:
FYI, both of these patches have now been pushed to libtool git master.
Great, thank you.
Yaakov
-BEGIN PGP SIGNATURE-
Version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
It looks like the fact that ncurses' install procedure already gzipped
the real manpages, and named the symlinks with a trailing .gz,
confuses cygport's __postinst procedure a bit. I've worked around it in
the latest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric,
With cygwin-1.7.0-44 and coreutils-7.0-2, install(1) no longer appends
'.exe' to the destination filename. STC:
### in a clean directory
$ echo -e '#include stdio.h\nint main(void) { printf(Hello
World!\\n); }' hello.c
$ echo 'all: hello'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin/X) wrote:
Chuck,
I've been testing this patch[1] for some time within Ports, and it has
solved a lot of the problems I was having with libtool-2.2. Could you
please consider this for inclusion in your gettext package?
[1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Can anyone explain why the attached STC returns an EAFNOSUPPORT?
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
WJFFM. Do you have a IPv6 enabled machine?
Duh, I didn't realize that IPv6 needed to be specifically installed on
Windows[1]. Now it's WJFFM too.
May I suggest that a link to this article be added to the FAQ and/or UG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Well, I'm not too thrilled about automatically upgrading every package
that uses gettext to the latest version -- even those that aren't being
built *for cygwin* itself. Basically, with your patch, if you do an
autoreconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
And it works as designed in your above testcase.
I tested with a filename containing a Euro sign (Unicode 0x20ac), in
HTML speak qqeuro;. Cygwin converted it to qq\016\342\202\254
The strace looks perfectly normal.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
Yes (or you could use the shorter unpack_cmd=tar Jxf). In fact, I had
to apply this to my local cygport in order to build m4-1.4.13-1 from the
upstream .xz tarball. It would be nice to see a new cygport release with
this made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
Note that the binary you got from there is a native windows binary, and it
will probably only understand windows style filenames. Configure may well try
and give it posix style filenames and it might get confused. If you run
1 - 100 of 2688 matches
Mail list logo
