chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] Re: separate build directory support for Chicken


From: Elf
Subject: Re: [Chicken-hackers] Re: separate build directory support for Chicken
Date: Sun, 13 Jan 2008 13:53:33 -0800 (PST)

On Sun, 13 Jan 2008, Aleksej Saushev wrote:

Elf <address@hidden> writes:

http://keramida.wordpress.com/2007/12/04/bmake-call-for-developers/

this is about the fifth differing bmake ive run across.  none of which seems
to be particularly well supported outside of the particular bsd in which
it was written.  most of which seem to be pre-alpha.  very few
of which seem to be 100% compat with each other.  explain to me
why this would be a win?

bmake is supported on: NetBSD, FreeBSD, OpenBSD, OSF/1, Tru64,
HP-UX, AIX, Solaris, Mac OS X, Windows NT, Linux.
I myself used it on: NetBSD, FreeBSD, Windows NT, Linux.

it is supposedly supported for one particular development environ in windows,
not for any of the ones we support.  are you going to port it to cygwin and
mingw?  its support for other systems is incredibly flaky at best, based on
their own documentation and their bug database.


Anyway, you drive discussion into unrelevant area.

Do you think that pmake or bmake is called that way in BSDs?
It is called "make", and GNU make is called "gmake".
Maybe we could look through ancient 20-25 years old trash and
found several another gmakes. Besides, gmake is well supported
only on GNU systems, you have to build it manually elsewhere
and make sure it doesn't conflict with native make.
So, your point doesn't matter.

i dont know where youre thinking that gmake is only well supported on gnu
systems; i use gnu make on linux, hpux, openbsd, cygwin, and mingw on a more-or-less daily basis, and not infrequently on darwin. ive not run
into a problem attributable to platform support/compatibility for at least 5
years.  opensolaris requires gmake to build basically everything except the
kernel. the last major bug with gmake on aix was in 2004: nowadays, aix requires gmake for compiling many packages, including their scsi drivers.
hpux sites ONLY use gmake at this point.  mingw is gnu make.  cygwin is gnu
tools. the irix site flat out states that theres no reason to use any of the native makes anymore. from personal experience, ive never had a problem
with gmake on bsd.  nor are there naming problems; gnu's install explicitly
sets the name to not conflict.

im not trying to defend gnu's make, yet again. i am merely stating that it works, is available, and in very common usage. ie, there is no barrier for entry and nothing extra people have to do to install it. this makes it more likely that people will install chicken.


In contrast, BSD make is supported on same range of platforms
and comes with build and package system, GNU doesn't provide either,
you have to build and to maintain installations manually.
But that doesn't matter here too.


which bsd make?  bsd makes on different bsd implementations are not compatible.
nor are the build or package systems, which i abhor.


What matters, is proposed conversion to GNU autotools and
GNU srcdir way.



i wasnt aware we were arguing regarding autotools.  felix got rid of autotools
a few months ago; 2.4 i think was either the last autotooled or first nonautotooled implementation. the autotools system became insanely unwieldly
and impractical, hence the current system.



_______________________________________________
Chicken-hackers mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/chicken-hackers





reply via email to

[Prev in Thread] Current Thread [Next in Thread]