Installation issue #149

Ryabkomv · 2022-07-22T07:12:58Z

I tried OpenRAM and after comment decided to make clean installation.

My steps are:

sudo git clone https://github.com/VLSIDA/OpenRAM.git
cd OpenRAM//docker/
sudo make build

I got an error:

Step 7/74 : RUN apt-get install --no-install-recommends -y build-essential git ssh vim gosu autoconf automake libtool bison flex
 ---> Running in d0575047808a
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package build-essential
E: Unable to locate package git
E: Unable to locate package ssh
E: Unable to locate package vim
E: Unable to locate package gosu
E: Unable to locate package autoconf
E: Unable to locate package automake
E: Unable to locate package libtool
E: Unable to locate package bison
E: Unable to locate package flex
The command '/bin/sh -c apt-get install --no-install-recommends -y build-essential git ssh vim gosu autoconf automake libtool bison flex' returned a non-zero code: 100
docker tag  vlsida/openram-ubuntu:2022-07-22 vlsida/openram-ubuntu:latest
Error response from daemon: No such image: vlsida/openram-ubuntu:2022-07-22
make: *** [Makefile:11: build] Error 1

Is the error related to docker file, or this is my system issue? By the way, running in terminal
apt-get install --no-install-recommends -y build-essential git ssh vim gosu autoconf automake libtool bison flex
works without any issue.

googling suggested to install apt-transport-https but it already installed.

The text was updated successfully, but these errors were encountered:

mguthaus · 2022-07-22T12:51:28Z

This looks like a docker permissions problem because you built with sudo. I'd suggest deleting the image and building without sudo. You can add yourself to the docket group so that sudo isn't necessary.

Ryabkomv · 2022-07-22T13:16:44Z

Unfortunately it doesn't help. I follow the steps to run docker without sudo, now it runs docker hello-world successfully.

However with OpenRAM I still got the same error.

By the way, I installed all the tools in docker image for OpenLane with sudo successfully.

I appreciate if you can further help to resolve the issue.

mguthaus · 2022-07-22T13:37:29Z

What type of system is the host? Looking closer it could be a network problem too. I'm not an expert in docker so I'd suggest getting help through their forums.

Ryabkomv · 2022-07-22T13:42:02Z

I'm using Ubuntu 20.04.4 LTS
Ok, thank you. I just want to confirm that I'm doing the things right.

I just clone the repository, go to docker folder, and run make build right?

mguthaus · 2022-07-22T13:42:50Z

I build on the same all the time so I'm not sure what is going on...

mguthaus · 2022-07-22T14:23:57Z

Yes, those instructions are right.

mguthaus · 2022-07-22T14:26:51Z

What version of docker are you using?

Ryabkomv · 2022-07-22T14:27:43Z

Docker version 20.10.17, build 100c701

mguthaus · 2022-07-22T20:48:28Z

I'm using the exact version. I can't replicate your problem....

Ryabkomv · 2022-07-27T06:35:13Z

Looks like bad luck. I still have no idea what is going on.
Is there a way to install OpenRAM manually?

mguthaus · 2022-07-27T12:29:34Z

You can look through the versions of tools required in the Dockerfile and install those locally but this isn't recommended.

I have a number of people using the same configuration so I'm not sure what else it could be. If you can isolate it a bit more, maybe we can help.

Does it recur every time? Sometimes network problems are intermittent.

Can you manually apt install in a docker image?

Ryabkomv · 2022-07-28T08:09:36Z

I tried to install on virtual Ubuntu machine which uses different network. Process is still ongoing but passed the stage at which the error is occurred previously. However I notice some other errors during installation which doesn't interrupt the process. Hopefully it is not fatal.

Meantime, I have not found in documentation write mask support. Also some student work mentioned about such functionality in context of OpenRAM.

My interest to OpenRAM is to combine Tiny Rocket core with photonic device and pass it through the OpenLane flow to get GDSII. But Rocket core uses write mask functionality which might be not yet supported by OpenRAM?

mguthaus · 2022-07-28T12:51:03Z

What errors? Errors are usually a problem whereas warnings may not be.

The write_size option determines the write granularity and hence the write size. It is fully supported. You should join the slack for further usage questions.

Ryabkomv · 2022-07-28T22:35:56Z

Finally I got the following error:

make[3]: Leaving directory '/root/klayout/build-debug/gsiqt/qt5/QtMultimedia'
make[2]: Leaving directory '/root/klayout/build-debug/gsiqt/qt5'
make[1]: Leaving directory '/root/klayout/build-debug/gsiqt'
The command '/bin/sh -c ./build.sh -qt5 -debug -j 8  && cp -r bin-debug /usr/local/klayout' returned a non-zero code: 1
docker tag  vlsida/openram-ubuntu:2022-07-28 vlsida/openram-ubuntu:latest
Error response from daemon: No such image: vlsida/openram-ubuntu:2022-07-28
make: *** [Makefile:11: build] Error 1

mguthaus · 2022-07-28T23:30:41Z

I don't know what you ran to get that... Can you share the entire output?

mguthaus · 2022-07-28T23:37:20Z

Actually it looks like you just ran make build. It seems like you have a system problem if klayout is failing to build. It builds fine here... What is the error from it?

mguthaus · 2022-07-28T23:39:23Z

Oh, can you decrease the number of threads given to the klayout build? Right now it is trying to use 8. Do you have 8 cores?

Ryabkomv · 2022-07-29T06:22:04Z

I've noticed that virtual machine by default uses 1 core. So I changed the line in Dockerfile:

RUN ./build.sh -qt5 -debug -j 1 \
 && cp -r bin-debug /usr/local/klayout

to use single core, but still have the same error:

../../../src/rdb/rdb/gsiDeclRdb.cc: In function 'void gsi::tp_output_rdb(db::TilingProcessor*, const string&, rdb::Database&, rdb::id_type, rdb::id_type)':
../../../src/rdb/rdb/gsiDeclRdb.cc:1388:30: error: expected type-specifier
 1388 |   proc->output (name, 0, new rdb::TiledRdbOutputReceiver (&rdb, cell_id, category_id), db::ICplxTrans ());
      |                              ^~~
../../../src/rdb/rdb/gsiDeclRdb.cc:1386:95: warning: unused parameter 'rdb' [-Wunused-parameter]
 1386 | static void tp_output_rdb (db::TilingProcessor *proc, const std::string &name, rdb::Database &rdb, rdb::id_type cell_id, rdb::id_type category_id)
      |                                                                                ~~~~~~~~~~~~~~~^~~
../../../src/rdb/rdb/gsiDeclRdb.cc:1386:113: warning: unused parameter 'cell_id' [-Wunused-parameter]
 1386 | static void tp_output_rdb (db::TilingProcessor *proc, const std::string &name, rdb::Database &rdb, rdb::id_type cell_id, rdb::id_type category_id)
      |                                                                                                    ~~~~~~~~~~~~~^~~~~~~
../../../src/rdb/rdb/gsiDeclRdb.cc:1386:135: warning: unused parameter 'category_id' [-Wunused-parameter]
 1386 | static void tp_output_rdb (db::TilingProcessor *proc, const std::string &name, rdb::Database &rdb, rdb::id_type cell_id, rdb::id_type category_id)
      |                                                                                                                          ~~~~~~~~~~~~~^~~~~~~~~~~
