Problem building PropGCC on Slackware64-14.2

Buck Rogers

Hello!
Yes your reading that title correctly. I run that distribution here natively on both systems who also run Windows and its tools there.
This is from the efforts for building PropGCC first before the IDE:

config.status: creating po/Makefile.in
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing default-1 commands
config.status: executing bfd_stdint.h commands
config.status: executing default commands
make[4]: Nothing to be done for 'info'.
make[4]: Leaving directory '/usr/src/work0/build/binutils/bfd/po'
make[4]: Entering directory '/usr/src/work0/build/binutils/bfd'
make[4]: Nothing to be done for 'info-am'.
make[4]: Leaving directory '/usr/src/work0/build/binutils/bfd'
Makefile:1617: recipe for target 'info-recursive' failed
make[3]: *** [info-recursive] Error 1
make[3]: Leaving directory '/usr/src/work0/build/binutils/bfd'
Makefile:2505: recipe for target 'all-bfd' failed
make[2]: *** [all-bfd] Error 2
make[2]: Leaving directory '/usr/src/work0/build/binutils'
Makefile:837: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/usr/src/work0/build/binutils'
Makefile:162: recipe for target '/usr/src/work0/propgcc/../build/binutils/binutils-built' failed
make: *** [/usr/src/work0/propgcc/../build/binutils/binutils-built] Error 2
root@masterskywalker:/usr/src/work0/propgcc# 

And no erco managed robots were involved here, just an R2 unit.

Publison

Sorry, but your specific question is?

Buck Rogers

Publison wrote: »

Sorry, but your specific question is?

Oh right.... It is not a question, I'm reporting a problem.

But why are there a cluster of R2 style 'droids in your den watching the telly?

DavidZemon

did you compile this with parallel make jobs (the -j option)? Looks like the actual error message is further up in the output.

Buck Rogers

DavidZemon wrote: »

did you compile this with parallel make jobs (the -j option)? Looks like the actual error message is further up in the output.

No should I have? I looked at the content I'd checked out, and did not look into the logic of the make file. I then ran it and waited. What do I need to look for?

DavidZemon

Typically, yes I recommend running with parallel make jobs. It's faster
But when you run into errors, parallelism makes it much harder to find those errors, so I'm glad you didn't.

Anyway, I don't see anything in that log that is remotely helpful
Can you run make from /usr/src/work0/build/binutils/bfd and see what happens?

yeti

PropGCC-1.0.x || PropGcc-1.9.y ?

Install an old texinfo (I used 4.13a) first, e.g. built to live in "/opt/textinfo" and put "/opt/texinfo/bin" in front of your PATH while building PropGCC.

Buck Rogers

DavidZemon wrote: »

Typically, yes I recommend running with parallel make jobs. It's faster
But when you run into errors, parallelism makes it much harder to find those errors, so I'm glad you didn't.

Anyway, I don't see anything in that log that is remotely helpful
Can you run make from /usr/src/work0/build/binutils/bfd and see what happens?

Okay good idea. That is next.

Buck Rogers

yeti wrote: »

PropGCC-1.0.x || PropGcc-1.9.y ?

Install an old texinfo (I used 4.13a) first, e.g. built to live in "/opt/textinfo" and put "/opt/texinfo/bin" in front of your PATH while building PropGCC.

How so? This is on what Slackware64-14.2 supplied.

DavidZemon

it is in the instructions for building propgcc that an old version of texinfo is required. Here's the related docs: https://github.com/parallaxinc/propgcc-docs/blob/master/doc/Build.md

Buck Rogers

DavidZemon wrote: »

it is in the instructions for building propgcc that an old version of texinfo is required. Here's the related docs: https://github.com/parallaxinc/propgcc-docs/blob/master/doc/Build.md

I see your point, Slackware64 is shipping 6.1, and that's too new for this creation. But I'm going to try your first idea, and also recreate that directory on my Slackware32 system.