facing issue while installing bison

170 views
Skip to first unread message

Billa Surendra

unread,
Dec 7, 2021, 12:44:20 AM12/7/21
to RISC-V SW Dev
Hi Everyone,

I am facing an issue while installing bison-3.7.4 on my RISC-V Linux distribution. Error details are given below. Please advise me, How I can resolve this issue.

Error:

  GEN      lib/sys/times.h
  GEN      lib/unistd.h
  GEN      lib/unistr.h
  GEN      lib/unitypes.h
  GEN      lib/uniwidth.h
  GEN      lib/wctype.h
  GEN      lib/wchar.h
echo 3.7.4 > .version-t && mv .version-t .version
  YACC     src/parse-gram.c
  LEX      src/scan-skel.c
make[1]: Leaving directory '/home/package_building/bison-3.7.4'
Updating ./doc/version.texi
/home/package_building/bison-3.7.4/./tests/bison: line 42: bison: No such file or directory
Can't open y.tab.[ch]: No such file or directory.
make: *** [Makefile:8329: src/parse-gram.c] Error 127


Thank you
Billa

Tommy Murphy

unread,
Dec 7, 2021, 7:25:10 AM12/7/21
to Billa Surendra, RISC-V SW Dev
There really isn't enough information to go on there in my opinion. You should probably attach a full build log and not just quote the last few lines. There could be some earlier error that triggers this as a secondary error. 

Also, isn't this maybe something that you should be asking about in the bison community?

Jim Wilson

unread,
Dec 7, 2021, 2:04:41 PM12/7/21
to Billa Surendra, RISC-V SW Dev
On Mon, Dec 6, 2021 at 9:44 PM Billa Surendra <billa.i...@gmail.com> wrote:
I am facing an issue while installing bison-3.7.4 on my RISC-V Linux distribution. Error details are given below. Please advise me, How I can resolve this issue.

/home/package_building/bison-3.7.4/./tests/bison: line 42: bison: No such file or directory

This looks like the first error.  Look at the file tests/bison.  What is on line 42?  Try running that command by hand.  Maybe it is trying to run a program that you haven't built yet.  Maybe it is trying to run a program that you built but isn't working for some reason, in which case you need to look at that binary for a problem.

You will get better error messages if you use a better shell.  Bash gives good error messages.  Some small shells like zsh don't.

Jim
 

Jim Wilson

unread,
Dec 7, 2021, 2:06:21 PM12/7/21
to Tommy Murphy, Billa Surendra, RISC-V SW Dev
On Tue, Dec 7, 2021 at 4:25 AM Tommy Murphy <tommy_...@hotmail.com> wrote:
There really isn't enough information to go on there in my opinion. You should probably attach a full build log and not just quote the last few lines. There could be some earlier error that triggers this as a secondary error. 

He is trying to build his own linux distro from scratch for Indian Shakti processors without the C extension.

Jim

Tommy Murphy

unread,
Dec 7, 2021, 3:01:34 PM12/7/21
to Jim Wilson, Billa Surendra, RISC-V SW Dev
> He is trying to build his own linux distro from scratch
> for Indian Shakti processors without the C extension.

Ok thanks. Not sure how people are supposed to know that from what was posted above though.

I think that the request for a more detailed build log still stands though .The partial snippet posted above isn't much to go on.

Khem Raj

unread,
Dec 7, 2021, 3:07:38 PM12/7/21
to Jim Wilson, Billa Surendra, RISC-V SW Dev
On Tue, Dec 7, 2021 at 11:04 AM Jim Wilson <jim.wil...@gmail.com> wrote:
>
> On Mon, Dec 6, 2021 at 9:44 PM Billa Surendra <billa.i...@gmail.com> wrote:
>>
>> I am facing an issue while installing bison-3.7.4 on my RISC-V Linux distribution. Error details are given below. Please advise me, How I can resolve this issue.
>>
>> /home/package_building/bison-3.7.4/./tests/bison: line 42: bison: No such file or directory
>
>
> This looks like the first error. Look at the file tests/bison. What is on line 42? Try running that command by hand. Maybe it is trying to run a program that you haven't built yet. Maybe it is trying to run a program that you built but isn't working for some reason, in which case you need to look at that binary for a problem.

maybe try with make -j1 or something like that to see if its not
related to parallelism.

>
> You will get better error messages if you use a better shell. Bash gives good error messages. Some small shells like zsh don't.
>
> Jim
>
>
> --
> You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.
> To view this discussion on the web visit https://groups.google.com/a/groups.riscv.org/d/msgid/sw-dev/CALNwTfxbYsto8UAS-8E2%3DEBrCaQbstTs2%3DON4R3fhqhp3uHkgw%40mail.gmail.com.

Bruce Hoult

unread,
Dec 7, 2021, 5:28:45 PM12/7/21
to Jim Wilson, Tommy Murphy, Billa Surendra, RISC-V SW Dev
As far as I'm aware, Shakti processors implement the C extension.

