Re: UPDATED: mutt-1.4.1-2
On 2003-11-19T23:20-0600, Gary R. Van Sickle wrote: ) http://home.att.net/~g.r.vansickle/cygwin/mutt/mutt-1.4.1-2.tar.bz2 ) http://home.att.net/~g.r.vansickle/cygwin/mutt/mutt-1.4.1-2-src.tar.bz2 ) http://home.att.net/~g.r.vansickle/cygwin/mutt/setup.hint Uploaded, thanks. -- Daniel Reed <[EMAIL PROTECTED]> http://naim-users.org/nmlorg/ http://naim.n.ml.org/ If nature has made you a giver, your hands are born open, and so is your heart. And though there may be times when your hands are empty, your heart is always full, and you can give things out of that. -- Frances Hodgson Burnett, Novelist
UPDATED: mutt-1.4.1-2
Now with Win9x-onality!: http://home.att.net/~g.r.vansickle/cygwin/mutt/mutt-1.4.1-2.tar.bz2 http://home.att.net/~g.r.vansickle/cygwin/mutt/mutt-1.4.1-2-src.tar.bz2 http://home.att.net/~g.r.vansickle/cygwin/mutt/setup.hint -- Gary R. Van Sickle
RE: UPDATED: mutt-1.4.1-1
[snip] > > Gary, > > > > any timeframe for the -2 version? > > Gary? Are you on vacation or aren't you interested in mutt maintainership > anymore? Vacation, I wish! ;-) No, just ridiculously busy. > It's 4 weeks now since you got the patch from Pierre and the > latest mutt still doesn't work on 9x/Me... > Gimme a sec to build and upload things, I did get his patch in. -- Gary R. Van Sickle
Re: minires-0.95 - a new package ready for review
At 10:18 AM 11/19/2003 +0100, Corinna Vinschen wrote: > >Review: The only problem I found was the naming of the source package. >It's missing the -1 and the source directory within is missing the -1, >too. OK, I think everything is taken care of. The openssh configure might even work OK now (let me know), but not with the static library. Pierre http://mysite.verizon.net/phumblet/setup.hint for minires and minires-devel for minires: http://mysite.verizon.net/phumblet/minires-0.97-1.tar.bz2 http://mysite.verizon.net/phumblet/minires-0.97-1-src.tar.bz2 for minires-devel: http://mysite.verizon.net/phumblet/minires-devel-0.97-1.tar.bz2 (no src) # minires-0.97-1 setup.hint sdesc: "A simple synchronous non caching stub resolver." ldesc: "A simple synchronous non caching stub resolver providing the basic functionality of bind. It interfaces to Windows to find the DNS servers." category: Libs requires: cygwin
Re: New package: suite3270-3.2.20-1
On Tue, 18 Nov 2003, Corinna Vinschen wrote:
> On Mon, Nov 17, 2003 at 02:51:15PM -0800, Peter A. Castro wrote:
> > After getting a successful login I did the following:
> > [EMAIL PROTECTED] ~ $ od -c
> >
> >
> >
> >
> >
> >
> >
> > 000 \0 \n \0 \n \0 \n \0 \n \n \n
> > 012
> >
> > Notice the \0's ? From above, if the crlf option is turned off, the
> > client sends 0x0d,0x00. It appears the telnet daemon is forwarding on
> > the 0x00 as part of the data stream. According to RFC 854, a
> > combination is supposed to be treated as a straight carriage-return, so
> > the daemon is supposed to turn that pair of characters into a single
> > character. You can run c3270 in trace mode ("c3270 -trace "
>
> Hmm, I had a look into telnetd and it actually does conform to RFC 854,
> AFAICS. There's a function called "telrcv()", which apparently cares
> for receiving characters from the client side. There's this stuff in
> the code:
>
> case TS_CR:
> state = TS_DATA;
> /* Strip off \n or \0 after a \r */
> if ((c == 0) || (c == '\n')) {
> break;
> }
> /* FALL THROUGH */
> case TS_DATA:
> [...]
>
> As it turns out, telnetd is operating in so-called "LINEMODE". An
> explanation of linemode is given in telnetd/termstat.c though it's
> not entirely clear to me how it works, admittedly. Linemode seems
> to speed up the connection at least.
The idea behind line-mode is that the client is suppose to do local
editing of the input and only transmit data when enter or some other
flush/sync character is received as input.
The other mode is typically called "character-at-a-time" or "kludge
linemode" in which all characters are sent, real time, and the client
does no editing or buffering.
> Anyway, if linemode is enabled (which is negotiated on server startup),
> telnetd never calls the above code, since a few lines below it turns a
> \r into a \n. When compiling telnetd without -DLINEMODE, that telnetd
> is able to operate with c3270 as expected. It's also able to work
> fine with a Linux and the Cygwin telnet client.
What's interest to me is that a c3270 trace shows that the Cygwin telnetd
is sending "DO LINEMODE" but c3270 is responding with "WONT LINEMODE"
which is supposed to mean that telnetd should not assume LINEMODE
semantics. A normal telnet client (using the "toggle options" command)
flow often shows "DO LINEMODE", intially, but after some additional
options are exchanged, later flows a "DONT LINEMODE". I haven't studied
the BSD code in detail, and so can't really say what's going on.
Alternatively, with other telnetd's (ie: Linux, AIX, Solaris) the telnet
flow is often "DONT LINEMODE" initially. I tried starting the telnetd
with the -k option, but to no avail.
> On the other hand, telnetd on BSD systems is by default also build
> with linemode on! So it's not quite clear to me what to do or if I
> should do anything at all.
I think this is just one of those odd peculiarities of telnet protocol
implementation and not something you need to address. Again, c3270 isn't
really ment to be used as a normal NVT client anyways.
> Corinna
--
Peter A. Castro <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
Re: minires-0.95 - a new package ready for review
Pierre Humblet wrote:
Nicholas Wourms wrote:
I am not sure if this addresses the problem at hand.
There IS and include file with #define foo __foo
but configure runs in a problem when it calls foo() without including
said include file. Thus we would like to have both __foo and foo.
Noo, you have to do it in the library source file, not the header,
that way the symbol is properly generated in the library dll. This is
quite similar to the way cygwin.din maps some symbols to underscore
aliases (or visa-versa).
Yep, but the bind people have already done it in the header.
(not sure why).
I could simply add #ifdef __CYGWIN__ to remove that feature.
But then I will loose binary compatibility between versions.
Is there a perfect solution?
Pierre,
Sorry for the noise, I was wrong. I had a brainfart and forgot that ld
doesn't actually export the #define'd symbols in sourcefiles to dlls.
Ironically, this will compile:
int __foo {
printf("foo\r\n");
return 0;
}
int foo __attribute__ ((alias("__foo"));
and produce a dll exporting both `__foo` and `foo`.
Unfortunately, however, any exe compiled against it will auto-import
_foo and segfault in crt0 when run :-(. Oh well...
Cheers,
Nicholas
Re: minires-0.95 - a new package ready for review
On Wed, Nov 19, 2003 at 04:57:24PM -0500, Pierre A. Humblet wrote: > > > Nicholas Wourms wrote: > > > > > > I am not sure if this addresses the problem at hand. > > > There IS and include file with #define foo __foo > > > but configure runs in a problem when it calls foo() without including > > > said include file. Thus we would like to have both __foo and foo. > > > > Noo, you have to do it in the library source file, not the header, > > that way the symbol is properly generated in the library dll. This is > > quite similar to the way cygwin.din maps some symbols to underscore > > aliases (or visa-versa). > > Yep, but the bind people have already done it in the header. > (not sure why). I guess the whole idea was to allow systems to update to bind8 when there are already bind4 functions in the system libs. It would allow to link against the bind8 libresolv without name clashing. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: minires-0.95 - a new package ready for review
On Wed, Nov 19, 2003 at 04:26:24PM -0500, Pierre A. Humblet wrote: > Corinna Vinschen wrote: > > Does ld on Cygwin support weak symbols? Or is it possible to > > define __imp__res_query additionally to __impres_query? > > Very interesting, thanks. > Apparently ld can do it, either with a DEF file (yuck, dll only?) That would be no problem! Even on Linux, the static libresolv.a lib has the __res_query symbol *only*. The weak reference is only defined in the shared library. If we have a a workaround for the DLL, that would be enough :-) > I had thought about adding a symbol. > One solution to define the additional symbol is to use something > like the newsym script in cygwin. > Btw, could cygwin use weak symbols instead of newsym? Dunno. If weak symbols are not supported, I guess the answer is no. But the idea to use something similar as newsym is cool. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: minires-0.95 - a new package ready for review
Nicholas Wourms wrote: > > > I am not sure if this addresses the problem at hand. > > There IS and include file with #define foo __foo > > but configure runs in a problem when it calls foo() without including > > said include file. Thus we would like to have both __foo and foo. > > Noo, you have to do it in the library source file, not the header, > that way the symbol is properly generated in the library dll. This is > quite similar to the way cygwin.din maps some symbols to underscore > aliases (or visa-versa). Yep, but the bind people have already done it in the header. (not sure why). I could simply add #ifdef __CYGWIN__ to remove that feature. But then I will loose binary compatibility between versions. Is there a perfect solution? Pierre
Re: minires-0.95 - a new package ready for review
Pierre Humblet wrote: Corinna Vinschen wrote: [SNIP] Btw, could cygwin use weak symbols instead of newsym? I suspect this would take quite a bit of doing. In addition to being aliases, weak symbols are also supposed to be "weak". That is, if locally controlled source redefines the symbol, that local symbol is supposed to override the global one. I think this is really only used in situations such as LD_PRELOAD, where one library's functions are supposed to override the system's libraries without having to relink against that other lib. Cheers, Nicholas
Re: minires-0.95 - a new package ready for review
Pierre Humblet wrote:
Nicholas Wourms wrote:
[snip]
However, the kludge I use to get around this is to just do this in the
source file:
#define foo __foo
int
__foo {
}
Or you can use a typedef if your symbol is a struct or similar.
I am not sure if this addresses the problem at hand.
There IS and include file with #define foo __foo
but configure runs in a problem when it calls foo() without including
said include file. Thus we would like to have both __foo and foo.
Noo, you have to do it in the library source file, not the header,
that way the symbol is properly generated in the library dll. This is
quite similar to the way cygwin.din maps some symbols to underscore
aliases (or visa-versa).
Cheers,
Nicholas
Re: minires-0.95 - a new package ready for review
Nicholas Wourms wrote:
>
> [EMAIL PROTECTED] wrote:
> > Does ld on Cygwin support weak symbols? Or is it possible to
> > define __imp__res_query additionally to __impres_query?
>
> No, the current pe bfd doesn't support the weak attribute. I believe
> only elf targets support it at this time (maybe some aout as well?).
There is something in the "Machine Dependent" node of the ld info.
> However, the kludge I use to get around this is to just do this in the
> source file:
>
> #define foo __foo
> int
> __foo {
>
> }
>
> Or you can use a typedef if your symbol is a struct or similar.
I am not sure if this addresses the problem at hand.
There IS and include file with #define foo __foo
but configure runs in a problem when it calls foo() without including
said include file. Thus we would like to have both __foo and foo.
Pierre
Re: minires-0.95 - a new package ready for review
Corinna Vinschen wrote: > > On Wed, Nov 19, 2003 at 01:23:05PM -0500, Pierre A. Humblet wrote: > > Does linux use a recent bind adding underscores (grep res_query resolv.h)? > > Yes. > > > Does OpenSSH's configure behave OK there? If so, why? > > Apparently, on Linux the shared lib libresolve.so defines not only a > text symbol __res_query, it also defines something called a weak > symbol named res_query: > > $ nm libresolv.so | grep res_query > 6640 T __res_query > 6880 T __res_querydomain > 6640 W res_query > 6880 W res_querydomain > > While minres doesn't do the same: > > $ nm /usr/lib/libresolv.dll.a | grep res_query > T ___res_querydomain > I __impres_querydomain > T ___res_query > I __impres_query > > Does ld on Cygwin support weak symbols? Or is it possible to > define __imp__res_query additionally to __impres_query? Very interesting, thanks. Apparently ld can do it, either with a DEF file (yuck, dll only?) or from the source. However in the second case I am afraid the #define will hurt us. I will experiment this evening. I had thought about adding a symbol. One solution to define the additional symbol is to use something like the newsym script in cygwin. Btw, could cygwin use weak symbols instead of newsym? Pierre
Re: minires-0.95 - a new package ready for review
[EMAIL PROTECTED] wrote:
On Wed, Nov 19, 2003 at 01:23:05PM -0500, Pierre A. Humblet wrote:
Does linux use a recent bind adding underscores (grep res_query resolv.h)?
Yes.
Does OpenSSH's configure behave OK there? If so, why?
Apparently, on Linux the shared lib libresolve.so defines not only a
text symbol __res_query, it also defines something called a weak
symbol named res_query:
$ nm libresolv.so | grep res_query
6640 T __res_query
6880 T __res_querydomain
6640 W res_query
6880 W res_querydomain
While minres doesn't do the same:
$ nm /usr/lib/libresolv.dll.a | grep res_query
T ___res_querydomain
I __impres_querydomain
T ___res_query
I __impres_query
Does ld on Cygwin support weak symbols? Or is it possible to
define __imp__res_query additionally to __impres_query?
No, the current pe bfd doesn't support the weak attribute. I believe
only elf targets support it at this time (maybe some aout as well?).
However, the kludge I use to get around this is to just do this in the
source file:
#define foo __foo
int
__foo {
}
Or you can use a typedef if your symbol is a struct or similar.
Cheers,
Nicholas
Re: automated PPL
On 2003-11-19T15:15-0500, Christopher Faylor wrote: ) On Wed, Nov 19, 2003 at 03:13:00PM -0500, Christopher Faylor wrote: ) >Are there ancillary files needed to support app-submit.php? ) I just moved the package there and, AFAICT, it just works without the ) .htaccess file. Apparently PHP is already turned on. I would like to remove the message templates into separate .txt files eventually, and the script does reference setup.ini by hardcoded absolute path, but other than that it is self-contained. It looked like package-maint was created by Elfyn specifically for this purpose, and all that was there was a dummy index.html; so, I just moved app-submit to htdocs/package-maint/index.php . Folks, this means http://cygwin.com/package-maint/ is now setup with the temporary message-drafting script. Anyone with commit to "cygwin" can modify htdocs/package-maint/index.php . -- Daniel Reed <[EMAIL PROTECTED]> http://naim-users.org/nmlorg/ http://naim.n.ml.org/ "True nobility lies not in being superior to another man, but in being superior to one's previous self."
Re: automated PPL
On Wed, 19 Nov 2003, Christopher Faylor wrote: > On Wed, Nov 19, 2003 at 03:13:00PM -0500, Christopher Faylor wrote: > >On Wed, Nov 19, 2003 at 02:40:32PM -0500, Igor Pechtchanski wrote: > >>On Tue, 18 Nov 2003, Christopher Faylor wrote: > >> > >>> On Tue, Nov 18, 2003 at 05:30:56PM -0500, Igor Pechtchanski wrote: > >>> > >>> >Also, what is the policy on scripts outside of the cgi-bin directory > >>> >(e.g., through the cgi-script handler in the .htaccess file)? > >>> > >>> "Don't do it". > >> > >>What about PHP scripts? Can they live in "normal" document directories? > >>Turns out Daniel's form is a PHP script, so I'm planning to move it to > >>htdocs/package-maint/app-submit.php (and will attempt to hide the .php > >>extension through .htaccess) unless people object. > > > >Are there ancillary files needed to support app-submit.php? > > I just moved the package there and, AFAICT, it just works without the > .htaccess file. Apparently PHP is already turned on. > > cgf I meant allowing it to be accessed as "http://cygwin.com/package-maint/app-submit"; (hiding the .php extension). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
Re: minires-0.95 - a new package ready for review
On Wed, Nov 19, 2003 at 01:23:05PM -0500, Pierre A. Humblet wrote: > Does linux use a recent bind adding underscores (grep res_query resolv.h)? Yes. > Does OpenSSH's configure behave OK there? If so, why? Apparently, on Linux the shared lib libresolve.so defines not only a text symbol __res_query, it also defines something called a weak symbol named res_query: $ nm libresolv.so | grep res_query 6640 T __res_query 6880 T __res_querydomain 6640 W res_query 6880 W res_querydomain While minres doesn't do the same: $ nm /usr/lib/libresolv.dll.a | grep res_query T ___res_querydomain I __impres_querydomain T ___res_query I __impres_query Does ld on Cygwin support weak symbols? Or is it possible to define __imp__res_query additionally to __impres_query? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: automated PPL
On Wed, Nov 19, 2003 at 03:13:00PM -0500, Christopher Faylor wrote: >On Wed, Nov 19, 2003 at 02:40:32PM -0500, Igor Pechtchanski wrote: >>On Tue, 18 Nov 2003, Christopher Faylor wrote: >> >>> On Tue, Nov 18, 2003 at 05:30:56PM -0500, Igor Pechtchanski wrote: >>> >>> >Also, what is the policy on scripts outside of the cgi-bin directory >>> >(e.g., through the cgi-script handler in the .htaccess file)? >>> >>> "Don't do it". >> >>What about PHP scripts? Can they live in "normal" document directories? >>Turns out Daniel's form is a PHP script, so I'm planning to move it to >>htdocs/package-maint/app-submit.php (and will attempt to hide the .php >>extension through .htaccess) unless people object. > >Are there ancillary files needed to support app-submit.php? I just moved the package there and, AFAICT, it just works without the .htaccess file. Apparently PHP is already turned on. cgf
Re: automated PPL
On Wed, Nov 19, 2003 at 02:40:32PM -0500, Igor Pechtchanski wrote: >On Tue, 18 Nov 2003, Christopher Faylor wrote: > >> On Tue, Nov 18, 2003 at 05:30:56PM -0500, Igor Pechtchanski wrote: >> >> >Also, what is the policy on scripts outside of the cgi-bin directory >> >(e.g., through the cgi-script handler in the .htaccess file)? >> >> "Don't do it". > >What about PHP scripts? Can they live in "normal" document directories? >Turns out Daniel's form is a PHP script, so I'm planning to move it to >htdocs/package-maint/app-submit.php (and will attempt to hide the .php >extension through .htaccess) unless people object. Are there ancillary files needed to support app-submit.php? cgf
Re: automated PPL
On Tue, 18 Nov 2003, Christopher Faylor wrote: > On Tue, Nov 18, 2003 at 05:30:56PM -0500, Igor Pechtchanski wrote: > > >Also, what is the policy on scripts outside of the cgi-bin directory > >(e.g., through the cgi-script handler in the .htaccess file)? > > "Don't do it". > > cgf What about PHP scripts? Can they live in "normal" document directories? Turns out Daniel's form is a PHP script, so I'm planning to move it to htdocs/package-maint/app-submit.php (and will attempt to hide the .php extension through .htaccess) unless people object. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton
Re: [Review 2 - Good to go] gd: A graphics library for fast image creation
> "Nicholas" == Nicholas Wourms <[EMAIL PROTECTED]> writes: Nicholas> Volker, Nicholas> I think the best way to determine this is whether or not the package Nicholas> installs versioned includes and static/import libs. Also, the naming Nicholas> of the libraries & include dirs is important. In the case of Nicholas> freetype, freetype-1 is libttf whereas freetype2 is libfreetype. Even Nicholas> if it doesn't, it pays to check out the Mandrake/RedHat/Debian Nicholas> packages to see how they are doing it. Sometimes it may be necessary Nicholas> to make a package have co-existing versions, especially in the case of Nicholas> databases where src API's can change, causing some existing sources Nicholas> not to compile/work. Also, it is pretty much a given that most GNOME Nicholas> libraries are going to need to be versioned. The key is to plan ahead Nicholas> now, before you are stuck providing kludges or empty-package Nicholas> work-arounds. It looks like the devel package is not versioned. I uploaded my packages again. See below for download script. Nicholas> Cheers, Nicholas> Nicholas Ciao Volker -- cut here - #!/bin/bash mkdir -p gd gd/libgd2 gd/libgd-devel cd gd wget http://de.geocities.com/vzell1/cygwin/gd.hint.zip mv gd.hint.zip setup.hint wget http://de.geocities.com/vzell1/cygwin/libgd2.hint.zip mv libgd2.hint.zip libgd2/setup.hint wget http://de.geocities.com/vzell1/cygwin/libgd-devel.hint.zip mv libgd-devel.hint.zip libgd-devel/setup.hint wget http://de.geocities.com/vzell1/cygwin/gd-2.0.15-1-src.tar.zip mv gd-2.0.15-1-src.tar.zip gd-2.0.15-1-src.tar.bz2 wget http://de.geocities.com/vzell1/cygwin/gd-2.0.15-1.tar.zip mv gd-2.0.15-1.tar.zip gd-2.0.15-1.tar.bz2 wget http://de.geocities.com/vzell1/cygwin/libgd-devel-2.0.15-1.tar.zip mv libgd-devel-2.0.15-1.tar.zip libgd-devel/libgd-devel-2.0.15-1.tar.bz2 wget http://de.geocities.com/vzell1/cygwin/libgd2-2.0.15-1.tar.zip mv libgd2-2.0.15-1.tar.zip libgd2/libgd2-2.0.15-1.tar.bz2 -- cut here -
Problem with apache+Win2k+SP4 [my httpd.conf]
sorry.
I forget to attach my httpd.conf.
-
ServerType standalone
ServerRoot "/usr/local/apache"
PidFile /usr/local/apache/logs/httpd.pid
ScoreBoardFile /usr/local/apache/logs/httpd.scoreboard
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
MinSpareServers 5
MaxSpareServers 10
StartServers 5
MaxClients 150
MaxRequestsPerChild 0
Port 80
User sezal
Group #-1
ServerAdmin [EMAIL PROTECTED]
DocumentRoot "/usr/local/apache/htdocs"
ServerName localhost
Options FollowSymLinks
AllowOverride None
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
Allow from all
UserDir public_html
DirectoryIndex index.html
AccessFileName .htaccess
Order allow,deny
Deny from all
Satisfy All
UseCanonicalName On
TypesConfig /usr/local/apache/conf/mime.types
DefaultType text/plain
MIMEMagicFile /usr/local/apache/conf/magic
HostnameLookups Off
ErrorLog /usr/local/apache/logs/error_log
LogLevel warn
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
CustomLog /usr/local/apache/logs/access_log common
ServerSignature On
Alias /icons/ "/usr/local/apache/icons/"
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
Alias /manual/ "/usr/local/apache/htdocs/manual/"
Options Indexes FollowSymlinks MultiViews
AllowOverride None
Order allow,deny
Allow from all
ScriptAlias /cgi-bin/ "/usr/local/apache/cgi-bin/"
AllowOverride None
Options None
Order allow,deny
Allow from all
IndexOptions FancyIndexing
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*
AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core
AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^
DefaultIcon /icons/unknown.gif
ReadmeName README
HeaderName HEADER
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
AddEncoding x-compress Z
AddEncoding x-gzip gz tgz
AddLanguage da .dk
AddLanguage nl .nl
AddLanguage en .en
AddLanguage et .ee
AddLanguage fr .fr
AddLanguage de .de
AddLanguage el .el
AddLanguage he .he
AddCharset ISO-8859-8 .iso8859-8
AddLanguage it .it
AddLanguage ja .ja
AddCharset ISO-2022-JP .jis
AddLanguage kr .kr
AddCharset ISO-2022-KR .iso-kr
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddCharset ISO-8859-2 .iso-pl
AddLanguage pt .pt
AddLanguage pt-br .pt-br
AddLanguage ltz .lu
AddLanguage ca .ca
AddLanguage es .es
AddLanguage sv .sv
AddLanguage cz .cz
AddLanguage ru .ru
AddLanguage zh-tw .tw
AddLanguage tw .tw
AddCharset Big5 .Big5.big5
AddCharset WINDOWS-1251 .cp-1251
AddCharset CP866.cp866
AddCharset ISO-8859-5 .iso-ru
AddCharset KOI8-R .koi8-r
AddCharset UCS-2.ucs2
AddCharset UCS-4.ucs4
AddCharset UTF-8.utf8
LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ru ltz ca es sv
tw
AddType application/x-tar .tgz
AddType image/x-icon .ico
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0
Re: minires-0.95 - a new package ready for review
Corinna Vinschen wrote: > > On Wed, Nov 19, 2003 at 09:20:40AM -0500, Pierre A. Humblet wrote: > > Corinna Vinschen wrote: > > > Oh, btw., why does minires export the symbols with leading underscores? > > > > Because minires is using include files from bind, and bind does it for > > reasons I don't > > know (older binds don't do it). There is no switch in the .h file to avoid > > that. The > > I see. Perhaps there's a spcific way to workaround that issue? > My example was really just an example. OpenSSH's configure performs > a somewhat more complex test for libresolv, which nevertheless fails. As pointed out in http://www.openldap.org/lists/openldap-bugs/199907/msg00021.html the basic problem is that configure builds a program that calls res_query without including resolv.h as it should. Some googling led to another approach (grep for res_query) http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/gnupg/configure.ac?rev=1.73 Does linux use a recent bind adding underscores (grep res_query resolv.h)? Does OpenSSH's configure behave OK there? If so, why? > > Advice welcome. > > Yeah, me too ;-) The issue was discussed was some of your redhat colleagues. http://sources.redhat.com/ml/libc-hacker/2000-07/msg00224.html http://sources.redhat.com/ml/libc-hacker/2000-07/msg00090.html Pierre
Problem with apache+Win2k+SP4
Hello. I'm using Win2k(RU) + SP4 + cygwin dll 1.5.5-1. After installing SP4 my apache-1.3.24-5 from cygwin distributive works not properly: after starting, restarting, stopping CPU usage on my Pentium-III-450 sometimes rise up to 100%. So I have no choice -- i need to restart my Win2k. Problem is not in my computer. (I have this problem on another computer with Win2k+SP4). I've tried to recompile apache (used apache-1.3.27) --- absolutely the same bug. My httpd.conf attached. How can I fix this bug ? Best regards, Sergiy Zuban
Re: minires-0.95 - a new package ready for review
On Wed, Nov 19, 2003 at 09:20:40AM -0500, Pierre A. Humblet wrote: > Corinna Vinschen wrote: > > Oh, btw., why does minires export the symbols with leading underscores? > > Because minires is using include files from bind, and bind does it for > reasons I don't > know (older binds don't do it). There is no switch in the .h file to avoid > that. The I see. Perhaps there's a spcific way to workaround that issue? My example was really just an example. OpenSSH's configure performs a somewhat more complex test for libresolv, which nevertheless fails. > Advice welcome. Yeah, me too ;-) > I will fix the -1 in the source package. Also should the package be renamed > libminires? Nah, that's really not necessary. Do as you like. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: [Review 2 - Good to go] gd: A graphics library for fast image creation
[EMAIL PROTECTED] wrote: "Gareth" == Gareth Pearce <[EMAIL PROTECTED]> writes: >> Hmm... just noticed that you have libgd2 and libgd2-devel... I was under >> the impression that you should stick the DLL version in the libgd >> package name, which you did, but I thought that the DLL version number >> was *not* included in the -devel package name. >> >> It seems to me that the devel package should be called: >> >> libgd-devel >> >> >> Anyone care to comment on this? Gareth> It would be nice to say that versioned devels are never necessary, but Gareth> unless the internals of the package are designed so as to be able to coexist Gareth> with future version devels (like libgd2 would be), there isn't any point Gareth> versioning them, and hence should not be so. Volker, I think the best way to determine this is whether or not the package installs versioned includes and static/import libs. Also, the naming of the libraries & include dirs is important. In the case of freetype, freetype-1 is libttf whereas freetype2 is libfreetype. Even if it doesn't, it pays to check out the Mandrake/RedHat/Debian packages to see how they are doing it. Sometimes it may be necessary to make a package have co-existing versions, especially in the case of databases where src API's can change, causing some existing sources not to compile/work. Also, it is pretty much a given that most GNOME libraries are going to need to be versioned. The key is to plan ahead now, before you are stuck providing kludges or empty-package work-arounds. Cheers, Nicholas
Re: minires-0.95 - a new package ready for review
Corinna Vinschen wrote: > On Wed, Nov 19, 2003 at 10:18:04AM +0100, Corinna Vinschen wrote: > > On Tue, Nov 18, 2003 at 09:43:45PM -0500, Pierre A. Humblet wrote: > > > Review? Vote? > > > > Review: The only problem I found was the naming of the source package. > > It's missing the -1 and the source directory within is missing the -1, > > too. > > > > Vote: +3 from me. > > Oh, btw., why does minires export the symbols with leading underscores? > This results in a problem with configure, e. g.: > > AC_CHECK_FUNC(res_query, > [], [ AC_CHECK_LIB(resolv, res_query, LIBS="$LIBS -lresolv") ] > ) > > won't work. Because minires is using include files from bind, and bind does it for reasons I don't know (older binds don't do it). There is no switch in the .h file to avoid that. The issue has already been pointed out to me and I did some research. It has come up elsewhere too, e.g. http://www.openldap.org/lists/openldap-bugs/199907/msg00021.html Given that bind does it, I am surprised that modern configures still choke, but it's an area I know little about. Advice welcome. I will fix the -1 in the source package. Also should the package be renamed libminires? Pierre
Re: minires-0.95 - a new package ready for review
On Wed, Nov 19, 2003 at 10:18:04AM +0100, Corinna Vinschen wrote: > On Tue, Nov 18, 2003 at 09:43:45PM -0500, Pierre A. Humblet wrote: > > Review? Vote? > > Review: The only problem I found was the naming of the source package. > It's missing the -1 and the source directory within is missing the -1, > too. > > Vote: +3 from me. Oh, btw., why does minires export the symbols with leading underscores? This results in a problem with configure, e. g.: AC_CHECK_FUNC(res_query, [], [ AC_CHECK_LIB(resolv, res_query, LIBS="$LIBS -lresolv") ] ) won't work. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: UPDATED: mutt-1.4.1-1
On Sun, Nov 09, 2003 at 10:05:23AM +0100, Corinna Vinschen wrote: > On Wed, Oct 22, 2003 at 02:13:43PM -0500, Gary R. Van Sickle wrote: > > > The latest mutt (has it been announced?) > > > > Not yet, no. I have to apologize, I've been busy getting my brother married. I > > shall do so post-haste. > > > > > does not seems to > > > contain the patch discussed in > > > > > > http://www.cygwin.com/ml/cygwin/2003-02/msg01148.html > > > http://cygwin.com/ml/cygwin/2002-11/msg00628.html > > > > > > and repeated below. Consequently it doesn't work on Win9x/ME. > > > > > > > Yeah, sorry. I actually looked for and didn't find the patch, and it wasn't > > immediately obvious to me how to apply your explanation of how exim worked to > > mutt, nor could I test the results since I currently have no access to 9x/ME. > > I'll be releasing a -2 shortly and I'll get this in it. Thanks for bringing > > this to my attention Pierre (and for sending the patch upstream). > > Gary, > > any timeframe for the -2 version? Gary? Are you on vacation or aren't you interested in mutt maintainership anymore? It's 4 weeks now since you got the patch from Pierre and the latest mutt still doesn't work on 9x/Me... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: minires-0.95 - a new package ready for review
On Tue, Nov 18, 2003 at 09:43:45PM -0500, Pierre A. Humblet wrote: > At 04:35 PM 11/18/2003 +0100, Corinna Vinschen wrote: > > Unfortunately, with the given GPL license it wouldn't > >be possible to be put into newlib nor into Cygwin directly. Did we > >straighten that out already? I don't remember... > > The GPL licence was never discussed. I don't know what newlib wants. I don't quite understand how the licensing in newlib works, actually. It seems ok for newlib to mix various open licenses, like LGPL, BSD and such. We should ask on the newlib list since GPL could really be a problem. > No news from Elfyn, so I have packaged it. > > minires-0.97-1 contains only the dll, the LICENCE and the README > minires-devel-0.97-1 contains the .h and .a, as well as a postinstall to > link libresolv.a (if it doesn't exist) to libminires.dll.a, but no > LICENCE nor README (they would be identical to the previous ones). > The two source packages are identical. Do we need two ? No, we can silently drop minires-devel-0.97-src.tar.bz2. > setup.hint should be used for both minires-0.97-1 and minires-devel-0.97-1 > I put it in the Libs category. Anything else, e.g. System? Libs is fine. > Review? Vote? Review: The only problem I found was the naming of the source package. It's missing the -1 and the source directory within is missing the -1, too. Vote: +3 from me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: [Review 2 - Good to go] gd: A graphics library for fast image creation
> "Gareth" == Gareth Pearce <[EMAIL PROTECTED]> writes: >> Hmm... just noticed that you have libgd2 and libgd2-devel... I was under >> the impression that you should stick the DLL version in the libgd >> package name, which you did, but I thought that the DLL version number >> was *not* included in the -devel package name. >> >> It seems to me that the devel package should be called: >> >> libgd-devel >> >> >> Anyone care to comment on this? Gareth> It would be nice to say that versioned devels are never necessary, but Gareth> unless the internals of the package are designed so as to be able to coexist Gareth> with future version devels (like libgd2 would be), there isn't any point Gareth> versioning them, and hence should not be so. I'll change it to not include the version number. Ciao Volker
RE: [Review 2 - Good to go] gd: A graphics library for fast image creation
> Hmm... just noticed that you have libgd2 and libgd2-devel... I was under > the impression that you should stick the DLL version in the libgd > package name, which you did, but I thought that the DLL version number > was *not* included in the -devel package name. > > It seems to me that the devel package should be called: > > libgd-devel > > > Anyone care to comment on this? It would be nice to say that versioned devels are never necessary, but unless the internals of the package are designed so as to be able to coexist with future version devels (like libgd2 would be), there isn't any point versioning them, and hence should not be so. > > > Harold
