I have/had/have had a similar " libintl_textdomain "

in a great many ports (currently pcmanfm and about twenty others), and it has 
persisted on-and-off year after

year.  No amount of dependency rebuild ususally solves it, eventually sometimes 
a remote package is installed
instead (v9)  So I would be interested not so much in those two specific 
errors, but a wrapper under which one
could build a port so that each element of the calling compilation line could 
be analyzed to see from which the
error specifically occurs, no matter how much it slows down the respective port 
build... 


________________________________
 From: O. Hartmann <ohart...@zedat.fu-berlin.de>
To: FreeBSD Ports <freebsd-ports@freebsd.org> 
Sent: Wednesday, July 31, 2013 7:28 AM
Subject: editors/vim: does not compile on CURRENT
 

I have one box that is reluctantly not compiling port editors/vim with
the following error.

main.c:(.text+0xbb7): undefined reference to `libintl_gettext'
main.c:(.text+0xc93): undefined reference to `libintl_gettext'
objects/main.o:main.c:(.text+0xcaf): more undefined references to
`libintl_gettext' follow cc: error: linker command failed with exit

code 1 (use -v to see invocation) link.sh: Linking failed *** Error
code 1
...............................................................................


J. Bouquet
(Just figured out how to put that top-posting down here, hopefully all the next 
emails I'll remember and
the post will be more readable...) 
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to