I have a tar archive created on an old Unixware machine using ISO8859-1 encoding. When I try to extract it under Macosx Lion, I experience a bit of weirdness with German umlauts. For instance: I o. Mac OS is more secure than Windows. Many of you might have heard that Mac Os is more secure than windows. But that’s not true. The market share of Mac is less than 10% which results in less malware and spyware attacks. Actually, the main reason behind this is iMac and Macbook. These two products running on Mac OS which is a bit expensive. This video will lead up to the next lessons in tutorials. That's why I'm recording this, even though it is simple. I am aware that there is a. Tar -c -f x.tar Test.txt When doing this: tar -tf x.tar I get the following list./.Test.txt Test.txt This is in the Terminal on Mac OS X Lion. Where does that./.Test.txt file come from? I don't see it when doing an ls -a. Upon inspecting the tar contents it seems to be some binary data, but I. Using the GUI zip tools are easy and user friendly, but if you want some more advanced options with better compression you can turn to the command line to make a tar and gzip archive. The syntax will be the same in Mac OS X as it is in Linux.
The first problem, before even running the configure script, is that one of the authors, François Pinard, puts his name in the source code in ISO-8859-1 encoding. It needs to be specified when generating gettext .po files. Edit the file po/Makefile.in.in, find the line that reads something like this:
And add another option,
--from-code=iso-8859-1 after --keyword=N_.Next, please make sure you have GNU sed installed, and make sure it's in the path searched before the stock /usr/bin/sed, which hangs on processing po/tar.pot file because of the alien character set.
Then, the configure script suffers a problem where .dSYM extension causes gcc to think that it's building a bundle. But it is not. It prevents configure script to detect many functions as present, which makes use of the lib/ compatibility functions. This leads to some catastrophic results (prototype not entirely compatible, conflicting qualifiers, etc.). The fix is to add ac_cv_exeext=' before the configure invocation:
