> It will build, but deprecated implies that you might have an issue trying to
> run it on 10.7 or 10.8... In any event without the fix for the _clock_gettime
> function
> in configure.in your code will only run on 10.12 and no OS version below it.
>
>>> By default the build is 64bit... you have
> Where did you get the code you are using from? Ideally you should have got it
> from github B2_5_Release.
It's not from Github but official tarbal fom firebirdsql.org.
> -mmacosx-version-min=10.7 is now -mmacosx-version-min=10.9 libstdc++
> has been deprecated.
I'm going to change that on n
> Do a debug build, enable crash dumps, post the full back trace from the
> crashes.
The first try to get an Debug-build did fail, it did build normal. The
Stacktrace is
> (lldb) thread backtrace all
> * thread #1, stop reason = signal SIGSTOP
> * frame #0: 0x00011a495aef
> fbintl.dylib`C
>> After compiling firebird 2.5.8 on latest MacOS I run into problem that
>> win1252 charset seems to crash software when using embedded to open
>> local database file.
>>
>> When charset is specified on connect crash does happen there.
>> When connect is done using UTF8 crash does happen as soon
After compiling firebird 2.5.8 on latest MacOS I run into problem that
win1252 charset seems to crash software when using embedded to open
local database file.
When charset is specified on connect crash does happen there.
When connect is done using UTF8 crash does happen as soon as an table
define
> You should correct those values in v1.5 before upgrading to v2.x.
I did find an different way:
It is possible to wipe out defective data within FB2.5:
UPDATE t SET f=null WHERE EXTRACT(year FROM f)<1859
Using EXTRACT does also allow to read defective data to let you see what
is going
On FB 2.5 invalid data in Timestamp fields does raise an error (even on
reading).
On FB 1.5 the invalid data was stored without any problems.
How can I avoid that error on reading data which has been stored by FB 1.5?
Elmar
--