At global scope:
cc1plus: warning: unrecognized command line option '-Wno-reserved-user-defined-literal'
make[2]: *** [Makefile:561: gsiDeclRdb.o] Error 1
make[2]: Leaving directory '/root/klayout/build-debug/rdb/rdb'
make[1]: *** [Makefile:48: sub-rdb-make_first] Error 2
make[1]: Leaving directory '/root/klayout/build-debug/rdb'
make: *** [Makefile:143: sub-rdb-make_first] Error 2
The command '/bin/sh -c ./build.sh -qt5 -debug -j 1  && cp -r bin-debug /usr/local/klayout' returned a non-zero code: 1
docker tag  vlsida/openram-ubuntu:2022-07-29 vlsida/openram-ubuntu:latest
Error response from daemon: No such image: vlsida/openram-ubuntu:2022-07-29
make: *** [Makefile:11: build] Error 1

I wonder why it says
No such image: vlsida/openram-ubuntu:2022-07-29
same as it was with the first machine.

mguthaus · 2022-07-29T13:02:59Z

You get that message because it doesn't complete building the docker image. The build command tries to create an image with today's date and if it succeeds, it tags it as the latest. I don't do any error checking if the build actually completes...

Ryabkomv · 2022-07-31T14:33:10Z

Ok. I have reinstalled everything from scratch. I set 4 cores on my virtual machine and started installation.
I get error at the same step.

mv -f libklayout_QtMultimedia.so.0.27 ../../../../build-debug/libklayout_QtMultimedia.so.0.27
make[3]: Leaving directory '/root/klayout/build-debug/gsiqt/qt5/QtMultimedia'
make[2]: Leaving directory '/root/klayout/build-debug/gsiqt/qt5'
make[1]: Leaving directory '/root/klayout/build-debug/gsiqt'
The command '/bin/sh -c ./build.sh -qt5 -debug -j 4  && cp -r bin-debug /usr/local/klayout' returned a non-zero code: 1
make: *** [Makefile:10: build] Error 1

I have no idea why this is happening. I had issue on 2 different machines. If nobody experienced such issue before seems my case is very specific.

And I do not think klayout itself is an issue, because I have installed it successfully both as a separate installation and in the scope of docker image with OpenLane.

mguthaus · 2022-07-31T14:36:43Z

Can you find more information on why klayout failed to build? The return code alone isn't sufficient to understand why and fix it.

I've also installed this on at least 3 machines, my students on all of their machines, and none of them did this.

Ryabkomv · 2022-07-31T14:54:50Z

I'm not and expert to be able to fix the build flow.
If you can suggest how to attack the problem I will check.

mguthaus · 2022-07-31T15:09:57Z

Can you include the whole output as an attachment?

Ryabkomv · 2022-07-31T15:33:41Z

ok, thanks. I have started the installation with redirection of the output to the file. Once finished I will share the file.

Ryabkomv · 2022-08-01T18:41:17Z

Here is a file

mguthaus · 2022-08-01T18:45:46Z

It looks like you might have some permission problems:

docker build -t vlsida/openram-ubuntu:2022-07-31 -f Dockerfile . | tee -i openram-ubuntu.log
tee: openram-ubuntu.log: Permission denied

Do you not have permissions on your local directory?

Also, do you not have permissions to write /usr/local? Maybe that is the problem...

mguthaus · 2022-08-01T18:57:21Z

Can you change this line to two lines?

RUN ./build.sh -qt5 -debug -j 8 \
   && cp -r bin-debug /usr/local/klayout

like this:

  RUN ./build.sh -qt5 -debug -j 8
  RUN cp -r bin-debug /usr/local/klayout

Does it fail on the second line? It seems to be completing the build in your output.

mguthaus · 2022-08-01T20:56:37Z

Can you send me the stdout in openram-ubuntu.log when you figure out the permissions problem?

Ryabkomv · 2022-08-02T13:38:51Z

With suggested split:

RUN ./build.sh -qt5 -debug -j 8
RUN cp -r bin-debug /usr/local/klayout

installation has passed this stage, but failed to install ngspice due to failure in name resolution of git://git.code.sf.net/p/ngspice/ngspice . Is it the Issue from my side only?
I have changed the repository to https://github.com/ngspice/ngspice

with that the installation has finished.

I was also able to compile the simple memory example from the main page.

