Mailing List Archive

For reference, compiling on OSX
I was talking to Dag Henning about compiling varnish on OSX earlier today at
the press conference. Just wanted to paste the current show stopper here for
reference:

if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -include
config.h-O2 -pipe -MT varnishd-cache_acceptor.o -MD -MP -MF
".deps/varnishd-cache_acceptor.Tpo" -c -o varnishd-cache_acceptor.o `test -f
'cache_acceptor.c' || echo './'`cache_acceptor.c; \
then mv -f ".deps/varnishd-cache_acceptor.Tpo"
".deps/varnishd-cache_acceptor.Po"; else rm -f
".deps/varnishd-cache_acceptor.Tpo"; exit 1; fi
cache_acceptor.c: In function 'vca_acct':
cache_acceptor.c:170: error: 'CLOCK_REALTIME' undeclared (first use in this
function)
cache_acceptor.c:170: error: (Each undeclared identifier is reported only
once
cache_acceptor.c:170: error: for each function it appears in.)
make[3]: *** [varnishd-cache_acceptor.o] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Dag Henning says this is because OSX does not have a clock_gettime system
call, and that gettimeofday aint monotonous enough or something like that...
:-) I will try to dig more into the issue.

Other first impressions from testing out Varnish:

We need more docs. Specially on making VCL policies.

varnish does not seem to set X-Forwarded-For ? (Maybe it's not common to do
it, but it's how my framework deals with reverse proxies)

--
With regards
Marcus Ramberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.linpro.no/pipermail/varnish-dev/attachments/20060920/6dbc765e/attachment.htm
For reference, compiling on OSX [ In reply to ]
I was talking to Dag Henning about compiling varnish on OSX earlier today at
the press conference. Just wanted to paste the current show stopper here for
reference:

if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../include -include
config.h-O2 -pipe -MT varnishd-cache_acceptor.o -MD -MP -MF
".deps/varnishd-cache_acceptor.Tpo" -c -o varnishd-cache_acceptor.o `test -f
'cache_acceptor.c' || echo './'`cache_acceptor.c; \
then mv -f ".deps/varnishd-cache_acceptor.Tpo"
".deps/varnishd-cache_acceptor.Po"; else rm -f
".deps/varnishd-cache_acceptor.Tpo"; exit 1; fi
cache_acceptor.c: In function 'vca_acct':
cache_acceptor.c:170: error: 'CLOCK_REALTIME' undeclared (first use in this
function)
cache_acceptor.c:170: error: (Each undeclared identifier is reported only
once
cache_acceptor.c:170: error: for each function it appears in.)
make[3]: *** [varnishd-cache_acceptor.o] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Dag Henning says this is because OSX does not have a clock_gettime system
call, and that gettimeofday aint monotonous enough or something like that...
:-) I will try to dig more into the issue.

Other first impressions from testing out Varnish:

We need more docs. Specially on making VCL policies.

varnish does not seem to set X-Forwarded-For ? (Maybe it's not common to do
it, but it's how my framework deals with reverse proxies)

--
With regards
Marcus Ramberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://projects.linpro.no/pipermail/varnish-dev/attachments/20060920/6dbc765e/attachment-0001.htm
For reference, compiling on OSX [ In reply to ]
In message <825a03c0609201347k1520a771h8c940c0704f163a9 at mail.gmail.com>, "Marcu
s Ramberg" writes:

>cache_acceptor.c:170: error: 'CLOCK_REALTIME' undeclared (first use in this
>function)
>
>Dag Henning says this is because OSX does not have a clock_gettime system
>call, and that gettimeofday aint monotonous enough or something like that...
>:-) I will try to dig more into the issue.

gettimeofday() will do. Just add a compat function that emulates
clock_gettime() with a gettimeofday() call, and then preferably
send an email to Jordan K. Hubbard at Apple and tell them to get
their act together.

>varnish does not seem to set X-Forwarded-For ? (Maybe it's not common to do
>it, but it's how my framework deals with reverse proxies)

I didn't know how widespread and widely used the X-Forwarded-For:
header was, so I didn't put it in initially. If there is a desire,
we can make it possible to do so from VCL.

Poul-Henning

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
For reference, compiling on OSX [ In reply to ]
In message <825a03c0609201347k1520a771h8c940c0704f163a9 at mail.gmail.com>, "Marcu
s Ramberg" writes:

>cache_acceptor.c:170: error: 'CLOCK_REALTIME' undeclared (first use in this
>function)
>
>Dag Henning says this is because OSX does not have a clock_gettime system
>call, and that gettimeofday aint monotonous enough or something like that...
>:-) I will try to dig more into the issue.

gettimeofday() will do. Just add a compat function that emulates
clock_gettime() with a gettimeofday() call, and then preferably
send an email to Jordan K. Hubbard at Apple and tell them to get
their act together.

>varnish does not seem to set X-Forwarded-For ? (Maybe it's not common to do
>it, but it's how my framework deals with reverse proxies)

I didn't know how widespread and widely used the X-Forwarded-For:
header was, so I didn't put it in initially. If there is a desire,
we can make it possible to do so from VCL.

Poul-Henning

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
For reference, compiling on OSX [ In reply to ]
> In message <825a03c0609201347k1520a771h8c940c0704f163a9 at mail.gmail.com>,
> "Marcu
> s Ramberg" writes:
>
>>cache_acceptor.c:170: error: 'CLOCK_REALTIME' undeclared (first use in
>> this
>>function)
>>
>>Dag Henning says this is because OSX does not have a clock_gettime system
>>call, and that gettimeofday aint monotonous enough or something like
>> that...
>>:-) I will try to dig more into the issue.
>
> gettimeofday() will do. Just add a compat function that emulates
> clock_gettime() with a gettimeofday() call, and then preferably
> send an email to Jordan K. Hubbard at Apple and tell them to get
> their act together.

For the non-programmers out there, this should maybe be done in the
buildscripts?

Anders Berg
For reference, compiling on OSX [ In reply to ]
> In message <825a03c0609201347k1520a771h8c940c0704f163a9 at mail.gmail.com>,
> "Marcu
> s Ramberg" writes:
>
>>cache_acceptor.c:170: error: 'CLOCK_REALTIME' undeclared (first use in
>> this
>>function)
>>
>>Dag Henning says this is because OSX does not have a clock_gettime system
>>call, and that gettimeofday aint monotonous enough or something like
>> that...
>>:-) I will try to dig more into the issue.
>
> gettimeofday() will do. Just add a compat function that emulates
> clock_gettime() with a gettimeofday() call, and then preferably
> send an email to Jordan K. Hubbard at Apple and tell them to get
> their act together.

For the non-programmers out there, this should maybe be done in the
buildscripts?

Anders Berg