ruby18 not compiling on -CURRENT.... tr bug

Sean McNeil sean at
Tue Jul 13 19:51:26 PDT 2004

Thanks, SANETO,

It was the bug in tr that was the problem.  I think this is a recurring
problem.  I recall tr had an issue once before and was fixed.

All is well again in my world :)

To recap, ruby18 was failing to portupgrade and ended up with an empty
config.h file.  SANETO saw the same issue and it is related to a bad
version of tr.  -CURRENT cvsup'd today has a fixed tr.


More information about the freebsd-ports mailing list