Matthew Lye wrote:
> > Are still any issues with build.sh?
> No, it appears to be finding everything and working fine now. Thanks.
Does it still pick -O instead of -O2 if you specify no such flag yourself?
If yes, what's the output of
gcc --version
?
--
Christian
--
On 15-Aug-07, at 1:19 PM, Christian Biere wrote:
>> Are still any issues with build.sh?
On 16 Aug 2007, [EMAIL PROTECTED] wrote:
> No, it appears to be finding everything and working fine now.
> Thanks.
Can you give us a command line that you use for an example on how to
build on Darwin, maybe
On 15-Aug-07, at 1:19 PM, Christian Biere wrote:
> Christian Biere wrote:
>>> uname -s gains "Darwin."
>>> Without the period.
>
> Ok, build.sh passes -D so=dylib to Configure in this case then.
...
> The ordering should be correct now.
>
> Are still any issues with build.sh?
No, it appears to b
Matthew Lye wrote:
> Well, apparently someone rolled a natural 20 on precog.
>
> Currently spotted problems:
> 1)cflags are defined as the "additional" cc flags, rather than the
> optimizer/debugger flags, which are now "-O". Not sure what effect
> this will have.
It should only use -O i
Well, apparently someone rolled a natural 20 on precog.
Currently spotted problems:
1) cflags are defined as the "additional" cc flags, rather than the
optimizer/debugger flags, which are now "-O". Not sure what effect
this will have.
2) my little attempt to hack the "$so" variable
