On 03/27/18 16:47, Elmar Haneke wrote:
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
> >> For some reason compile stopped with an error when including ICU.
> >> Therefore I did install ICU to /usr/local
> > What was the error?
> /Applications/Xcode.app/Contents/Developer/usr/bin/make -f
> ../gen/Makefile.refDatabases ref_databases
> rm -f -f msg.fdb
> echo create database
> 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
> > 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.
Which does not contain the few changes I added to make it build properly after
2.5.8 was released on Linux and
> 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
> An real debug-build did make the crash vanish therefore no further
> stacktrace.
>
> After switching to -O0 the problem is vanished, with -O1 it does fail
Right and thats the right thing to do - I found and fixed this for 2.5.8
release
- thats why I asked what optimisation level you were
> 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
>
> >> 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
On 21/03/2018 15:01, Paul Beach wrote:
> Email me privately
It's better that port efforts be done here in the list.
Adriano
--
Check out the vibrant tech community on one of the world's most
engaging tech sites,
> >> 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
>> 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
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
13 matches
Mail list logo
