>
> Hi,
>
> [EMAIL PROTECTED] wrote:
>>> To use the internal curl, just run "ccmake .." in the build
>>> directory, and change the HAVE_CURL_INTERNAL variable to ON, or (as
>>> you say) call cmake with the argument "cmake ..
>>> -DHAVE_CURL_INTERNAL=ON"
>>
>>
>> Hm, I feel about stupid about this. It didn't work for me.
>>
>> "HAVE_CURL_INTERNAL="ON" ccmake .." in the build directory presented
>> me with an ascii-gui program showing all kinds of variables; I saw
>> nothing reading *CURL*. The build following leaving that "gui" copied
>> a lot of stuff, also a manual "cmake .." did only the same, it ends
>> with..:
>
> When I run ccmake .. I get a list of variables - there are many of
> them, more than will fit in one page.
>
> I can search for CURL by typing /CURL<return> and I see that there is
> CURL_INTERNAL, set to 1 (I'm using Dapper, so my curl isn't recent
> enough in the system).
>
> So you should run cmake like this (excuse me, I didn't check earlier):
> $ cmake .. -DCURL_INTERNAL=ON
Ok, right. I found CURL in the list now too (my fault was that I looked
for "HAVE_.."), changed it to ON, pressed 'c', then 'g' and cmake appeared
to do something useful. However, when I exited and retried to compile
("ccmake .." or "ccmake .. _DCURL..") output was different: I got a new
configure run (checking for blah..), then the files being copied thing
(again), no new libs or executables were created. D'oh. :(
>> Ok, you're right of course. I didn't notice that. When I tried first,
>> the automatic timeout hit me so it appeared I couldn't create tickets
>> although I was logged in. trying again, I ran into trouble: the
>> timeout is really short so I was logged out again. There really is not
>> enough time writing a halfway decent report with that timeout. Also,
>> logging in after getting the error loses all info from the ticket,
>> this is really annoying. Please consider increasing the timeout (or
>> rather, why not keep people logged in once they're authenticated?).
>
> Weird - I stay logged in all day, without necessarily doing anything in
> particular. Are you sure you have session cookies turned on? Do you
> have any problems with other tracs?
Ok, sorry for flaming then :)
I checked my cookie settings, they're set to be kept 'until they expire'
from the site and the session cookie for trac is set to expire in one and
three months or something like that. So no idea what exactly is wrong,
maybe a firefox bug. Muah..
I have headaches, I'll go to get dinner, maybe things magically change in
the meantime ;)
Sebastian
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
