Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Parrot link failure imc_yyin_set/get

0 views
Skip to first unread message

Klaas-Jan Stol

unread,
Jan 16, 2006, 7:30:27 AM1/16/06
to perl6-i...@perl.org
Hi,
since yesterday, Parrot breaks during compiling, with the following output:

c++ -o miniparrot -L/usr/local/lib -Wl,-E compilers/imcc/main.o \
-Wl,-rpath=/home/klaas/parrot/blib/lib -L/home/klaas/parrot/blib/lib
-lparrot -lnsl -ldl -lm -lcrypt -lutil -lpthread -lrt -lgmp
src/null_config.o
compilers/imcc/main.o(.text+0xd85): In function `main':
compilers/imcc/main.c:494: undefined reference to `imc_yyin_set'
compilers/imcc/main.o(.text+0xe03):compilers/imcc/main.c:504: undefined
reference to `imc_yyin_set'
compilers/imcc/main.o(.text+0xfcf):compilers/imcc/main.c:551: undefined
reference to `imc_yyin_get'
compilers/imcc/main.o(.text+0x1125):compilers/imcc/main.c:580: undefined
reference to `imc_yyin_get'
compilers/imcc/main.o(.text+0x118b):compilers/imcc/main.c:591: undefined
reference to `imc_yyin_get'
collect2: ld returned 1 exit status
gmake: *** [miniparrot] Error 1
klaas@jerry:~/parrot$

imc.c is compiled, and the Makefile looks ok too.
regards,
klaas-jan

Klaas-Jan Stol

unread,
Jan 16, 2006, 7:42:09 AM1/16/06
to Klaas-Jan Stol, perl6-i...@perl.org
Klaas-Jan Stol wrote:

correction: it seems the file "imc.o" is not linked at the Parrot and
Miniparrot targets in the Makefile
(line ~800).

regards,
klaas-jan

Larry Wall

unread,
Jan 16, 2006, 5:48:57 PM1/16/06
to perl6-i...@perl.org
I just had the same problem, and chased it down to the fact that it was
using -L/usr/local/lib ahead of its own blib, so it was linking against
an old libparrot of some sort or other. I'm not sure what the correct
solution is, but as a workaround I deleted /usr/local/lib/libparrot*
and then it links.

Larry

Larry Wall

unread,
Jan 16, 2006, 5:55:09 PM1/16/06
to perl6-i...@perl.org
On Mon, Jan 16, 2006 at 02:48:57PM -0800, Larry Wall wrote:
: I just had the same problem, and chased it down to the fact that it was

Maybe because I had LD_LIBRARY_PATH=/usr/local/lib so that pugs would run?

Larry

Jonathan Worthington

unread,
Jan 16, 2006, 6:33:44 PM1/16/06
to Larry Wall, perl6-i...@perl.org
Ooh, nice catch - I'm to blame for the addition of those two functions but
(a) develop on Win32 where this likely wouldn't show up and (b) don't have
an installed Parrot anyway, thus meaning I've had a rather hard time trying
to find the problem. ;-)

Solution may be to have the full path to libparrot in the link line, to
ensure we get the right one. Thoughts, anyone?

Thanks,

Jonathan

Joshua Isom

unread,
Jan 16, 2006, 6:37:26 PM1/16/06
to Jonathan Worthington
What about the whole parrot/installable_parrot difference?
0 new messages