maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #04821
Re: what compiler should i use when building mariadb?
I suspect that we have a tool chain problem here at tokutek.
We can build maria 5.5 with gcc 4.7.1 and binutils 2.22 on a centos
6.2 machine (we built gcc and binutils ourselves).
We can not build it on a centos 5.8 machine with the same gcc 4.7.1
and binutils 2.22 (we also built gcc and binutils ourselves).
So, we are doing additional experiments to find the root cause of this problem.
Thanks for information about successful maria 5.5 builds with gcc 4.7.1.
On Mon, Aug 6, 2012 at 7:46 AM, Kristian Nielsen
<knielsen@xxxxxxxxxxxxxxx> wrote:
>>>>>>> "Rich" == Rich Prohaska <prohaska@xxxxxxxxxxx> writes:
>
>> Rich> hello,
>> Rich> we have been using gcc 4.4 to build mysql and mariadb successfully.
>> Rich> however, when we tried to use gcc 4.7.1 to build mariadb-5.5.25, we
>> Rich> hit this problem:
>>
>> Rich> /home/tokubuild/build-tokudb-46462/mariadb-5.5.25-tokudb-46462-linux-x86_64-build/mariadb-5.5.25-tokudb-46462-src/mysys/my_context.c:
>> Rich> Assembler messages:
>> Rich> /home/tokubuild/build-tokudb-46462/mariadb-5.5.25-tokudb-46462-linux-x86_64-build/mariadb-5.5.25-tokudb-46462-src/mysys/my_context.c:207:
>> Rich> Error: CFI instruction used without previous .cfi_startproc
>
> CFI is used to emit DWARF2 stack unwinding information. This is supposed to be
> used in gcc versions from 4.4 on. But from the error message, it seems that
> your GCC 4.7.1 did not emit such information.
>
> I was not able to reproduce the problem. I have GCC 4.7.1. I built like this:
>
> cmake -DWITH_EMBEDDED_SERVER=1 -DWITH_SSL=system .. && make -j8 -k
>
> I suspect that you are building in some special way that triggers this
> problem.
>
> Can you supply the full cmake and make commands you used to build to get this
> problem?
>
> Also it would be useful for me to get the full gcc command line used to build
> my_context.c when it fails like this (use `make VERBOSE=1`).
>
> And please provide full output of `gcc --version`.
>
> It would be nice to find out what makes this fail and get it fixed, so others
> will not get the same failures...
>
> - Kristian.
Follow ups
References