>>>>> On Mon, 27 Nov 2006 05:36:41 -1000, Hydro Meteor said: > > As an update to my push for getting Bacula into use on Mac OS X (in this > case the Intel iMac with Core 2 Duo), I was looking through my output in > more detail and trying to make some human sense parsing what I observed and > comparing to Ubuntu Linux (the comparison I believe is good because, if I > understand the history correctly, Kern created Bacula on Linux so naturally > there is going to be more knowledge and experience around Linux distros > running Bacula). > > I found this output from ./configure on the Mac's command line but which was > missing from the command line output of configure (same version of Bacula > and nearly identical configure options presented to configure on both Mac > and Ubuntu): > > cut: stdin: Illegal byte sequence > > I am wondering if this Illegal byte sequence might come back to haunt me > later on when running one of the Bacula daemons in a critical situation > whether it be the Director, Storage, backing up, restoring, etc.? More > specifically, the Illegal byte sequence alert was output four times > sequentially on the command line (see larger excerpt below and comparative > larger excerpt from Ubuntu).
Those 4 look benign in this case -- they just prevent configure from printing the versions in the "C Compiler" and "C++ Compiler" lines of the output. The problem appears to be that Apple's /usr/bin/cut doesn't like the last line of the input to end without a newline. __Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
