Re: [patch] compile: Fix MinGW build [Re: [mingw rfc] Add mkdtemp to gdb/gnulib/]

Jan Kratochvil
2014-12-17T18:21:55Z

Hi Pierre,

On Tue, 16 Dec 2014 13:40:28 +0100, Pierre Muller wrote:
> which appeared as an attached file named 1.sql,
> which made it difficult to guess it was indeed the patch...

The mail has:
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline; filename=1

So there was no ".sql" extension; there was just no extension at all.

> To go a little bit further, I tried to use
> the compile command on the newly generated mingw32 GDB executable.
>
> using ./gdb ./gdb
> (with a minimal hello.c source code)
>
> <<<< (top-gdb) compile code hello.c
> returns
> >>>> The program must be running for the compile command to work.
> I am not sure why this restriction should apply.

I do not understand what it should do without running inferior. Or rather
I can understand it but that would be a functionality completely unrelated to
the current 'compile' functionality - which hooks into the running inferior.
I would find it rather confusing myself.

> (top-gdb) start
> Temporary breakpoint 3 at 0x40158a: file ../../../binutils-gdb/gdb/gdb.c, line 28.
> Starting program: E:\cygwin-32\home\Pierre\git\build\mult-mingw32\gdb\gdb.exe
> [New Thread 6572.0x4e0]
>
> Temporary breakpoint 3, main (argc=1, argv=0x3d4b30)
> at ../../../binutils-gdb/gdb/gdb.c:28
> (top-gdb) compile file hello.c
> Could not load libcc1.so: "libcc1.so": Le module spÃ©cifiÃ© est introuvable.
> (French meaning: "the specified module can't be found").
>
> So the mkdtmp is not the only problem
> for mingw compile support.

That is correct, you need to build gcc-5.0 which contains libcc1.so.
But that currently also will not work as it will get named libcc1.dll, you can
read more in:
https://sourceware.org/ml/gdb-patches/2014-12/msg00429.html

Thanks,
Jan