Send kea-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."
Today's Topics:
1. Re: The kea-msg-compiler does not support cross-compile ?
(Tomek Mrugalski)
2. Re: The kea-msg-compiler does not support cross-compile ?
(Francis Dupont)
3. Re: The kea-msg-compiler does not support cross-compile ?
(Francis Dupont)
4. Re: The kea-msg-compiler does not support cross-compile ?
(=?utf-8?B?5rW35rWq?=)
5. Re: The kea-msg-compiler does not support cross-compile ?
(Francis Dupont)
6. Re: Is it possible for hooks to hande server shutdown?
(Dave Cole)
7. Re: Is it possible for hooks to hande server shutdown?
(Thomas Markwalder)
----------------------------------------------------------------------
Message: 1
Date: Thu, 5 Oct 2017 14:20:22 +0200
From: Tomek Mrugalski <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] The kea-msg-compiler does not support
cross-compile ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
W dniu 05.10.2017 o?08:32, ?? pisze:
> Hi all,
> ? ? I am porting the kea project into OpenWRT (for platform mips, arm,
> x86...) but it seems the target kea-msg-compiler does not support
> cross-compile.
Am afraid you may be one of the first to try cross-compilation of Kea.
As far as I can tell, none of the ISC engineers done cross-compilation.
It is quite possible that some things are not exactly right. If you're
willing to share some patches, we'd gladly take a look. Just keep in
mind that the patches must not affect regular compilation, as this is
the great majority of our user base.
Message compiler is needed only during compilation. It takes .mes files
and produces .cc and .h files out of them. If you want to just install
Kea and keep the English messages Kea is producing by default, you don't
really need kea-msg-compiler on your target system, just on your host
system where you cross-compile.
It may be useful if you (or your users) want to modify .mes file, e.g.
to translate Kea to a different language. But then, you'd probably do
that on a PC, not on OpenWRT, right?
So my suggestion is to think whether you really need kea-msg-compiler on
your target platform. If not, you should modify the makefiles to not
require msg-compiler installation. A switch to configure would probably
be the best way to go.
Tomek
------------------------------
Message: 2
Date: Thu, 05 Oct 2017 12:26:00 +0000
From: Francis Dupont <[email protected]>
To: "=?utf-8?B?5rW35rWq?=" <[email protected]>
Cc: "=?utf-8?B?a2VhLWRldg==?=" <[email protected]>
Subject: Re: [kea-dev] The kea-msg-compiler does not support
cross-compile ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
There is an old ticket about cross-compiling and according to it
the main problem is to build kea-msg-compiler as a building box binary
(vs the target box), cf #3745. BTW if the "very easy" solution works
well for you please signal it to us so the ticket will be reconsidered
for a future release...
Regards
Francis Dupont <[email protected]>
------------------------------
Message: 3
Date: Thu, 05 Oct 2017 12:56:01 +0000
From: Francis Dupont <[email protected]>
To: Tomek Mrugalski <[email protected]>
Cc: [email protected]
Subject: Re: [kea-dev] The kea-msg-compiler does not support
cross-compile ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
I tried a long time ago (this is why we have #3745 ticket) but with
Apple Xcode and iOS target (so I checked only how to build) mainly
because it is well documented and pretty fast...
Regards
Francis Dupont <[email protected]>
PS: BTW I simply copied the message compiler binary to its destination
in the build tree.
------------------------------
Message: 4
Date: Thu, 5 Oct 2017 22:01:55 +0800
From: "=?utf-8?B?5rW35rWq?=" <[email protected]>
To: "=?utf-8?B?RnJhbmNpcyBEdXBvbnQ=?=" <[email protected]>,
"=?utf-8?B?VG9tZWsgTXJ1Z2Fsc2tp?=" <[email protected]>
Cc: "=?utf-8?B?a2VhLWRldg==?=" <[email protected]>
Subject: Re: [kea-dev] The kea-msg-compiler does not support
cross-compile ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Yes, me either, I want to copy the message compiler binary into my build tree,
but this seems not a good solution,
How about making kea-project to be a OOTB (Out of the box) software.
------------------ Original ------------------
From: "Francis Dupont"<[email protected]>;
Date: 2017?10?5?(???) ??8:56
To: "Tomek Mrugalski"<[email protected]>;
Cc: "kea-dev"<[email protected]>;
Subject: Re: [kea-dev] The kea-msg-compiler does not support cross-compile ?
I tried a long time ago (this is why we have #3745 ticket) but with
Apple Xcode and iOS target (so I checked only how to build) mainly
because it is well documented and pretty fast...
Regards
Francis Dupont <[email protected]>
PS: BTW I simply copied the message compiler binary to its destination
in the build tree.
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/kea-dev/attachments/20171005/ca85b652/attachment-0001.html>
------------------------------
Message: 5
Date: Thu, 05 Oct 2017 14:39:40 +0000
From: Francis Dupont <[email protected]>
To: "=?utf-8?B?5rW35rWq?=" <[email protected]>
Cc: "=?utf-8?B?RnJhbmNpcyBEdXBvbnQ=?=" <[email protected]>,
"=?utf-8?B?VG9tZWsgTXJ1Z2Fsc2tp?=" <[email protected]>,
"=?utf-8?B?a2VhLWRldg==?=" <[email protected]>
Subject: Re: [kea-dev] The kea-msg-compiler does not support
cross-compile ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
> Yes, me either, I want to copy the message compiler binary into my
> build tree, but this seems not a good solution,
=> by "not a good solution" do you mean it does not work or just
you really prefer a more integrated support for cross-compiling.
> How about making kea-project to be a OOTB (Out of the box) software.
=> for cross-compiling it is just a question of requests: you are the
first person asking for it and when I looked at what to add and created
the #3745 ticket there were a lot of more urgent things so it was not
discussed/addressed even for a (too) basic solution...
Note if the only problem is to build an usable message compiler we
already have another product (bind9) which uses also an internal
generator binary so it is not something very hard (just time consuming).
Regards
Francis Dupont <[email protected]>
------------------------------
Message: 6
Date: Fri, 6 Oct 2017 00:57:50 +0000
From: Dave Cole <[email protected]>
To: Baptiste Jonglez <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [kea-dev] Is it possible for hooks to hande server
shutdown?
Message-ID:
<syxpr01mb17275312c724c36d536ae8d6f2...@syxpr01mb1727.ausprd01.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
> The load and unload points are in the same file wrapped in the same extern
> "C".
>
> In my in-expect browsing of the code I could not see any way that the unload
> hook was being called on server exit.? I was just hoping someone with a clue
> would confirm that for me, and maybe suggest a way to achieve the same effect.
>
> Using onexit is not going to work since a hook reload would almost certainly
> cause a segfault during server exit.
I do not pretend to understand what is going on, but when I built my hook on
centos7, the unload callback is being invoked during server shutdown.
Oh well...
------------------------------
Message: 7
Date: Fri, 6 Oct 2017 06:59:28 -0400
From: Thomas Markwalder <[email protected]>
To: [email protected]
Subject: Re: [kea-dev] Is it possible for hooks to hande server
shutdown?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
On 10/5/17 8:57 PM, Dave Cole wrote:
>> The load and unload points are in the same file wrapped in the same extern
>> "C".
>>
>> In my in-expect browsing of the code I could not see any way that the unload
>> hook was being called on server exit.? I was just hoping someone with a clue
>> would confirm that for me, and maybe suggest a way to achieve the same
>> effect.
>>
>> Using onexit is not going to work since a hook reload would almost certainly
>> cause a segfault during server exit.
> I do not pretend to understand what is going on, but when I built my hook on
> centos7, the unload callback is being invoked during server shutdown.
>
> Oh well...
> _______________________________________________
> kea-dev mailing list
> [email protected]
> https://lists.isc.org/mailman/listinfo/kea-dev
Hi Dave:
Each configured hook library is owned by an instance of
isc::hooks::LibraryManager.? Whenever a library needs to unloaded, it is
done through:?
LibraryManager::unloadLibrary() -> LibraryManager::runUnload() ->
SomeHookLib::unload().
This chain is invoked by LibraryManager's destructor, so during a
shutdown the hook library unloads are automatically called, as each
LibraryManager gets destroyed.
Hope that answers your question.
Regards,
Thomas Markwalder
ISC Software Engineering
------------------------------
Subject: Digest Footer
_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev
------------------------------
End of kea-dev Digest, Vol 43, Issue 5
**************************************
