Jose E. Marchesi wrote:
> I think in this case it is better to not use the xalloc module in
> libpoke at all.
This looks feasible: There are not many references to functions like
xmalloc in libpoke.
pkl-ast.c:116: PKL_AST_STRING_POINTER (new) = xstrdup (str);
pkl-ast.c:131: PKL_AST_IDENTIFIER_P
> Hannes Domani wrote:
>> When I'm trying to (statically) link libpoke into gdb, I get the following
>> errors:
>>
>> ... gl-libpoke/xmalloc.c:44: multiple definition of `xmalloc'; alloc.o
>> ... gdb/alloc.c:49: first defined here
>>
>> Both gdb and gl-libpoke define these x* allocation functi
Hannes Domani wrote:
> When I'm trying to (statically) link libpoke into gdb, I get the following
> errors:
>
> ... gl-libpoke/xmalloc.c:44: multiple definition of `xmalloc'; alloc.o
> ... gdb/alloc.c:49: first defined here
>
> Both gdb and gl-libpoke define these x* allocation functions, and I'
Hello
When I'm trying to (statically) link libpoke into gdb, I get the following
errors:
c:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
C:/src/repos/poke/inst/lib/libpoke.a(libgnu_la-xmalloc.o): in function
`xmalloc':
C:\src\repos\poke\po