In a message on July 20 2019 Neel Gala wrote (in part):

As a member of the SHAKTI team, I would like to clear up quite a bit of mis-information in your last mail:
  1. All of our current cores support Compressed ISA.
  2. Our SDK supports all currently ratified extensions. The SDK is not meant for RISECREEK (the 22nm *test*-chip). 
  3. RISECREEK was a test-chip and continues to serve its purpose for us. It has had none of the grave-repurcussions you seem to claim.
I won't repeat the rest here as it gets into personal matters not technical. Those interested can read this and related messages at:



--
You received this message because you are subscribed to the Google Groups "RISC-V SW Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sw-dev+un...@groups.riscv.org.

Yan Titarenko

unread,
Dec 7, 2021, 7:35:12 PM12/7/21
to Bruce Hoult, we...@redhat.com, Jim Wilson, Tommy Murphy, Billa Surendra, RISC-V SW Dev
It is interesting that C and I classes of Shakti chips are capable of running https://github.com/apache/nifi-minifi-cpp , which has bison package as one of it's dependencies.
I am not sure about API compatibility/versioning but a fresh version of bison (if I am interpreting correctly - Tim Spann could explain in detail).
Unsure about I class - but M and higher classes might be capable of running https://nifi.apache.org/minifi/index.html

Wei Fu, do you have any progress in building/testing MiNiFi (C++ port)?

Yan

ср, 8 дек. 2021 г., 00:28 Bruce Hoult <br...@hoult.org>:

Jim Wilson

unread,
Dec 7, 2021, 8:48:49 PM12/7/21
to Bruce Hoult, Tommy Murphy, Billa Surendra, RISC-V SW Dev
On Tue, Dec 7, 2021 at 2:28 PM Bruce Hoult <br...@hoult.org> wrote:
As far as I'm aware, Shakti processors implement the C extension.


It doesn't explicitly mention Shakti.  I did mention Shakti a few posts later and wasn't contradicted.  I could be wrong about that detail.  But note that saying that current Shakti parts support C does not exclude the possibility that past parts did not, and some people might still be trying to use old parts.  The old stuff doesn't just disappear when new stuff comes out.  We are still getting gcc patches for the DEC Vax for instance.

Jim

Billa Surendra

unread,
Dec 8, 2021, 7:30:18 AM12/8/21
to Jim Wilson, RISC-V SW Dev
On Wed, Dec 8, 2021 at 12:34 AM Jim Wilson <jim.wil...@gmail.com> wrote:
On Mon, Dec 6, 2021 at 9:44 PM Billa Surendra <billa.i...@gmail.com> wrote:
I am facing an issue while installing bison-3.7.4 on my RISC-V Linux distribution. Error details are given below. Please advise me, How I can resolve this issue.

/home/package_building/bison-3.7.4/./tests/bison: line 42: bison: No such file or directory

This looks like the first error.  Look at the file tests/bison.  What is on line 42?  Try running that command by hand.  Maybe it is trying to run a program that you haven't built yet.  Maybe it is trying to run a program that you built but isn't working for some reason, in which case you need to look at that binary for a problem.

I have tried running the line 42 command by hand, it shows the error message like this
Error:

bash-5.1# $PREBISON "$abs_top_builddir/src/bison" ${1+"$@"} 2>"$stderr"
status=$?
bash: : No such file or directory

Billa Surendra

unread,
Dec 8, 2021, 7:33:41 AM12/8/21
to Tommy Murphy, RISC-V SW Dev
On Tue, Dec 7, 2021 at 5:55 PM Tommy Murphy <tommy_...@hotmail.com> wrote:
There really isn't enough information to go on there in my opinion. You should probably attach a full build log and not just quote the last few lines. There could be some earlier error that triggers this as a secondary error. 

Here I am attaching my config.log file.
config.log

Tommy Murphy

unread,
Dec 8, 2021, 8:00:39 AM12/8/21
to Billa Surendra, RISC-V SW Dev
> Here I am attaching my config.log file.

What about the build log?

Jim Wilson

unread,
Dec 8, 2021, 1:40:17 PM12/8/21
to Billa Surendra, RISC-V SW Dev
On Wed, Dec 8, 2021 at 4:30 AM Billa Surendra <billa.i...@gmail.com> wrote:
I have tried running the line 42 command by hand, it shows the error message like this
Error:

bash-5.1# $PREBISON "$abs_top_builddir/src/bison" ${1+"$@"} 2>"$stderr"
status=$?
bash: : No such file or directory

The shell variables have to be expanded.  With bash, you can use the -x option to echo commands as they are executed.  So run the script with -x to see what the actual command is, maybe modifying the makefile that runs the script to add the -x option.  Then once you know the actual command you can try running it by hand.  Meanwhile, I would suggest looking at src/bison.  You can use the "file" command to see what kind of file it is.  If it is a binary, and not statically linked, then try running "ldd" on it to see if the shared libraries and dynamic linker are OK.

Jim

Reply all
Reply to author
Forward
0 new messages