Dave Korn wrote:
>
> This adds all the outstanding BLODA entries I am aware of to the list in the
> FAQ. OK for HEAD?
>
> winsup/doc/ChangeLog
>
> * faq-using.xml (faq.using.bloda): Update with new entries.
Sorry, should have mentioned: tested by rebuilding in the build
i686-pc-cyg
This adds all the outstanding BLODA entries I am aware of to the list in the
FAQ. OK for HEAD?
winsup/doc/ChangeLog
* faq-using.xml (faq.using.bloda): Update with new entries.
cheers,
DaveK
Index: winsup/doc/faq-using.xml
=
-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 \nint main(void) { printf("Hello
World!\\n"); }' > hello.c
$ echo 'all: hello' > Ma
-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
[same version, for both cygwin-1.5 and cygwin-1.7]
This version requires the test: version of csih (0.1.9-2). The iu-config
script of this package uses some of the new features of that csih
package, to support "unattended" installation. See below.
This package also includes the fix for the proble
Further testing exposed a few bugs with the new features; corrected in
this release. Still marked test: though. The new (test) inetutils-1.5-6
uses some of the new features, such as unattended installation support.
More on that in the accompanying [Avail for test] announcement for
inetutils.
--
-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-
Vers
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.
--
Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Document
Nuzhna Pomoshch wrote:
> --- On Sat, 3/14/09, Dave Korn wrote:
>
>> Nuzhna, you didn't mention what the two other apps are,
>> but VPN software has been known to cause problems in the
>> past. What is the other stuff you have installed?
>
> The only two apps on the machine are Bloomberg and Redi
On 2009-03-29 23:51Z, Nuzhna Pomoshch wrote:
>
> I have been fighting this for another two weeks with no
> progress whatsoever. Does any documentation exist that
> describes the least painful way to reinstall everything
> (specifically including what I should back up)? I also
> would place a high
Yaakov (Cygwin/X) wrote:
> This version still does not work with automake < 1.9:
>
> aclocal: macro `_LT_PREPARE_SED_QUOTE_VARS' required but not defined
> aclocal: macro `_LT_PROG_ECHO_BACKSLASH' required but not defined
> autoreconf-2.63: aclocal failed with exit status: 1
Thanks for the repor
--- On Sat, 3/14/09, Dave Korn wrote:
> Nuzhna, you didn't mention what the two other apps are,
> but VPN software has been known to cause problems in the
> past. What is the other stuff you have installed?
The only two apps on the machine are Bloomberg and Redi.
> Also, please grab a set of
I think it is great for someone to add "html" file support to the man
command. As indicated in
http://sourceware.org/ml/cygwin/2009-03/msg00300.html , the man command
in 1.7 apparently does not work for html files. If this was answered,
please excuse me being hospitalized for more than a week
-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 `_LT_
After the installation of texinfo-4.13-2 I see that in root dir (/), and
in the tarball, that there is a directory called "netrel":
---
$ ls -R /netrel
/netrel:
inst
/netrel/inst:
texinfo-4.13-2
/netrel/inst/texinfo-4.13-2:
usr
/netrel/inst/texinfo-4
-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
Hi there,
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 not found in library Cygwin1.dll
(translated from German)
I'm confused a
Dave Korn:
> Andy Koppe wrote:
>> According to this post on the gcc mailing list a few years back, gcc's
>> -mwindows option should imply --Wl,subsystem,windows:
>>
>> http://gcc.gnu.org/ml/gcc-help/2004-01/msg00225.html
>
> Yep, it still does.
Ah, you're right. I seem to have confused myself ab
Andy Koppe wrote:
> According to this post on the gcc mailing list a few years back, gcc's
> -mwindows option should imply --Wl,subsystem,windows:
>
> http://gcc.gnu.org/ml/gcc-help/2004-01/msg00225.html
Yep, it still does.
> I find, however, that I'm getting different behaviour when passing
According to this post on the gcc mailing list a few years back, gcc's
-mwindows option should imply --Wl,subsystem,windows:
http://gcc.gnu.org/ml/gcc-help/2004-01/msg00225.html
I find, however, that I'm getting different behaviour when passing
--Wl,subsystem,windows explicitly. (Without it, stdo
* wishi (Sat, 28 Mar 2009 14:34:24 +0100)
> Thorsten Kampe schrieb:
> > * wishi (Sat, 28 Mar 2009 12:44:57 +0100)
> >> After the initial setup on a Windows XP SP III Cygwin's setup.exe
> >> creates a Read-Only folder. That normally isn't that big of a
> >> problem, but screen needs \tmp.
> >>
> >>
> Well, I guess the question is, what's the minimum level of CPU we want to
> support, and I can configure the next version --with-arch that level, and as
> long as it's >=486 we'll be ok. I think the question is mainly "686, or is
> there any reason to have 586 as the minimum supported CPU"?
Wi
Yaakov (Cygwin/X) wrote:
> 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
> `___sync_add_and_fetch_4'
>
> Some
23 matches
Mail list logo
