Re: 1.5.10 build woes: libiconv

To: Mutt mailing list <mutt-users@xxxxxxxx>
Subject: Re: 1.5.10 build woes: libiconv
From: Charles Cazabon <mutt@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 30 Sep 2005 14:29:29 -0600
In-reply-to: <20050930191658.GA10005@xxxxxxxxxxxxxxxxxxxx>
List-unsubscribe: <mailto:mutt-users-request@mutt.org?body=unsubscribe>
Mail-followup-to: Mutt mailing list <mutt-users@xxxxxxxx>
References: <20050930191658.GA10005@xxxxxxxxxxxxxxxxxxxx>
Sender: owner-mutt-users@xxxxxxxx
User-agent: Mutt/1.5.6i

Charles Cazabon <mutt@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> Or am I doing something wrong?

Apparently I was.  I'm currently using libiconv in "plugin mode" via
LD_PRELOAD with mutt 1.5.6; once added to the systems' ld cache, configure
runs correctly.  Interestingly, this means the systems original header files
were good enough for configure for mutt 1.5.6 (though the functions themselves
were not), but configure won't even run without the newer object files with
mutt 1.5.10.

Charles
-- 
-----------------------------------------------------------------------
Charles Cazabon                             <mutt@xxxxxxxxxxxxxxxxxxxx>
GPL'ed software available at:               http://pyropus.ca/software/
-----------------------------------------------------------------------

References:
- 1.5.10 build woes: libiconv
  - From: Charles Cazabon

Prev by Date: 1.5.10 build woes: libiconv
Next by Date: send-hooks for Cc:
Previous by thread: 1.5.10 build woes: libiconv
Next by thread: send-hooks for Cc:
Index(es):
- Date
- Thread