From: "David A. Desrosiers" <hacker@gnu-designs.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: Evolution Pilot Conduit
Date: Sun, 6 Jan 2002 13:19:48 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.43.0201061316230.5815-100000@broccoli.geek.box> (raw)
> If anyone is interested it was pilot-link that had a broken
> configure-script causing it not to build with iconv support. :)
Actually, no. Your build of pilot-link wasn't built properly. In
fact, one of the Ximian guys added the iconv check to pilot-link last
December, since it never used iconv in the past. You can see the actual
insertion point here:
http://cvs.pilot-link.org/index.cgi/configure.in.diff?r1=1.27&r2=1.28
Please don't blame pilot-link for incorrect builds. The script works
fine on my machine, and on many other machines that have included iconv
support. If there's a bug, please submit a patch to the file in question, or
report the bug at bugs.pilot-link.org.
I'm not on this list, so replies back to the list will not reach me.
/d
next reply other threads:[~2002-01-06 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 21:19 David A. Desrosiers [this message]
2002-01-06 21:55 ` [gentoo-dev] Re: Evolution Pilot Conduit Mikael Hallendal
[not found] <Pine.LNX.4.43.0201061551040.6853-100000@broccoli.geek.box>
2002-01-07 0:21 ` Mikael Hallendal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.43.0201061316230.5815-100000@broccoli.geek.box \
--to=hacker@gnu-designs.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox