Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rakudo build fails when building NQPCORE.setting.pir starting with rakudo git tag 0fde4a1e375a26da8d7b511aafdb6174e934b757 #2790

Closed
p6rt opened this issue Jun 15, 2012 · 10 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Jun 15, 2012

Migrated from rt.perl.org#113660 (status was 'resolved')

Searchable as RT113660$

@p6rt
Copy link
Author

p6rt commented Jun 15, 2012

From @ronaldxs

I did a "git reset --hard 5a415c993343cea899c10e52abd0cc0d76a90b37"
which took me back just before the nqp change and I could build rakudo.

Builds after that fail for me and a few other people.

See IRC conversation here​:
http://irclog.perlgeek.de/perl6/2012-06-15#i_5730212

@p6rt
Copy link
Author

p6rt commented Jun 21, 2012

From @ronaldxs

So jnthn asked on IRC for someone to get the NQP commit that causes the
build to break and I think I got it

I set rakudo to build from rakudo commit
0fde4a1e375a26da8d7b511aafdb6174e934b757 and did Perl Configure.pl --
gen-parrot and watched the build failed as described. Then I started
from NQP commit 6be8ad9fd52fe4b769e6ba92a0e3de24b2f971e9 and did git --
reset hard for each commit after it in the nqp directory until it
failed.

For NQP commit ba8bf9311b31bacfeb0fcf368ccdf33bd375fd58 I can do a
"make clean; make" and nqp builds.

For NQP commit 35db04446b64c1d8f0a88e7579c2bbd0b3c5f2ea, the very next
one, "make clean; make" fails with the characteristic invoke() not
implemented error.

Ron

@p6rt
Copy link
Author

p6rt commented Jun 21, 2012

@ronaldxs - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Jun 21, 2012

From @jnthn

On 6/21/2012 23​:59, Ron Schmidt via RT wrote​:

So jnthn asked on IRC for someone to get the NQP commit that causes the
build to break and I think I got it

I set rakudo to build from rakudo commit
0fde4a1e375a26da8d7b511aafdb6174e934b757 and did Perl Configure.pl --
gen-parrot and watched the build failed as described. Then I started
from NQP commit 6be8ad9fd52fe4b769e6ba92a0e3de24b2f971e9 and did git --
reset hard for each commit after it in the nqp directory until it
failed.

For NQP commit ba8bf9311b31bacfeb0fcf368ccdf33bd375fd58 I can do a
"make clean; make" and nqp builds.

For NQP commit 35db04446b64c1d8f0a88e7579c2bbd0b3c5f2ea, the very next
one, "make clean; make" fails with the characteristic invoke() not
implemented error.
Thanks for that...sadly, knowing it was that commit doesn't immediately
give me a good idea of what is going wrong; it's one where the bootstrap
copy of the files is updated, but the stage 2 should really have failed
in previous revisions if there was breakage.

Please can I get platform details (32-bit or 64-bit, OS, compiler) from
anybody who has this issue? I'll dig a bit deeper and see if I can spot
anything that could be to blame between this bootstrap update and the
previous one.

Thanks,

Jonathan

@p6rt
Copy link
Author

p6rt commented Jun 21, 2012

From @jnthn

On 6/21/2012 23​:59, Ron Schmidt via RT wrote​:

So jnthn asked on IRC for someone to get the NQP commit that causes the
build to break and I think I got it

I set rakudo to build from rakudo commit
0fde4a1e375a26da8d7b511aafdb6174e934b757 and did Perl Configure.pl --
gen-parrot and watched the build failed as described. Then I started
from NQP commit 6be8ad9fd52fe4b769e6ba92a0e3de24b2f971e9 and did git --
reset hard for each commit after it in the nqp directory until it
failed.

For NQP commit ba8bf9311b31bacfeb0fcf368ccdf33bd375fd58 I can do a
"make clean; make" and nqp builds.

For NQP commit 35db04446b64c1d8f0a88e7579c2bbd0b3c5f2ea, the very next
one, "make clean; make" fails with the characteristic invoke() not
implemented error.
Oops, my previous reply didn't go to the address that makes an RT entry.
Here does again​:

Sadly, knowing it was that commit doesn't immediately give me a good
idea of what is going wrong; it's one where the bootstrap copy of the
files is updated, but the stage 2 should really have failed in previous
revisions if there was breakage.

Please can I get platform details (32-bit or 64-bit, OS, compiler) from
anybody who has this issue? I'll dig a bit deeper and see if I can spot
anything that could be to blame between this bootstrap update and the
previous one.

