Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 17397
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

creating library from command line: dbCreateLib cannot find cds.lib

meland

I am wanting to kick off SKILL scripts from the command line, and I've quickly run into an issue. I've attempted this in 6.1.5 and 6.1.7.


I have a SKILL script called 'hello.il' which all it has is

lib_id = dbCreateLib("hello", "cadence_libs/hello")

I kick cadence off with the below command

virtuoso -nograph -restore /path_to_file/hello.il

I get the output

*WARNING* Couldn't get an exclusive lock for "/path_to_run_dir/cds.lib.new"
    Permission denied
*WARNING* (DB-270165): dbCreateLib: cannot create library 'hello'  because ddCreateLib: Could not open '/path_to_run_dir/cds.lib.new' for output.

This creates a file called 'cds.lib.new' in the run directory, but does not add anything to it and does not add anything (Specifically wanting a DEFINE for hello) into the cds.lib file. It does create the cadence_libs/hello directory though ( I do not know if it is correct). Just doesn't update the cds.lib.

In the manual for ddCreateLib it says it bases the cds.lib file off of 'ddUpdateLibList'. Running ddUpdateLibList() passes fine. I've also tried using ddSetForcedLib and the command line flag -cdslib to force it to "cds.lib".

I do not have this issue if I try running the script from the ciw.

If these are just warnings I could in theory just put the names into the cds.lib file after this script, but it would be cleaner if it were through cadence.

Any ideas as to what is going on?


Thanks

-Matthew

  • Matthew,

    My guess is that you can't be running from the same directory or the user is different. The only way I think you can get this error is if the working directory isn't writeable for the user running the code. When you create a library using ddCreateLib (or ddCreateLib) it will create a new cds.lib file in  temporary file (cds.lib.new) and then rename it to cds.lib. This is done to avoid accidentally corrupting the cds.lib if the disk is full (for example); many of the saving operations in OA and Virtuoso work this way - create a new file, then rename the old and new files.

    I can get exactly the same error if the directory I'm in isn't writable.

    Regards,

    Andrew.

  • You're right again. I had all the proper permissions, but my session was in some weird state where it selectively didn't give me access to things I should have.


    I did 'newgrp this_group' on the terminal and it started working... Thanks for the help and the insight into what's going on behind the hood.

    -Matthew

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.