ADS 2009 in Debian - start up

[Vigort]

Hi!
Who can faced installation ADS in Debian? Itself ADS it was installed without problems. But when you run ads produces an error
~/Program Files/ADS2009U1/bin $./ads
Agilent Technologies
Advanced Design System
./ads [8]:.: eesofboot.sh: cannot open [There is no such file or the directory]

The file eesofboot.sh bin is present at a directory. In what there can be a problem?
Help me, please.

 

[kokabanga]

Hey there!

Can you pls tell me where I can get ADS 2009 from?

 

[Vigort]

In http://www.home.agilent.com/agilent/download.jspx?nid=-34346.0&cc=US&lc=eng&pageMode=DL you can downloads free trial version

 

[Filip]

Priviliges? (try: chmod 555 eesoftboot.sh)

 

[Vigort]

No. This file is present also access (privileges) for it complete.

 

[mrflibble]

Hello Vigort,

I also just now decided to give ADS2009 a try, which is why I did a search on here about it. It also happens to be on debian. For it to start I needed to do 2 things. First make sure the HPEESOF_DIR environment variable is set to the install dir of ads2009. And 2nd add it's bin directory to your path.

So in your case something like:

~ $ cd  "~/Program Files/ADS2009U1"
~/Program Files/ADS2009U1 $ export HPEESOF_DIR=$(pwd)
~/Program Files/ADS2009U1 $ export PATH=${HPEESOF_DIR}/bin:${PATH}

I also noted that you have spaces in your directory name. Please be aware that on *nix that sometimes gives problems with programs and especially shell scripts. And I see ads itself is a korn shell script, so just beware.

Alright, now all I need is that trial license.

Anyway, hope this helps you.

 

[Vigort]

Hello Vigort,
I also just now decided to give ADS2009 a try, which is why I did a search on here about it. It also happens to be on debian. For it to start I needed to do 2 things. First make sure the HPEESOF_DIR environment variable is set to the install dir of ads2009. And 2nd add it's bin directory to your path.

Hello, mrflibble!
Thanks for the information, but for me are a question:
Where to me to look this variable HPEESOF_DIR: in install or in the installed directory?

I also noted that you have spaces in your directory name. Please be aware that on *nix that sometimes gives problems with programs and especially shell scripts. And I see ads itself is a korn shell script, so just beware.

Thanks, I will consider on the future.

Alright, now all I need is that trial license.

If it is really necessary to you, that I think that this question can be solved ;-)

P.S. You install "Complete" or "Custom" (with FlexNET files) versions ADS?

 

[mrflibble]

Where to me to look this variable HPEESOF_DIR: in install or in the installed directory?

I used the installer to install in this directory: /opt/ads2009u1

Then I just did the following:

export HPEESOF_DIR=/opt/ads2009u1
export PATH=/opt/ads2009u1/bin:$PATH
ads

If it is really necessary to you, that I think that this question can be solved ;-)

P.S. You install "Complete" or "Custom" (with FlexNET files) versions ADS?

I'm always interested to hear about potential solutions. Especially when this potential solution works in linux.

To answer your question, I did a custom install, complete with the flexnet files.

Added after 8 minutes:

To be more precise, I put it in a shell script called ads2009.sh like this:

#!/bin/sh
#
# Agilent ADS 2009 Update 1
#
export HPEESOF_DIR=/opt/ads2009u1
export PATH=${HPEESOF_DIR}/bin:${PATH}
ads $@

Then I can just call ads2009.sh from commandline, and it will even pass any needed argument.

hope that helps!

 

[Vigort]

I use longer script:
1. I extend in.bashrc:

HPEESOF_DIR=/home/Programs/ADS2009U1 
PATH=.:$HPEESOF_DIR/bin/linux_x86_64:$HPEESOF_DIR/bin:$PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/adsptolemy/lib.linux_x86:$LD_LIBRARY_PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/lib/linux_x86:$LD_LIBRARY_PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/adsptolemy/lib.linux_x86_64:$LD_LIBRARY_PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/lib/linux_x86_64:$LD_LIBRARY_PATH 
SIMARCH=linux_x86_64