Will check further with sky130 pdk

mguthaus · 2022-08-02T15:33:14Z

Splitting the commands wasn't a suggested fix, it was supposed to help me understand what was the error. Whether it was a build problem or a copy problem. The fact that it passes with that makes me believe there is something very unstable in your system or setup.

What about the initial permissions issue? Did you fix that? Why don't you have permissions to write the local directory?

The network problem is due to an unstable network. Try again and/or try on a better network.

Ryabkomv · 2022-08-02T15:46:10Z

I'm not sure if permission issues are still there. The mentioned folders are owned by root. So I made installation with sudo. Network during installation was different, but I think both of networks should have similar restrictions. I also wonder why the split of the commands allow to overcome the issue. I remember some suggestions at stackoverflow to split commands in docker file. Anyway, I will check if I can compile needed memory using sky130.

…

On Tue, 2 Aug 2022, 18:33 Matt Guthaus, ***@***.***> wrote: Splitting the commands wasn't a suggested fix, it was supposed to help me understand what was the error. Whether it was a build problem or a copy problem. The fact that it passes with that makes me believe there is something very unstable in your system or setup. What about the initial permissions issue? Did you fix that? Why don't you have permissions to write the local directory? The network problem is due to an unstable network. Try again and/or try on a better network. — Reply to this email directly, view it on GitHub <#149 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5L42LATYRPAXJWGUI57LDVXE5UNANCNFSM54KIO6HQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

mguthaus · 2022-08-02T17:22:06Z

That ngspice repo hasn't been updated since 2015. It may not work...

Ryabkomv · 2022-08-02T18:04:44Z

Oh, but I can't access original repo from any network. Will try to reinstall with up to date repo later.
As of now I was able to compile SRAM with default library scn4m_subm and

# Data word size
word_size = 32
# Number of words in the memory
num_words = 1024

However when I change library to tech_name = "sky130"

I got the following error:

