Opened 11 years ago

Closed 11 years ago

#40403 closed defect (fixed)

gtypist: Undefined symbols: _libiconv _libiconv_close _libiconv_open

Reported by: boloomka@… Owned by: joseph@…
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: haspatch Cc: ryandesign (Ryan Carsten Schmidt)
Port: gtypist

Description

Compiling of gtypist ends with error 

:info:build Undefined symbols for architecture x86_64:
:info:build   "_libiconv", referenced from:
:info:build       _convertUTF8ToCurrentEncoding in utf8.o
:info:build   "_libiconv_close", referenced from:
:info:build       _convertUTF8ToCurrentEncoding in utf8.o
:info:build   "_libiconv_open", referenced from:
:info:build       _convertUTF8ToCurrentEncoding in utf8.o
:info:build ld: symbol(s) not found for architecture x86_64

It is new macbook air with OS X 10.8.4. I think that it might be some missing dependency, but I have "libiconv" installed.

Attachments (2)

main.log​ (12.3 KB) - added by boloomka@… 11 years ago.
log output from compiling gtypist
gtypist-iconv.diff​ (803 bytes) - added by ryandesign (Ryan Carsten Schmidt) 11 years ago.
proposed patch

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by boloomka@…

Attachment: main.log​ added

log output from compiling gtypist

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Keywords: haspatch added
Owner: changed from macports-tickets@… to joseph@…
Summary: cannot compile gtypist → gtypist: Undefined symbols: _libiconv _libiconv_close _libiconv_open

I've attached a patch that fixes it. Joseph, may I commit it?

Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: gtypist-iconv.diff​ added

proposed patch

comment:2 in reply to:  1 ; Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

I've attached a patch that fixes it. Joseph, may I commit it?

I didn't know that configure.libs could be used instead of configure.ldflags... could someone document this keyword in the guide please? Although I suppose that's a separate issue...

comment:3 in reply to:  2 Changed 11 years ago by larryv (Lawrence Velázquez)

Replying to egall@…:

I didn't know that configure.libs could be used instead of configure.ldflags

It can’t be. That is, it’s not a drop-in replacement; it only works if the build respects the LIBS environment variable.

comment:4 Changed 11 years ago by neverpanic (Clemens Lang)

Resolution: → fixed
Status: new → closed

Fixed in r114087 and r114088.

Note: See TracTickets for help on using tickets.