| 1 |
sön 2002-01-06 klockan 22.19 skrev David A. Desrosiers: |
| 2 |
> |
| 3 |
> > If anyone is interested it was pilot-link that had a broken |
| 4 |
> > configure-script causing it not to build with iconv support. :) |
| 5 |
|
| 6 |
First, next time you send a one month delayed reply to a list it would |
| 7 |
be nice if you didn't cut out who wrote the first mail (it turned out to |
| 8 |
be me). |
| 9 |
|
| 10 |
> Actually, no. Your build of pilot-link wasn't built properly. |
| 11 |
|
| 12 |
That is the entire problem. |
| 13 |
|
| 14 |
> Please don't blame pilot-link for incorrect builds. |
| 15 |
|
| 16 |
If the problem that pilot-link doesn't get built correctly is the fault |
| 17 |
of pilot-link it should be blamed. |
| 18 |
|
| 19 |
> The script works fine on my machine, and on many other machines that |
| 20 |
> have included iconv support. |
| 21 |
|
| 22 |
That isn't always equal to the script being correct though. |
| 23 |
|
| 24 |
> If there's a bug, please submit a patch to the file in question, or |
| 25 |
> report the bug at bugs.pilot-link.org. |
| 26 |
|
| 27 |
The problem was that configure found iconv in our glibc but it didn't |
| 28 |
set HAVE_ICONV=1 in pi-config.h. If I did |
| 29 |
|
| 30 |
echo "#define HAVE_ICONV 1" >> pi-config.h |
| 31 |
|
| 32 |
after configure had run it built correctly with ICONV support. So I |
| 33 |
think that in someway the configure-script was broken. Haven't had time |
| 34 |
to look more deeply into it. Might also be our autoconf but I haven't |
| 35 |
had any problems with any other packages than pilot-link. |
| 36 |
|
| 37 |
Regards, |
| 38 |
Mikael Hallendal |
| 39 |
|
| 40 |
-- |
| 41 |
Mikael Hallendal |
| 42 |
Gentoo Linux Developer, Desktop Team Leader |
| 43 |
CodeFactory AB, Stockholm, Sweden |
Archives