In message <[EMAIL PROTECTED]>, Rick Hoffman writes: >> Probably the best thing is to get a fresh copy of 4.0.3 and run >> './configure' and 'make' yourself. Then, if you still have any >> problems, you can enable debug tracing and see what's going on. > >I am guessing the Debian maintainer of this package used all the >default settings when he/she compiled it. I am also guessing that >would be the most logical thing to do because if there are any >specific user settings/configuration issues shouldn't I be able to >negociate those through command line options or a configuration file? >If not then I wonder what it is that I need to compile in to make >a difference from what is going on now.
That's not necessarily true. Why don't you contact the Debian developer for this package? He can probably tell you if the problems you're seeing are due to how he packaged it or not. In general, bugs in Debian packages should be reported to the Debian Bug Tracking System first, and then to the upstream developers, so that the upstream isn't bothered trying to support bugs that were introduced by Debian in the first place. You can find instructions for submitting Debian bug reports here: http://www.debian.org/Bugs/Reporting Thanks. -- Ted Cabeen http://www.pobox.com/~secabeen [EMAIL PROTECTED] Check Website or Keyserver for PGP/GPG Key BA0349D2 [EMAIL PROTECTED] "I have taken all knowledge to be my province." -F. Bacon [EMAIL PROTECTED] "Human kind cannot bear very much reality."-T.S.Eliot [EMAIL PROTECTED]
