RE: Compile/configure question.

Subject: RE: Compile/configure question.
From: Howard Chu (hyc at highlandsun dot com)
Date: Thu Apr 03 2003 - 12:11:20 EST

I totally agree. Not to mention, my gcc complains, something about default
path problems, because it already searches /usr/local/include by default. I
always delete that CMU_ADD_LIBPATH from my local copy before I start a build.

  -- Howard Chu
  Chief Architect, Symas Corp. Director, Highland Sun
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-cyrus-sasl at lists dot andrew dot cmu dot edu
> [mailto:owner-cyrus-sasl at lists dot andrew dot cmu dot edu]On Behalf Of Mathias

> [ Lawrence Greenfield ]
> > Why are these included? Why not just append a "To include
> > /usr/local/foo when compiling, set {CPP|LD}FLAGS before running
> > 'configure'." or something to docs. The CMU_ADD_LIBPATH line
> > above has caused me a lot of extra work.
> >
> > Because a long time ago Cyrus IMAP was distributed without adding
> > /usr/local to stuff and the developers got lots of questions about
> > why stuff in /usr/local wasn't found.
> >
> > They decided to add /usr/local and it's been that way ever since.
> Hmm. That's fixing the wrong problem if you ask me. Because of this
> builds break. Why not print "If libs in /usr/local are ignored, do
> this: ..." on both the web-site and in the docs in the package, and
> then fix the code. As it is now, this looks like a bug.
> Am I the only one who doesn't like this?
> --
> Mathias Meisfjordskar
> GNU/Linux addict.
> "If it works; HIT IT AGAIN!"

Hosted Email Solutions

Invaluement Anti-Spam DNSBLs

Powered By FreeBSD   Powered By FreeBSD