Stefan Sperling wrote:
> On Sat, Apr 25, 2009 at 03:04:04AM +0200, Arfrever Frehtes Taifersar Arahesis wrote:
>> 2009-04-25 02:02:55 Neels Janosch Hofmeyr napisal(a):
>>> Sorry Senthil, my build was wrong, as stsp kindly pointed out to me.
>>>
>>> I still had a --disable-shared in the builds of some deps that I forgot to
>>> remove, so Subversion automatically switched to --disable-shared mode (there
>>> was no error that --with-gnome-keyring can't work like that).
>> I can't reproduce it:
>>
>> ./configure --with-gnome-keyring --disable-shared
>> configure: Configuring Subversion 1.7.0
>> ...
>
> That's not what Neels did. He had --disable-shared in APR's configure
> flags, and not in Subversion's configure flags.
Yes, exactly. With --disable-shared in the svn ./configure, I get the same
error. With --disable-shared in apr, apr-util, neon I don't get any warnings
although it seems to be the cause of Gnome keyring failing.
And I'd like to add, the window that you (Arfrever) attached a screenshot of
is not exactly the typical window that one gets. Your window pops up because
you don't seem to have a default keyring to begin with, and Gnome asks you
to initialize a new default keyring by entering a new password twice. The
typical GUIs would ask for either a) a passphrase to unlock an existing
keyring or b) permission to access an existing password entry in an
existing, already unlocked keyring. It's a mouthful...
In addition to that, if I understand correctly, the Gnome keyring usage by
Subversion should currently not pop up any GUIs at all, because we're trying
to allow headless use of it (no Gnome WM running).
Is that right, Senthil?
> But I can't be sure, because I keep finding out again and again that
> I don't understand libtool.
>
> Stefan
Hey, I'm relying on you here ;)
~Neels
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1963883
Received on 2009-04-28 16:02:53 CEST