Subject: Overriding Makefile vars from the commandline.

From: "Mike A. Harris" <[email-masked]>
Date: Tue, 12 Dec 2000 04:25:37 -0500 (EST)

I'd like to override some of the Makefile vars from the
commandline..

Looking in the build script it appears possible, but I'd like to
know if my args will _override_ vars in the Makefiles...

Also, being new to the code, what is the easiest way of adding an
extra include line to the compiler flags?  PINE 4.31 won't build
with ssl support on Red Hat 7.0 because it doesn't seem to look
in /usr/include/openssl for headers...

I was going to add -I/usr/include/openssl, but I'm not sure the
best place to put it.

TIA

----------------------------------------------------------------------
      Mike A. Harris  -  Linux advocate  -  Open source advocate
          This message is copyright 2000, all rights reserved.
  Views expressed are my own, not necessarily shared by my employer.
----------------------------------------------------------------------

Windows 95(n) - 32-bit extensions and graphical shell for a 16-bit patch
to an 8-bit operating system originally coded for a 4-bit microprocessor,
written by a 2-bit company that can't stand 1 bit of competition. 

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: "Mike A. Harris" <[email-masked]>
Date: Tue, 12 Dec 2000 09:44:40 -0500 (EST)

On Tue, 12 Dec 2000, Stefan Vacek wrote:

>On Tue, Dec 12, 2000 at 04:25:37AM -0500, Mike A. Harris wrote:
>I changed imap/src/osdep/unix/Makefile.ssl to set things right.

I'm not sure what you mean by that.  I've got the PINE 4.31
source, and it doesn't build without the my Red Hat openssl patch
being applied.  It hits imap/src/osdep/unix/Makefile.ssl and
auth_ssl.c.

If I'm missing something, please clue me in.  ;o)

Fun thing to do as root, in the root directory:
chmod -R 666 *
Just as bad as rm -rf *, but more fun.
"The files are all there, but I can't do anything with them!"
And you can't change permissions, since chmod isn't executable either. :-)