Additionally, I just pushed an additional bootstrap update, just in case
it helps, but I don't really see why it would. Feel free to try out
73ebd23 though.

Thanks,

Jonathan

@p6rt
Copy link
Author

p6rt commented Jun 22, 2012

From @ronaldxs

On Thu Jun 21 15​:33​:36 2012, jonathan@​jnthn.net wrote​:

Please can I get platform details (32-bit or 64-bit, OS, compiler)
from
anybody who has this issue?

32 bit Ubuntu 8.04 with gcc 4.2.4

20​:09​:57 ron-laptop​:~/rakudo/nqp$ getconf LONG_BIT
32
20​:15​:21 ron-laptop​:~/rakudo/nqp$ cat /etc/issue
Ubuntu 8.04.3 LTS \n \l
20​:11​:07 ron-laptop​:~/rakudo/nqp$ cat /proc/version
Linux version 2.6.24-24-generic (buildd@​palmer) (gcc version 4.2.4
(Ubuntu 4.2.4
-1ubuntu4)) #​1 SMP Tue Jul 7 19​:46​:39 UTC 2009
20​:12​:01 ron-laptop​:~/rakudo/nqp$ gcc -v
Using built-in specs.
Target​: i486-linux-gnu
Configured with​: ../src/configure -v --enable-languages=c,c
++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-
system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-
threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2
--program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --
enable-objc-gc --enable-mpfr --enable-targets=all --enable-
checking=release --build=i486-linux-gnu --host=i486-linux-gnu --
target=i486-linux-gnu
Thread model​: posix
gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
20​:12​:16 ron-laptop​:~/rakudo/nqp$

I'll dig a bit deeper and see if I can spot

anything that could be to blame between this bootstrap update and the
previous one.

Additionally, I just pushed an additional bootstrap update, just in
case
it helps, but I don't really see why it would. Feel free to try out
73ebd23 though.

Tried the new version 73ebd23 but no luck after make clean ; make

Ron

@p6rt
Copy link
Author

p6rt commented Jul 21, 2012

From @ronaldxs

flussence++ found a workaround by turning off parrot garbage collection
in the failing steps.

For example add -G to the line below in nqp/tools/build/Makefile.in

  $(PARROT) -library=$(STAGE0) $(STAGE0)/$(NQP_PBC) \
  --target=pir --output=$(STAGE1)/$(CORE_SETTING_PIR) \
  --module-path=$(STAGE1) --setting=NULL --no-regex-lib \
  $(STAGE1)/$(CORE_SETTING_NQP)

like :

  $(PARROT) -G -library=$(STAGE0) $(STAGE0)/$(NQP_PBC) \
  --target=pir --output=$(STAGE1)/$(CORE_SETTING_PIR) \
  --module-path=$(STAGE1) --setting=NULL --no-regex-lib \
  $(STAGE1)/$(CORE_SETTING_NQP)

and that's enough to get me running. flussence needed to add the -G
flag to one later step involving the core setting and stage 2.

Ron

1 similar comment
@p6rt
Copy link
Author

p6rt commented Jul 21, 2012

From @ronaldxs

flussence++ found a workaround by turning off parrot garbage collection
in the failing steps.

For example add -G to the line below in nqp/tools/build/Makefile.in

  $(PARROT) -library=$(STAGE0) $(STAGE0)/$(NQP_PBC) \
  --target=pir --output=$(STAGE1)/$(CORE_SETTING_PIR) \
  --module-path=$(STAGE1) --setting=NULL --no-regex-lib \
  $(STAGE1)/$(CORE_SETTING_NQP)

like :

  $(PARROT) -G -library=$(STAGE0) $(STAGE0)/$(NQP_PBC) \
  --target=pir --output=$(STAGE1)/$(CORE_SETTING_PIR) \
  --module-path=$(STAGE1) --setting=NULL --no-regex-lib \
  $(STAGE1)/$(CORE_SETTING_NQP)

and that's enough to get me running. flussence needed to add the -G
flag to one later step involving the core setting and stage 2.

Ron

@p6rt
Copy link
Author

p6rt commented Sep 1, 2012

From @moritz

This was hopefully fixed in nqp commit
c0fbe4d73f3189f0c0a349a0848ec7ff8d8249a1. Please re-open this ticket if
the newest version from git still shows the same error.

@p6rt
Copy link
Author

p6rt commented Sep 1, 2012

@moritz - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Sep 1, 2012
@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant