clamav 0.98.3_0 fails in build stage (missing symbols) with pre-Xcode 5.1

[zzanderr]

In main.log, I have numerous innocuous warnings, at least as far as I could tell, then :

:info:build ld warning: in ../libclamav/libclamav.map, file is not of required architecture

A few lines later, I get

:info:build ld: symbol(s) not found
:info:build collect2: ld returned 1 exit status
:info:build make[4]: *** [libclamav.la] Error 1

Note that the Changelog for clamav 0.98.3 states that the release is intended to "address Windows-specific issues." I'm by no means an expert, but perhaps this release wasn't meant for Macs that lack a windows boot partition.

Machine: ppc 7450 (PowerBook G4, 1.67 GHz)
OS: 10.5.8
XCode: 3.1.4 (latest version for Leopard)
Compiler: Xcode GCC 4.2
Port: clamav@0.98.3_0 (upgrade) (no clamav_milter nor universal variants selected in original install)
main.log attached

[zzanderr]

clamav 0.98.3_0 main.log

[danielluke (Daniel J. Luke)]

That's just a warning, but the problem seems to be similar to what happens on snow leopard, lion, mountain lion, and mavericks with Xcode 5.0 (but does not happen with Xcode 5.1 on mavericks):

  CCLD   libclamav.la
ld: warning: ignoring file ../libclamav/libclamav.map, file was built for unsupported file format ( 0x43 0x4C 0x41 0x4D 0x41 0x56 0x5F 0x50 0x55 0x42 0x4C 0x49 0x43 0x20 0x7B 0x0A ) which is not the architecture being linked (x86_64): ../libclamav/libclamav.map
Undefined symbols for architecture x86_64:
  "_libiconv", referenced from:
      _encoding_normalize_toascii in libclamav_la-entconv.o
  "_libiconv_close", referenced from:
      _encoding_normalize_toascii in libclamav_la-entconv.o
      _iconv_pool_tls_instance_destroy in libclamav_la-entconv.o
  "_libiconv_open", referenced from:
      _encoding_normalize_toascii in libclamav_la-entconv.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Your problem appears to be a different set of symbols (but is otherwise similar).

I'm not sure what the problem is (yet).

If you figure it out before I do, please update this ticket.