From: Silas S. <si...@gm...> - 2011-05-07 00:02:04
|
Hi there. notion is a great continuation of ion3, and much more democratic :-) I'd like to ask you how you deal with portability. Is Linux the main target? Is it the only target? I've successfully compiled and used notion in NetBSD, with no problems, but recently I had to make a one-line modification to workaround a problem... patch is attached. So, do you plan to work on portability? Thanks. -- Silas Silva |
From: Etan R. <de...@un...> - 2011-05-07 04:07:10
|
There's no patch attached. As far as I'm concerned, which only counts a certain amount, any reasonable changes needed to handle portability are worth it. Given the needs of notion there really shouldn't be too much that causes portability headaches. -Etan |
From: Arnout E. <no...@bz...> - 2011-05-08 11:26:44
|
On Fri, May 06, 2011 at 09:02:32PM -0300, Silas Silva wrote: > notion is a great continuation of ion3, and much more democratic :-) > > I'd like to ask you how you deal with portability. Is Linux the main > target? Yes > Is it the only target? No: a while ago we fixed some problems to build have notion build properly on solaris, for example > I've successfully compiled and used notion in NetBSD, with no problems, Cool > but recently I had to make a one-line modification to workaround a > problem... patch is attached. No it isn't :) > So, do you plan to work on portability? Personally, not really, but if you can test things and provide patches I'd be happy to consider them for inclusion. Kind regards, Arnout |
From: Silas S. <si...@gm...> - 2011-05-10 18:24:46
Attachments:
notion-netbsd.diff
|
On Fri, May 06, 2011 at 09:02:32PM -0300, Silas Silva wrote: > I've successfully compiled and used notion in NetBSD, with no problems, > but recently I had to make a one-line modification to workaround a > problem... patch is attached. Sorry, here we go with patch _attached_ now!!! :-) This is quick and ugly. There might be a more inteligent way of doing this besides poluting code with #ifdefs... -- Silas Silva |
From: Etan R. <de...@un...> - 2011-05-10 18:28:02
|
What problem does that fix exactly? -Etan |
From: Silas S. <si...@gm...> - 2011-05-10 18:43:43
|
On Tue, May 10, 2011 at 02:27:53PM -0400, Etan Reisner wrote: > What problem does that fix exactly? features.h doesn't exist in NetBSD and maybe in other BSD platforms. #include <features.h> is really necessary in Linux? I even don't know what functionality it includes... -- Silas Silva |
From: Etan R. <de...@un...> - 2011-05-11 15:03:42
|
On Tue, May 10, 2011 at 03:44:19PM -0300, Silas Silva wrote: > On Tue, May 10, 2011 at 02:27:53PM -0400, Etan Reisner wrote: > > What problem does that fix exactly? > > features.h doesn't exist in NetBSD and maybe in other BSD platforms. Does '#include <sys/featuretest.h>' work? -Etan |
From: Silas S. <si...@gm...> - 2011-05-11 17:12:13
|
On Wed, May 11, 2011 at 11:03:34AM -0400, Etan Reisner wrote: > Does '#include <sys/featuretest.h>' work? It works and it is a much better solution, thanks!!! Have conditional compilation to differentiate OS/machines is ugly. Stickying to ANSI C is much better and it is why Lua is so portable :-) Thank you very much. -- Silas Silva |
From: Etan R. <de...@un...> - 2011-05-11 17:26:42
|
On Wed, May 11, 2011 at 02:12:47PM -0300, Silas Silva wrote: > On Wed, May 11, 2011 at 11:03:34AM -0400, Etan Reisner wrote: > > Does '#include <sys/featuretest.h>' work? > > It works and it is a much better solution, thanks!!! Ok, good. Now I just need to find out what defines I can use to detect netbsd. > Have conditional compilation to differentiate OS/machines is ugly. > Stickying to ANSI C is much better and it is why Lua is so portable :-) Yeah, when it is reasonably possible being natively portable is definitely the best option. But the farther up the stack you get the less that's really possible (well up to a certain point at least). -Etan |