Ticket #16862 (closed defect: fixed)
QT4-mac cannot find iconv
| Reported by: | myschizobuddy@… | Owned by: | erickt@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | qt4-mac | Cc: | clubjuggler@…, mcalhoun@… |
| Port: | qt4-mac |
Description
qt4-mac version 4.4.3 cannot find the iconv library and disables iconv support
OSIX iconv auto-detection... ()
g++ -c -pipe -Os -Wall -W -I../../../mkspecs/macx-g++ -I. -I../../../include -I. -o iconv.o iconv.cpp
g++ -headerpad_max_install_names -o iconv iconv.o -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_aqua_qt4-mac/work/qt-mac-opensource-src-4.4.3/lib -L/opt/local/lib -liconv
Undefined symbols:
"_iconv", referenced from:
_main in iconv.o
"_iconv_close", referenced from:
_main in iconv.o
"_iconv_open", referenced from:
_main in iconv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make: *** [iconv] Error 1
POSIX iconv disabled.
GNU libiconv auto-detection... ()
g++ -c -pipe -Os -Wall -W -I../../../mkspecs/macx-g++ -I. -I../../../include -I. -o gnu-libiconv.o gnu-libiconv.cpp
gnu-libiconv.cpp: In function 'int main(int, char**)':
gnu-libiconv.cpp:13: error: invalid conversion from 'const char**' to 'char**'
gnu-libiconv.cpp:13: error: initializing argument 2 of 'size_t iconv(void*, char**, size_t*, char**, size_t*)'
make: *** [gnu-libiconv.o] Error 1
GNU libiconv disabled.
Attachments
Change History
comment:1 Changed 5 years ago by macsforever2000@…
- Owner changed from macports-tickets@… to erickt@…
- Cc clubjuggler@… added
comment:2 Changed 5 years ago by blb@…
Looks like another iconv vs. libiconv symbol error, see #13055.
comment:5 Changed 4 years ago by mcalhoun@…
- Status changed from new to closed
- Resolution set to fixed
Fixed in r44197.
comment:7 Changed 3 months ago by rmstonecipher@…
There are several lines in the configure.args section of the qt4-x11 Portfile similar to:
-I${prefix}/include/gstreamer-0.10 \
If qt is updated to work with gstreamer 1.x (new port gstreamer1) in the future, would looking for 0.10.x headers explicitly like this lead to opportunistic linking?
Are all of these -I flags still needed?
Note: See
TracTickets for help on using
tickets.


Assigning to maintainers.