Errors are worst when there is no message explaining why
it could not copy it.
(libtool 2.2.6)
# libtoolize --copy --force --verbose
libtoolize: putting auxiliary files in `.'.
libtoolize: can not copy `/usr/share/libtool/config/ltmain.sh' to `./'
libtoolize: Not copying `m4/argz.m4', libltdl no
On 07/24/2009 11:25 AM, Jan Engelhardt wrote:
Hi,
when one has a program that does something like
if(strcmp(argv[0], "gunzip") == 0)
uncompress();
else
compress();
and this program also uses a libtool library, then the - lets use this
example - just-built "gzip" file will be a
Hello Jan,
* Jan Engelhardt wrote on Tue, Jul 28, 2009 at 03:14:01PM CEST:
> Errors are worst when there is no message explaining why
> it could not copy it.
True. Also, users come up with broken systems that one could never
think of. ;->
So, to avoid further surprises, please ensure you have
> #ifdef _WIN32
> executable_name = strrchr (argv[0], '\\');
Bzzt. You have to use the multi-byte character set aware _mbschr() and
_mbsrchr() functions from to search for backlashes (or
slashes) in "narrow" (char *) system code page strings (for instance,
file names) on Windows. The East Asian
