Sponsored Content
Top Forums Programming GFORTRAN library problem: libgFORTRAN.so.1 cannot open.... Post 302792067 by DGPickett on Tuesday 9th of April 2013 04:19:14 PM
Old 04-09-2013
Well, usually you can use 'find' to find missing files, or you can download and install them in their native packsge. And of course add them to LD_LIBRARY_PATH!
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Crontab failure.Can't open shared library

Plz advise on the following error for a crontab job i have scheduled for running a script /usr/lib/dld.sl: Can't open shared library: /home/build3p/PMReleases/Symphony711/HP-UX/rw/710/lib/libtls4d.sl /usr/lib/dld.sl: No such file or directory /ushhquest/data001/Scripts/Inform/Build_Data.sh:... (0 Replies)
Discussion started by: reader_regular
0 Replies

2. Programming

gfortran compiling problem,calling too many arguments

Hello, My problem is with compiling a program modelling shallow water. In it there is a subroutine called stat with 9 parameters. In the main program it is called with 9 parameters also I'm running Ubuntu 11.04 with gfortran version 4.5. Thanks. ---------- Post updated at 11:57 PM... (0 Replies)
Discussion started by: b_franz
0 Replies

3. HP-UX

Can't open shared library problem

I am getting following error when I am trying access PMCMD utility /usr/lib/dld.sl: Can't open shared library: /home/build3p/PMReleases/Zeus/HP-UX/xml/xerces2_4_0-icu2_6_1_811/lib/libxerces-c.sl.24 /usr/lib/dld.sl: No such file or directory Please help me with this (0 Replies)
Discussion started by: imran_affu
0 Replies

4. Programming

Compilation problem with gfortran

Hello everyone, I'm trying since a few days to compile a f90 program with gfortran (on Ubuntu) with a makefile. The fortran program calls 2 routines written in C. Here is my makefile: FC = gfortran SFC = gfortran FFLAGS = -ffree-form -O... (21 Replies)
Discussion started by: leroygr
21 Replies

5. Linux

./configure problem for libsf library due to apparently missing libdb library.

Hello, ./configure script fails to configure libsf. Please check the following last few lines of configure script error. checking for db1/db.h... no checking for db.h... yes checking for dbopen in -ldb1... no configure: error: No libdb? No libsf. But find command shows the following; ... (4 Replies)
Discussion started by: vectrum
4 Replies

6. Programming

problem compiling with gfortran in two different debian releases

Hello, I hope this is the correct forum for this post. I have the following problem: A Fortran 77 program that has to deal with several large matrices (each approx. 5000 x 5000) and uses lapack and blas subroutines has been correctly compiled and executed using Debian Etch. When I tried... (1 Reply)
Discussion started by: currix
1 Replies
DH_INSTALL(1)							     Debhelper							     DH_INSTALL(1)

NAME
dh_install - install files into package build directories SYNOPSIS
dh_install [-Xitem] [--autodest] [--sourcedir=dir] [debhelperoptions] [file|dir...destdir] DESCRIPTION
dh_install is a debhelper program that handles installing files into package build directories. There are many dh_install* commands that handle installing specific types of files such as documentation, examples, man pages, and so on, and they should be used when possible as they often have extra intelligence for those particular tasks. dh_install, then, is useful for installing everything else, for which no particular intelligence is needed. It is a replacement for the old dh_movefiles command. This program may be used in one of two ways. If you just have a file or two that the upstream Makefile does not install for you, you can run dh_install on them to move them into place. On the other hand, maybe you have a large package that builds multiple binary packages. You can use the upstream Makefile to install it all into debian/tmp, and then use dh_install to copy directories and files from there into the proper package build directories. From debhelper compatibility level 7 on, dh_install will fall back to looking in debian/tmp for files, if it does not find them in the current directory (or wherever you've told it to look using --sourcedir). FILES
debian/package.install List the files to install into each package and the directory they should be installed to. The format is a set of lines, where each line lists a file or files to install, and at the end of the line tells the directory it should be installed in. The name of the files (or directories) to install should be given relative to the current directory, while the installation directory is given relative to the package build directory. You may use wildcards in the names of the files to install. Note that if you list exactly one filename or wildcard-pattern on a line by itself, with no explicit destination, then dh_install will automatically guess the destination to use, the same as if the --autodest option were used. debian/not-installed Used with the deprecated --list-missing and --fail-missing options. Please refer to dh_missing(1) for the documentation of this file. OPTIONS
--list-missing Deprecated: Please use dh_missing --list-missing instead. If you use this option, dh_install will call dh_missing with that option after it has processed all the files. Please see dh_missing(1) for the documentation of this option. This option is removed in compat 12. --fail-missing Deprecated: Please use dh_missing --fail-missing instead. If you use this option, dh_install will call dh_missing with that option after it has processed all the files. Please see dh_missing(1) for the documentation of this option. This option is removed in compat 12. --sourcedir=dir Look in the specified directory for files to be installed. Note that this is not the same as the --sourcedirectory option used by the dh_auto_* commands. You rarely need to use this option, since dh_install automatically looks for files in debian/tmp in debhelper compatibility level 7 and above. --autodest Guess as the destination directory to install things to. If this is specified, you should not list destination directories in debian/package.install files or on the command line. Instead, dh_install will guess as follows: Strip off debian/tmp (or the sourcedir if one is given) from the front of the filename, if it is present, and install into the dirname of the filename. So if the filename is debian/tmp/usr/bin, then that directory will be copied to debian/package/usr/. If the filename is debian/tmp/etc/passwd, it will be copied to debian/package/etc/. file|dir ... destdir Lists files (or directories) to install and where to install them to. The files will be installed into the first package dh_install acts on. LIMITATIONS
dh_install cannot rename files or directories, it can only install them with the names they already have into wherever you want in the package build tree. However, renaming can be achieved by using dh-exec with compatibility level 9 or later. An example debian/package.install file using dh- exec could look like: #!/usr/bin/dh-exec debian/default.conf => /etc/my-package/start.conf Please remember the following three things: o The package must be using compatibility level 9 or later (see debhelper(7)) o The package will need a build-dependency on dh-exec. o The install file must be marked as executable. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 11.1.6ubuntu2 2018-05-10 DH_INSTALL(1)
All times are GMT -4. The time now is 10:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy