I don't know about tr, but there has been a sed encoding-related bug [1] lurking around for some time now.
[1] https://trac.macports.org/ticket/20686 Le 3 avr. 2010 à 06:31, Scott Haneda a écrit : > I seem to recall a while back, that there may have been an issue with > MacPorts due to how there are subtle differences in the `tr` command. > > Is my memory off base here, was it a different command? > > If anyone can point me to a relevant thread, I would appreciate it. I am > working on a port and I keep getting a "tr: Illegal byte sequence", which is > no fault of MacPorts, but the answer to this may lead me down the path of an > explanation. > > Thank you. > -- > Scott * If you contact me off list replace talklists@ with scott@ * > > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
