On 2/6/06, Jack Howarth <[EMAIL PROTECTED]> wrote:
> Alex,
>The changes I have to sparky-py (a 3.111-1002 version) are simply
> to allow it to build in the 10.4 tree. These include...
>
> 1) the GCC variable was changed from 3.3 to 4.0
> 2) I eliminated the changes to the 'CXX= g+
Alex,
The changes I have to sparky-py (a 3.111-1002 version) are simply
to allow it to build in the 10.4 tree. These include...
1) the GCC variable was changed from 3.3 to 4.0
2) I eliminated the changes to the 'CXX= g++' section of
the patch to c++/Makefile
since the GCC
On 2/6/06, Jack Howarth <[EMAIL PROTECTED]> wrote:
> While adjusting my sparky-py packaging to build under the new 10.4 tree
> last night, I noticed I had optimized the compile with a '-mtune=970'. What
> is the recommended approach for handling this under 10.4 with the new
> Architecture list.
While adjusting my sparky-py packaging to build under the new 10.4 tree
last night, I noticed I had optimized the compile with a '-mtune=970'. What
is the recommended approach for handling this under 10.4 with the new
Architecture list. It would be nice if the Architecture list could be used
to
