Internal error: Link failed: Building target <common-dylan>timers.o

[fraya]

Hi guys, I'm slowly learning OpenDylan.

The firsts weeks everything was ok, and I could make small tests. But when I tried to clone opendylan's repo I was under a firewall and I couldnt 'git clone' recursively. Now that this problem is solved and I try to use other libraries I have this error:

> Build of 'polynomial-tests' completed
> Linking polynomial-tests
>
< Internal error: Link failed: Building target <common-dylan>timers.o: "gcc -c -o "/home/fraya/src/dylan/_build/build/polynomial-tests/../common-dylan/timers.o" -w -g -O2 > -DOPEN_DYLAN_PLATFORM_UNIX -DOPEN_DYLAN_PLATFORM_LINUX -DOPEN_DYLAN_ARCH_X86_64 -fPIC -DGC_USE_BOEHM -DGC_THREADS  -I/opt

> /opendylan-2014.1/include "/home/fraya/src/dylan/_build/build/polynomial-tests/../common-dylan/timers.c"" failed with return status 1
> Exiting with return code -1

I tried to compile the 'binary-data' repository with same luck.

My configuration is:

.bashrc

> # OPENDYLAN
> export OPENDYLAN_HOME=/opt/opendylan-2014.1
> export OPEN_DYLAN_USER_REGISTRIES=/home/fraya/src/dylan/opendylan/sources/registry:/home/fraya/src/dylan/registry

polynomial/tests/library.dylan

> Module: dylan-user
> Synopsis: Polynomial test suite
> Copyright: See LICENSE in this distribution for details.
>
> define library polynomial-tests
>  use common-dylan;
>  use testworks;
>  use polynomial;
> end;
>
> define module polynomial-tests
>  use common-dylan;
>  use testworks;
>  use polynomial;
> end;

Can you help me? Thanks in advance

[fraya]

Sorry, I think I resolve it. It's the inclusion in 'OPEN_DYLAN_USER_REGISTRIES' of opendylan registry.

> OPEN_DYLAN_USER_REGISTRIES=/home/fraya/src/dylan/opendylan/sources/registry:/home/fraya/src/dylan/registry

now is

> OPEN_DYLAN_USER_REGISTRIES=/home/fraya/src/dylan/registry

[peter...@gmail.com]

On Sunday, 25 November 2018 15:13:16 UTC, fraya wrote:

Sorry, I think I resolve it. It's the inclusion in 'OPEN_DYLAN_USER_REGISTRIES' of opendylan registry.

Glad to hear you've solved it yourself, I was feeling a bit guilty I hadn't had time to look at it.

It's worth knowing because the cause of the error is not obvious given the error message.

Pete