This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: new package: lighttpd

Hello Jan,

>> With some information how to install as Cygwin service via cygrunsrv.

> Can you gimme some links on how to set it up ?

/usr/share/doc/Cygwin/cygrunsrv.README && cygrunsrv --help?

Should look like this
cygrunsrv --install lighttpd --path /usr/sbin/lighttpd --args "-D"
you may add more options like --disp "CYGWIN lighttpd"


>> Why don't you include openssl support (default no)?

> Will be added.
>> What about the other configure flags:
>>   --enable-mod-localizer  Turn on mod_localizer
>>   --with-ldap             enable LDAP support
>>   --with-attr             enable extended attribute support
>> ?

> --with-attr is linux only. ldap and localizer would be possible.



>> Wouldn't make it more sense to use --disable-static --enable-shared
>> instead of having all those static module files which are of no use?

> The package is build that way. If someone has more insight then me in
> the way cygwin builds modules I'm happy to add the changes. 

ZThe static archives '.a' are really useless in this case and the
import libraries '.dll.a' may be removed after installation unless you
need them to link other modules against them.

>> Also the import libraries for the modules could be removed from the
>> binary tarball, and if you are not using dlopen, the .la files fr the
>> modules can be removed too.

> *.a and *.la wont be packaged in the next round. 

It depends on the way you're loading the modules, if it is done via
libtool, the .la files are needed, e.g. Perl doesn't need them to load

>> I cannot rebuild from source:
>> rm -f configparser.h
>> ../src/lemon -q /home/gerrit/lighttpd-1.2.8/src/configparser.y
>> /home/gerrit/lighttpd-1.2.8/src/lempar.c
>> if sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H
>> -DLIBRARY_DIR="\"/usr/lib\"" -I. -I/home/gerrit/lighttpd-1.2.8/src
>> -D_REENTRANT  -O2 -Wall -W -Wshadow -pedantic -MT config.lo -MD -MP
>> -MF ".deps/config.Tpo" -c -o config.lo config.c; \
>> then mv -f ".deps/config.Tpo" ".deps/config.Plo"; else rm -f ".deps/config.Tpo"; exit 1; fi
>>  gcc -DHAVE_CONFIG_H -DLIBRARY_DIR=\"/usr/lib\" -I.
>> -I/home/gerrit/lighttpd-1.2.8/src -I.. -D_FILE_OFFSET_BITS=64
>> -Wshadow -pedantic -MT config.lo -MD -MP -MF .deps/config.Tpo -c
>> config.c  -DPIC -o .libs/config.o
>> gcc: config.c: No such file or directory
>> gcc: no input files
>> make[2]: *** [config.lo] Error 1
>> make[2]: Leaving directory `/home/gerrit/lighttpd-1.2.8/.build/src'
>> make[1]: *** [all-recursive] Error 1
>> make[1]: Leaving directory `/home/gerrit/lighttpd-1.2.8/.build'
>> make: *** [all] Error 2

> This is a tricky one as if you start the script again with

> $ build

> it will build the package take the right path for config.c and won't try
> to search for it in the build-directory.
This is probably taken from the missing README?  This breaks the
generic-build-script, it will terminate with error and using option
'all' is impossible.  You may change the build-script to your needs,
it is just a generic template which doesn't fit in this case, i.e.
call make twice and catch the error in the first round gracefully.

>> It seems you're the upstream maintainer as well, wouldn't it make more
>> sense to release a new tarball with the changes included?

> Yes the changes will be included in the next release. The original
> 1.2.8-tarball will never change after it has been released. No, this
> changes will be included in the upcoming 1.3.0 release.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]