What is the best way to test if a header file works or not? I mean, I
removed all the includes from list.h, I want to check if it works
On Thu, Jun 8, 2017 at 1:43 AM, Vivek Roy <vivekroyandroid@xxxxxxxxx> wrote:
Why is there all the net/*.h and netinet/*.h? Why do you need those for a
linked list?
On Thu, Jun 8, 2017 at 1:26 AM, Vivek Roy <vivekroyandroid@xxxxxxxxx>
wrote:
I have seen this, but this has a bunch of includes which are not there in
Haiku
On Thu, Jun 8, 2017 at 12:00 AM, Hamish Morrison <hamishm53@xxxxxxxxx>
wrote:
Here's the one from FreeBSD's linux compatibility layer:
https://github.com/freebsd/freebsd/blob/master/sys/compat/li
nuxkpi/common/include/linux/list.h
You could use this verbatim in Haiku - no tweaking needed.
On Wed, Jun 7, 2017 at 6:47 PM, Vivek Roy <vivekroyandroid@xxxxxxxxx>
wrote:
The code in question (for now) is Linux's list.h (doubly linked list).required to
There are implementations in FreeBSD and NetBSD but the effort
tweak them to suit Haiku is almost the same (I feel would be) as takingis safe
Linux's implementation and working with it. So I was wondering if it
to work directly with Linux's implementation.wrote:
On Wed, Jun 7, 2017 at 4:42 AM, Hamish Morrison <hamishm53@xxxxxxxxx>
some
What is the code in question by the way? You might be able to find
need toFreeBSD/DragonyflyBSD implementation if this is Linux kernel code we
umccullough@xxxxxxxxxemulate.
On 06/06/2017 22:26, Vivek Roy wrote:
Okay thanks James Taylor and Urias McCullough.
On Wed, Jun 7, 2017 at 2:20 AM, Urias McCullough <
james.dewey.taylor@xxxxxxxxx<mailto:umccullough@xxxxxxxxx>> wrote:
On Tue, Jun 6, 2017 at 1:42 PM, Dewey <
ering<mailto:james.dewey.taylor@xxxxxxxxx>> wrote:
https://en.m.wikipedia.org/wiki/Chinese_wall#Reverse_engine
based on
<https://en.m.wikipedia.org/wiki/Chinese_wall#Reverse_engineering>
Not specifically reverse engineering, but it's what would be
called a clean-room reimplementation. One person or group
documents the existing code and another writes new code
thethe documentation. This allows new code to be written and
released under any license without infringing the license of
involvedexisting code. At least two participants/groups MUST be
seebecause the person(s) writing new code cannot be allowed to
one orthe old code whatsoever to prevent inadvertently writing code
that is too similar to the original code.
There is another option...
If the code in question is relatively small, and copyright by
project.two people only - you may be able to just contact them and ask
permission to relicense it under MIT/BSD or similar for your
to
Sometimes that's all that is needed.
If, on the other hand, the copyright has been assigned to some
larger body, and they are anal about GPL licensing, you may have
do the clean room implementation or find another similar version
that is licensed the way you want.
- Urias