export HPEESOF_DIR

(It is recommended Agilent for 64 bit Linux, but thus loadtime slightly increases)

2. And a simple script for start ADS:

#!/bin/sh
#
#Startup script for ADS2006A
cd /home/igor/Programs/ADS2009U1/bin
ads

And that laziness each time to come into house directory ADS.

I will try your variant, can start will faster.

 

[mrflibble]

I use longer script:
1. I extend in.bashrc:

HPEESOF_DIR=/home/Programs/ADS2009U1 
PATH=.:$HPEESOF_DIR/bin/linux_x86_64:$HPEESOF_DIR/bin:$PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/adsptolemy/lib.linux_x86:$LD_LIBRARY_PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/lib/linux_x86:$LD_LIBRARY_PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/adsptolemy/lib.linux_x86_64:$LD_LIBRARY_PATH 
LD_LIBRARY_PATH=$HPEESOF_DIR/lib/linux_x86_64:$LD_LIBRARY_PATH 
SIMARCH=linux_x86_64

export HPEESOF_DIR

Yeah, you can do that too. Personally I prefer to put that sort of thing in a shell script. If only because quite often I have more than one version of a piece of software on my machine. If you put all the env vars in your .bashrc then that typically is for 1 specific install. And regarding the LD_LIBRARY_PATH, I noticed eesofboot.sh etc already takes care of that based on the HPEESOF_DIR variable.

But either way, I suppose it mostly comes down to personal preference.

 

[Vigort]

Well it is the first my experience of installation ADS on linux. LD_LIBRARY_PATH I have registered, as for me produced an error libXm.so.3 (demanded 32 bit).

 

[mrflibble]

LD_LIBRARY_PATH I have registered, as for me produced an error libXm.so.3 (demanded 32 bit).

libXm.so.3 is provided by the libmotif3 debian package...

 

[Vigort]

I know. Therefore also it was necessary to register LD since libmotif3 for me for 64, and he demanded 32 bats. At first I tried to solve by means of the character link in the directory/usr/lib32 but when has looked library that have seen: ELF 64-bit LSB shared object, has understood that such course will not help

 

[varuniyengar]

I have installed ADS 2011.01 linux on Fedora in /usr/local/ADS2011_01

I start the lmgrd like this


Then i get this


My .bashrc looks like this


I get the error msg


Please help me out with the configuration in bashrc

 

[Vigort]

Similar that at you doesn't find a file (symlink) libz.so.1. Try to install a packet zlib1-1.2.3-*.rpm

 

[varuniyengar]

I have installed that now stuck with libXm.so.3
Unable to debug this!!

What is the package name for fedorax86_64??

 

[Vigort]

openmotif-2.2.3-*.rpm

 

[varuniyengar]

First i did this
$yum whatprovides "*libXm.so.*"

and installed all the packages using yum
openmotif-2.3.3-1.fc14.i686
& lesstif-0.95.2-2.fc15.i686

then ran ads to which i got the same error

hpeesofde: error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory

Using Fedora 16 x86_64

 

[Vigort]

To you it is necessary lib for x86x64: openmotif-2.3.3-*.rpm
In Debian I did so: Install libmotif3 (64bit packet libXm.so.3), than download libmotif3 for i686 unpackked from libmotif3 in a folder /usr/lib32 libXm.so.3 and libXm.so.3.0.*

 

[varuniyengar]

I have installed both i686 and x86_64 versions

when is query for the packages its shows the packages!!

when i run ads
i also get this error /usr/local/ADS**/bin/ads[8]:.[13]:.[70]:.[7]:.[28]: lsb_release: not found [no such file or directory]
& /usr/local/ADS**/bin/ads[8]:.[13]:.[70]:.[7]:.line 29: lsb_release: not found
Using 64bit data display and simulation settings


Then libXm.so.3 error