libmemcache/pmk stuff

[Tomaž Borštnar]

Joerg Sonnenberger wrote:
On Tue, Apr 12, 2005 at 11:15:11PM +0200, Tomaž Borštnar wrote:

* Checking header [include_socket]
       Use C language with CC compiler.
       Store compiler flags in 'CFLAGS'.
       Found function 'socket' in 'sys/socket.h' : no.
Error : failed to find function 'socket'.


I guess they don't include sys/types.h first as it is common convention.
Stand-alone system headers is still on my list.
Joerg
This is what I got from pmk people:

Damien Couderc wrote:
> Here is what i got with the sources that are in the current tree :
>
> PMK version 0.9.3-s2
>
> Loaded 44 predefinined variables.
> Loaded 0 overridden switches.
> Loaded 0 overridden variables.
> Total : 62 variables.
>
> Parsing '/home/mips/work/projects/premake/tst/pmkfile'
>
> Processing commands :
>
> * Parsing settings
>         Setting global language :
>                 Set to 'C'.
>
> * Checking header [header_stdbool_h]
>         Use C language with /usr/bin/cc compiler.
>         Store compiler flags in 'CFLAGS'.
>         Found header 'sys/socket.h' : yes.
>         Found function 'socket' : yes.
>
>
> With the following pmkfile :
>
> # set target file
> SETTINGS {
> 	LANG="C"
> }
>
> # checking stdbool.h
> CHECK_HEADER(header_stdbool_h) {
> 	REQUIRED = FALSE
> 	NAME = "sys/socket.h"
> 	SUBHDR = ("sys/types.h")
> 	FUNCTION = ("socket")
> }
>
>
> And the content of the build log is :
>
> Generated source file:
> /* dependency headers */
> #include <sys/types.h>
> /* main header to test */
> #include <sys/socket.h>
> /* main procedure */
> int main() {
> /* check procedure */
> void (*pmk_funcp)() = (void *) socket;
> return(0);
> }
>
>
> As you can see the header dependencies are incorporated in the test.
> I think that in the near future i will try first to check the header
> without dependencies and retry with it on failure.
>
> BTW i've not been able to get an account on a DragonFlyBSD box, could
> you provide me some informations about the system so i can populate
> the pmkcomp.dat file with a DFBSD record (and then say HI to shared
> lib support) ?
>
> For example the FreeBSD record is the following:
> ADD_SYSTEM {
> 	NAME = "FreeBSD"
> 	SL_EXT = ".so"
> 	SL_VERSION = "$SL_MAJOR.$SL_MINOR"
> 	SL_LIBNAME = "lib$SL_NAME$SL_EXT"
> 	SL_LIBNAME_VMAJ = "$SL_LIBNAME.$SL_MAJOR"
> 	SL_LIBNAME_VFULL = "$SL_LIBNAME.$SL_VERSION"
> }
>
> (it needs to be updated as i've heard that there was no longer micro
> version in FreeBSD)
>
> Have fun,
> Damien
Can somebody help me provide them with an answer?

Thanks.

Tomaž