Re:What I Learned from porting my projects to FreeBSD
by rwmj on Sunday October 28, 2018 @06:33AM
(#18320018)
Could do all that, but FreeBSD could also have GNU make as the standard "make". I know there's some "license purity" reason why they don't want to do that, but don't expect everyone else to work around your self-imposed problem.
[ Parent
| on HN ]
Re:What I Learned from porting my projects to FreeBSD
by simias on Sunday October 28, 2018 @09:34AM
(#18320508)
GNU make is ported to FreeBSD and very frequently used to build ports that use GNU-isms in their Makefiles. It's a non-issue really.
Re:What I Learned from porting my projects to FreeBSD
by wolfgke on Sunday October 28, 2018 @08:15PM
(#18324054)
> GNU make is ported to FreeBSD and very frequently used to build ports that use GNU-isms in their Makefiles. It's a non-issue really.
At least the OpenBSD developers hated the Linuxisms so much that they made a song "Aquarela do Linux!" to name and shame this:
Re:What I Learned from porting my projects to FreeBSD
by jlg23 on Sunday October 28, 2018 @04:16PM
(#18322886)
No, GNU devs should understand Unix beyond the GNU ecosystem. I'd be retired on my private planet if I had gotten a dime each time I ported Linux software (mostly the build system) to work on non-linux unixoid operating system.
To be fair: Nothing in GNUiverse teaches you interoperability; I too learned it the hard way when switching from Linux to BSD.
Re:What I Learned from porting my projects to FreeBSD
by rwmj on Monday October 29, 2018 @08:54AM
(#18327072)
GNU is literally a platform. If you want to run the software on another platform (particularly one which is not as widely used as GNU) then you have to port the software.
Re:What I Learned from porting my projects to FreeBSD
by dzamo_norton on Tuesday October 30, 2018 @02:01AM
(#18334254)
Or you have to write portable software.
Re:What I Learned from porting my projects to FreeBSD
by minusf on Sunday October 28, 2018 @07:51AM
(#18320232)
isn't make older than gmake? it is normally gnu that adds extensions not compatible with the rest of the Unix world. making people believe sh == bash, make == gmake, m4 == gm4, and the list goes on for everything they touch.
Re:What I Learned from porting my projects to FreeBSD
by lmz on Sunday October 28, 2018 @08:18AM
(#18320312)
But BSD make has extensions too. They're just different extensions.
Re:What I Learned from porting my projects to FreeBSD
by shlomifish on Monday October 29, 2018 @09:40AM
(#18327408)
To be frank, many of the GNU extensions are very useful. BSD tools have their own extensions over POSIX as well. Anyway, GNU software is FOSS and tends to be portable and so you can create something like GNU/FreeBSD or GNU/OpenBSD or whatever (Debian did it in the past). Naturally, the GPL/LGPL/etc. may not be "free" enough for the tastes of the BSD devs, but this is getting into politics.
Re:What I Learned from porting my projects to FreeBSD
by bewo001 on Monday October 29, 2018 @09:32AM
(#18327353)
Every Unix used to have its own implementation of those standard tools. They were often quite buggy and outdated (eg the C compiler that came with SunOS and Solaris in the mid 1990's only supported K&R syntax).
When installing Solaris, Sinix, AIX etc, you'd typically install the GNU tools immediately.
I understand the FreeBSD folks' frustration, though.