Hi Lorenzo,
I agree with bash, but since echo -n isn't supported
in OS X 10.5.x, I cannot see how this could be a good
move. Especially since dropping echo -n didn't create
any side effects, but having it was creating an obviously
wrongly formatted .dylib name.
I can't understand why we have so different results.
How could I have been working with Mac OS X is there are so many
things to change now?
In my apps I use several .dylib created using hb-mkslib.
The 'echo -n' problem was in 'hb-func.sh', so plain
'hb-mkslib.sh' usage was not affected.
Another reason why you missed some of the problems, is
because you don't use universal binaries. The '-o '
problem only comes up if I use my custom C_USR/L_USR
universal flags.
Yet another reason for differences is that you use a
customized list of contribs (with some non-SVN ones),
while I use the plain default, which includes all but
a few contribs now.
Another cause of difference might be that you
reported success with make_gnu.sh, while the 'echo -n'
problem could only come up if you run 'make_gnu.sh install'.
You had the .dylib on your system somehow though, so
I don't know.
I still don't understand however, how couldn't you be
affected by 'echo -n' problem when creating the default
harbour.dylib... For some reason we might have something
different in our default shell settings.
I've now did a full svn export (r9100) and 'make_gnu.sh' +
'make_gnu.sh install', and the 'echo -n' problem is clearly
there. This is a Core 2 Duo Mac with the exact same Leopard
and now XCode 3.1 (final) that is on the other Mac. This
is a quite new machine, without any special tricks or tweaks
applied through the command line, so I'm 100% sure that
the shell is the Apple default.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
