Aaron Stone wrote:
Magnus has an important point: don't check for an OS, check for what its
behavior is. I believe that in this case, we're talking about activating
parts of a system-dependent header with this flag. That the flag is system
dependent is not at issue; it's how we test that.
If
Magnus has an important point: don't check for an OS, check for what its
behavior is. I believe that in this case, we're talking about activating
parts of a system-dependent header with this flag. That the flag is system
dependent is not at issue; it's how we test that.
If the approach is like
Original Message
From: Aaron Stone dbmail@dbmail.org
To: dbmail@dbmail.org
Subject: Re: [Dbmail] PATCH: dbmail_configure_check_os.patch
Sent: Sat, 1 Mar 2003 00:58:48 -0800 (PST)
Magnus has an important point: don't check for an OS, check for what its
behavior is. I believe that in this case
Hi,
Is this really whise?
I remember the old time when you should compile emacs. You had to look
in the README file and change something in a configuration file with a
text editor and then write make.
A few years later, the way of compiling emacs was
./configure
make
Where the configure script
Hello Magnus,
What I suggest is that you test for the LINUX capabilities in the
configure script. By this way will the software be much more portable to
other operating systems.
You apparently misunderstood what Ryan said; this is exactly what
the patch does. Just run ./configure and if
Thanks for that patch, Ryan. I changed it to define __LINUX__
instead of LINUX (as that's what md5.c is checking), and also added
a check to build.sh to define that as well. I tested both build.sh
and ./configure build methods, and APOP/md5 works on our Sparc when
built both ways. This patch
