converters/libiconv build error

[Henk van Oers]

On a small FreeBSD 6.3 system (Pentium I, 120 MHz, 32 MB)
i have postfix running, a bit of perl and ... bash

I did an upgrade after reading:
<q>
20080605:
   AFFECTS: users of devel/gettext (ie: YOU)
   AUTHOR: ade at FreeBSD.org

   As a result of the upgrade to gettext-0.17, the shared library version
   of libintl has changed, so you will need to rebuild all ports that
   depend on gettext:

   # portupgrade -rf gettext
   # portmaster -r gettext\*

   Given the scope and sheer number of dependent ports, it may be more
   advisable to simply blow away all existing install ports (after
   keeping any local configuration changes), and rebuilding from scratch.
</q>

Even with a hand full of gettext dependencies, normal upgrade did not
work, so i deleted all related ports and started rebuilding from scratch.

For bash i need converters/libiconv but is stops with:
[...]
config.status: creating po/Makefile
./configure.lineno: 40477: Syntax error: Unterminated quoted string
===>  Script "configure" failed unexpectedly.
Please run the gnomelogalyzer, available from
"http://www.freebsd.org/gnome/gnomelogalyzer.sh", which will diagnose the
problem and suggest a solution. If - and only if - the gnomelogalyzer 
cannot
solve the problem, report the build failure to the FreeBSD GNOME team at
gnome at FreeBSD.org, and attach (a)
"/usr/ports/converters/libiconv/work/libiconv-1.11/config.log", (b) the 
output
of the failed make command, and (c) the gnomelogalyzer output. Also, it 
might
be a good idea to provide an overview of all packages installed on your 
system
(i.e. an `ls /var/db/pkg`). Put your attachment up on any website,
copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) 
with
the attachment. Try to avoid sending any attachments to the mailing list
(gnome at FreeBSD.org), because attachments sent to FreeBSD mailing lists are
usually discarded by the mailing list software.
*** Error code 1

Stop in /usr/ports/converters/libiconv.
*** Error code 1
-----------------------

Mmmm, ok, run gnomelogalyzer.sh on the logfile:

<q>
The cause of your build failure is not known to gnomelogalyzer.sh.  Before
e-mailing the build log to the FreeBSD GNOME team at 
freebsd-gnome at FreeBSD.org,
TRY EACH OF THE FOLLOWING:

   * If you are generating your own logfile, make sure to generate it with
     something similar to:
           "make 2>&1 | tee /path/to/logfile" (sh/bash/ksh/zsh) or
           "make |& tee /path/to/logfile" (csh/tcsh)
         * Make sure your cvsup(1) configuration file specifies the 
'ports-all'
           collection
         * Run cvsup(1) and attempt the build again
         * Check /usr/ports/UPDATING for information pertinent to your 
build
           failure
         * 99% of the commonly reported build failures can be solved by
           running "portupgrade -a"
         * Read the FAQs at http://www.FreeBSD.org/gnome/
         * Search the archives of freebsd-gnome at FreeBSD.org.  Archives can 
be
           searched at http://www.freebsd.org/gnome/index.html#search

If you have not performed each of the above suggestions, don't bother 
asking
for help.  The chances are good that you'll simply be told to perform one 
of
the aforementioned steps.
</q>

I did re-portsnap, portupgrade -a has nothing to do.
FAQ's and archive did not help.
I want my bash back, but it needs iconv....

NB the output of 
/usr/ports/converters/libiconv/work/libiconv-1.11/config.log
is:
[....]
#define VOID_UNSETENV 1
#define HAVE__BOOL 1
#define HAVE_STDBOOL_H 1
#define HAVE_STRERROR 1
#define HAVE_READLINK 1

configure: exit 2

Do you need the whole file?