Marius Gedminas proclaimed on mutt-users that:
>On Sun, Jul 02, 2000 at 01:06:29PM -0500, Donnie Pennington wrote:
>> Well, you're absolutely correct. Mutt installed to /usr/local rather than
>> /usr. Is something I could have tweaked to get the install to go to /usr
>> instead?
>Yes, the --pr
On Sun, Jul 02, 2000 at 01:06:29PM -0500, Donnie Pennington wrote:
> Well, you're absolutely correct. Mutt installed to /usr/local rather than
> /usr. Is something I could have tweaked to get the install to go to /usr
> instead?
Yes, the --prefix=usr option to ./configure. However I prefer to
Donnie Pennington proclaimed on mutt-users that:
>Well, you're absolutely correct. Mutt installed to /usr/local rather than
>/usr. Is something I could have tweaked to get the install to go to /usr
>instead?
You can set the install directory when running ./configure. Or, you could
just move t
On Sun Jul 02 2000 at 03:40:45PM +0200, Marius Gedminas wrote:
> This sounds like you did a `make install' and it installed everyting
> into /usr/local, while your old mutt version is still in /usr. Try
> running /usr/local/bin/mutt. If it works, you can rpm -e your old mutt
> package.
>
> (Als
> I installed glibc-devel and ncurses-devel. The mutt compile acted like it
> was working, but when I check mutt after the compile I'm still left with the
> old one. Here is the latest config.log. The problem appears to be at line
> 3593.
This logs looks pretty ok to me. Did you do a 'make i
On Sat, Jul 01, 2000 at 10:20:49PM -0500, Donnie Pennington wrote:
> On Sat Jul 01 2000 at 07:03:30PM +0100, Lars Hecking wrote:
> > Ok. According to this, you won't be able to compile anything
> > with your compiler. You need to install the glibc-devel RPM
> > which includes essential files li
On Sat Jul 01 2000 at 07:03:30PM +0100, Lars Hecking wrote:
> Ok. According to this, you won't be able to compile anything
> with your compiler. You need to install the glibc-devel RPM
> which includes essential files like the startup codes for
> C programs (crt1.o), and libraries and include
> Sorry for the wordwrap problem. I switched from gedit to joe. Maybe this
> will look better.
Indeed :)
> Here is the config.log. How do I get "full configure output"?
I'm only refering to the output from configure. But, in this case,
config.log is enough to diagnose the problem.
> co
On Sat Jul 01 2000 at 04:46:23PM +0100, Lars Hecking wrote:
>
> [Argh - please wrap long lines. Makes reading easier.]
>
> Donnie Pennington writes:
> > OK, I readily admit to Mutt newbie status. But I do have Mutt, Fetchmail and
>Sendmail working apparently OK on my iMac with LinuxPPC. I'm u
[Argh - please wrap long lines. Makes reading easier.]
Donnie Pennington writes:
> OK, I readily admit to Mutt newbie status. But I do have Mutt, Fetchmail and
>Sendmail working apparently OK on my iMac with LinuxPPC. I'm using the older mutt
>that LinuxPPC provides an RPM for, but have trie
OK, I readily admit to Mutt newbie status. But I do have Mutt, Fetchmail and Sendmail
working apparently OK on my iMac with LinuxPPC. I'm using the older mutt that
LinuxPPC provides an RPM for, but have tried unsuccessfully to compile the latest
stable mutt. I finally figured out I had to in
11 matches
Mail list logo
