Hello, I am still testing and fixing my aMule 2.2.3 port.
I am using 'port test' from porttools (a very nice tool), and in the
"make package" step I notice something funny:
===> Building package for aMule-2.2.3
Creating package /usr/ports/net-p2p/amule2.work/aMule-2.2.3.tbz
Registering depends:.
Registering conflicts: aMule-1.* aMule-devel-[0-9]* ed2k-hash-1.*.
Creating bzip'd tar ball in '/usr/ports/net-p2p/amule2.work/aMule-2.2.3.tbz'
tar: share/locale/en_US/LC_MESSAGES/amule.mo: Cannot stat: No such
file or directory
tar: share/locale/es_MX/LC_MESSAGES/amule.mo: Cannot stat: No such
file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** Error code 1
Stop in /usr/ports/net-p2p/amule2.work.
*** Error code 1
Stop in /usr/ports/net-p2p/amule2.work.
===> Error running make package
In work/aMule-2.2.3/intl/config.charset I find this little snippet:
# FreeBSD 4.2 doesn't have nl_langinfo(CODESET); therefore
# localcharset.c falls back to using the full locale name
# from the environment variables.
Well, according to nl_langinfo(3), FreeBSD has that function since FreeBSD 4.6.
I am not really sure how to handle this. The port already use these
configure args:
--without-included-gettext
--with-libintl-prefix=${LOCALBASE}
So the parts in work/aMule-2.2.3/intl shouldn't matter. Or am I
missing something (again)?
Anyway, the output of 'port test' can be found here[1], in case it helps.
References:
1) http://tingox.googlepages.com/amule-testing.txt
--
Regards,
Torfinn Ingolfsen
_______________________________________________
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"