** Start: 08/02/2022 17:29:46
Technology: sky130
Total size: 32768 bits
Word size: 32
Words: 1024
Banks: 1
Write size: None
RW ports: 1
R-only ports: 0
W-only ports: 0
DRC/LVS/PEX is only run on the top-level design to save run-time (inline_lvsdrc=True to do inline checking).
DRC/LVS/PEX is disabled (check_lvsdrc=True to enable).
Characterization is disabled (using analytical delay models) (analytical_delay=False to simulate).
Only generating nominal corner timing.
ERROR: file sram_config.py: line 132: Invalid number of cols including rbl(s): 257. Total cols must be divisible by 2
Traceback (most recent call last):
  File "/home/maxim/OpenRAM/compiler/openram.py", line 54, in <module>
    c = sram_config(word_size=OPTS.word_size,
  File "/home/maxim/OpenRAM/compiler/modules/sram_config.py", line 44, in __init__
    self.compute_sizes()
  File "/home/maxim/OpenRAM/compiler/modules/sram_config.py", line 95, in compute_sizes
    self.recompute_sizes()
  File "/home/maxim/OpenRAM/compiler/modules/sram_config.py", line 132, in recompute_sizes
    debug.error("Invalid number of cols including rbl(s): {}. Total cols must be divisible by {}".format(self.num_cols + num_ports + self.num_spare_cols, self.array_col_multiple), -1)
  File "/home/maxim/OpenRAM/compiler/debug.py", line 47, in error
    assert return_value == 0
AssertionError

I might did something stupid, because I just changed the pdk, although config is the same to this

my full config is

# Data word size
word_size = 32
# Number of words in the memory
num_words = 1024

# Technology to use in $OPENRAM_TECH
tech_name = "sky130"

# You can use the technology nominal corner only
nominal_corner_only = True
# Or you can specify particular corners
# Process corners to characterize
# process_corners = ["SS", "TT", "FF"]
# Voltage corners to characterize
# supply_voltages = [ 3.0, 3.3, 3.5 ]
# Temperature corners to characterize
# temperatures = [ 0, 25 100]

# Output directory for the results
output_path = "temp"
# Output file base name
output_name = "sram_{0}_{1}_{2}".format(word_size,num_words,tech_name)

# Disable analytical models for full characterization (WARNING: slow!)
# analytical_delay = False

mguthaus · 2022-08-02T18:09:43Z

Take a look at the example configs in:
https://github.com/VLSIDA/OpenRAM/blob/69d5731d6778f4b87bc7517ac06b6d28094abb67/macros/configs/sky130_sram_2kbyte_1rw_32x512_8.py

sky130 has certain requirements on the number of columns and rows. Since we use a replica timing column, there must be a dummy column added to make the number even.

EDIT: Updated to use a single port SRAM which needs the even number.

mguthaus · 2022-08-02T18:10:37Z

I'm not sure what to say about the ngspice repo. Their official distribution is via sourceforge (sf.net)... Can you access this information page?
https://ngspice.sourceforge.io/gitaccess.html

Ryabkomv · 2022-08-02T18:13:09Z

yes, this page is accessible!

mguthaus · 2022-08-02T18:24:32Z

But it says where to get the git repo which is unaccessible to you. Maybe you should contact them?

Ryabkomv · 2022-08-02T18:28:41Z

Thanks, I will try. Actually, when I first tried manual installation of the OpenLane, some of the repos were at sourceforge, and were inaccessible to me as well. I saw some people also experienced issues with sourceforge. I will contact them. вт, 2 авг. 2022 г. в 21:24, Matt Guthaus ***@***.***>:

…

But it says where to get the git repo which is unaccessible to you. Maybe you should contact them? — Reply to this email directly, view it on GitHub <#149 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5L42LGCCVNNCJSXLDTBGTVXFRWZANCNFSM54KIO6HQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

mguthaus closed this as completed Jul 22, 2022

Installation issue #149

Installation issue #149

Comments

Ryabkomv commented Jul 22, 2022

mguthaus commented Jul 22, 2022

Ryabkomv commented Jul 22, 2022

mguthaus commented Jul 22, 2022

Ryabkomv commented Jul 22, 2022

mguthaus commented Jul 22, 2022

mguthaus commented Jul 22, 2022

mguthaus commented Jul 22, 2022

Ryabkomv commented Jul 22, 2022

mguthaus commented Jul 22, 2022

Ryabkomv commented Jul 27, 2022

mguthaus commented Jul 27, 2022

Ryabkomv commented Jul 28, 2022 • edited Loading

mguthaus commented Jul 28, 2022

Ryabkomv commented Jul 28, 2022

mguthaus commented Jul 28, 2022

mguthaus commented Jul 28, 2022

mguthaus commented Jul 28, 2022

Ryabkomv commented Jul 29, 2022

mguthaus commented Jul 29, 2022

Ryabkomv commented Jul 31, 2022

mguthaus commented Jul 31, 2022

Ryabkomv commented Jul 31, 2022

mguthaus commented Jul 31, 2022

Ryabkomv commented Jul 31, 2022

Ryabkomv commented Aug 1, 2022

mguthaus commented Aug 1, 2022

mguthaus commented Aug 1, 2022

mguthaus commented Aug 1, 2022

Ryabkomv commented Aug 2, 2022

mguthaus commented Aug 2, 2022

Ryabkomv commented Aug 2, 2022 via email

mguthaus commented Aug 2, 2022

Ryabkomv commented Aug 2, 2022

mguthaus commented Aug 2, 2022 • edited Loading

mguthaus commented Aug 2, 2022

Ryabkomv commented Aug 2, 2022

mguthaus commented Aug 2, 2022

Ryabkomv commented Aug 2, 2022 via email

Ryabkomv commented Jul 28, 2022 •

edited

Loading

mguthaus commented Aug 2, 2022 •

edited

Loading