Hi Przemek, Lorenzo,

/bin/sh --help

I can't confirm these problems.
I can build rev. 9079 without any problem.

/bin/bash --version returns:
GNU bash, version 3.2.17(1)-release (powerpc-apple-darwin9.0)

1) My shell versions:
silver:harbour vszakats$ /bin/bash --version
GNU bash, version 3.2.17(1)-release (powerpc-apple-darwin9.0)
Copyright (C) 2005 Free Software Foundation, Inc.

silver:harbour vszakats$ /bin/sh --version
GNU bash, version 3.2.17(1)-release (powerpc-apple-darwin9.0)
Copyright (C) 2005 Free Software Foundation, Inc.
silver:harbour vszakats$

Still the two binaries are a bit different, see the linked
article in my previous mail.

2) I'm using Mac OS X 10.5.4 with all patches on a PPC G4.

XCode is 3.1 (Beta)
Xcode IDE: 1037.0
Xcode Core: 1036.0
ToolSupport: 1024.0

3) Snippet from the man page of sed (emphasis from me):
--
Normally, sed cyclically copies a line of input, not including its terminating newline character, into a pattern space, (unless there is something left after a ``D'' function), applies all of the commands with addresses that select that pattern space, copies the pattern space to the standard output, __appending a newline__, and deletes the
     pattern space.
--

4) I have no errors/warnings whatsoever (besides the ones mentioned
by Lorenzo, plus one known sqlite3.c warning), if you start a plain
./make_gnu.sh. But notice that this path won't trigger hb-func.sh
(responsible for .dylib, hbfm stuffs), and also won't create a tar.gz,
so the sed/gzip problem is also not touched.

This explains why Lorenzo have no problem, while I do.

Also notice, that for binary distributions, one must use make_tgz.sh.

5) I've tried to run make_tgz.sh without my universal binary extra
flags, and this way .dylib _got_ created and included in the .inst.sh/.tar.gz
file, this is fine. Also, the hbextern and hbfm errors vanished, too.
So we can conclude that somehow hb-func.sh triggered .dylib, hbextern
and hbfm stuffs are broken when trying to create a unibin release,
and/or I'm missing something/doing something wrong when I use these
envvars to trigger the unibin build:
--
export C_USR="-arch -i386 -arch ppc"
export L_USR="$C_USR"
--

Sorry for the information flood / overdose.

Brgds,
Viktor

_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to