Sponsored Content
Full Discussion: unable to make Q espresso
Top Forums UNIX for Dummies Questions & Answers unable to make Q espresso Post 302395461 by chevskan on Tuesday 16th of February 2010 07:04:55 AM
Old 02-16-2010
unable to make Q espresso

Dear all

I am trying to install quantum espresso. When I implement the necessary commands (like configure and make), I get the following error:
Code:
/usr/bin/ld: warning: libgfortran.so.1, needed by/usr/lib64/openmpi/1.2.4-gcc/libmpi_f90.so, may conflict with libgfortran.so.3

Can anyone suggest what i should do?

thanks in advance
chevskan

Last edited by chevskan; 02-17-2010 at 04:26 AM.. Reason: Please use code tags!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

make and make install commands

Hi there, I am installing a package at the moment on to my Solaris version 8 and I have run into a problem with the 'make' command. I have installed the package using the 'pkgadd' command and I am now at the stage where I have to use the 'make' command followed by the 'make install'... (4 Replies)
Discussion started by: gerwhelan
4 Replies

2. Programming

Unable to make a debuggable exe in HP 11i

Hi Guys, I need a help from you all. Basically I am working on 64 HP-UX 11i. I am building an exe from some 2gb of C codes. Now my problem is that I am unable to make the exe a debuggable one. So whenever I remove the -s fla from the make file, during building, the error message "Out of memory"... (1 Reply)
Discussion started by: hrishiraj_b
1 Replies

3. Linux

Error in issuing a make and make install

Hi, Recently I install a package and try to do a make and make install. However, in the make it gives me below error:- make:Nothing to be done for 'install-exec-am' make:Nothing to be done for 'install-data-am' Can anyone please explain to me what does this mean? I have been trying... (1 Reply)
Discussion started by: ahjiefreak
1 Replies

4. UNIX for Advanced & Expert Users

make/Oracle : Unable to find library 'libclntsh.sl.9.0

Hi all, If any of DBA/build experts can help me on solving this issue, it would be of great help: Recently Oracle was upgraded from 9.2.0.6 to 9.2.0.8 version, after this our C/ProC build is is erroring out by giving the following error : 860:/usr/lib/pa20_64/dld.sl: Unable to find library... (1 Reply)
Discussion started by: shihabvk
1 Replies

5. Solaris

Gani Network Driver Won't Install - make: Fatal error: Don't know how to make targ...

I attached a README file that I will refer to. I successfully completed everything in the README file until step 4. # pwd /gani/gani-2.4.4 # ls COPYING Makefile.macros gem.c Makefile Makefile.sparc_gcc gem.h Makefile.amd64_gcc ... (1 Reply)
Discussion started by: Bradj47
1 Replies

6. Shell Programming and Scripting

Unable to make script executable

Hello everybody, I'm unable to make my shell script an executable file. The details are as follows: PATH includes my $HOME/bin i.e. /rchome/rc1/bin HOME directory is /rchome/rc1 script name is prep_mig.sh permissions set are 755 It's executing if I give below command sh prep_mig.sh but... (4 Replies)
Discussion started by: jitu.keshwani
4 Replies

7. UNIX for Dummies Questions & Answers

Difference between configure/make/make install.

Hi, While installation of apache on linux, we perform the below tasks. 1) Untar 2) configure 3) make 4) make install. I wanted to understand the difference and working of configure/make/make install. Can any one help me understanding this? Thanks in advance. (1 Reply)
Discussion started by: praveen_b744
1 Replies

8. Programming

Issue with make, no rule to make target etc.

I have been trying to split up my src directory to clear out files that are not re-compiled very often. Now I have the following setup in my trunk, trunk/bld trunk/src/ trunk/src/src_server trunk/makefile.linux In the make file, I have compile rules SOURCELOC = src # compile src c++... (4 Replies)
Discussion started by: LMHmedchem
4 Replies

9. UNIX for Dummies Questions & Answers

SLURM script for quantum espresso

Hello everyone. I am trying to submit a job on quantum espresso program on a SLURM environment (parallel computing); of course SBATCH is used. I am a UNIX dummy and not sure if my script is right but i keep getting the error: sbatch: error: Batch job submission failed: job has invalid account. The... (0 Replies)
Discussion started by: lebphys78
0 Replies

10. Shell Programming and Scripting

How to let it go straight into espresso coding?

13578875446998765 (0 Replies)
Discussion started by: qwer123
0 Replies
GIMPTOOL-2.0(1) 					      General Commands Manual						   GIMPTOOL-2.0(1)

NAME
gimptool-2.0 - script to perform various GIMPy functions SYNOPSIS
gimptool-2.0 [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--msvc-syntax] [--bindir] [--sbindir] [--libexecdir] [--datadir] [--sysconfdir] [--sharedstatedir] [--localstatedir] [--libdir] [--infodir] [--mandir] [--includedir] [--gimpplugindir] [--gimpdatadir] [--libs] [--libs-noui] [--cflags] [--cflags-noi] [--build plug-in.c] [--build-strip plug-in.c] [--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-in.c] [--install-bin plug-in] [--install-admin-strip plug-in.c] [--install-bin-strip plug-in] [--install-admin-bin plug-in] [--install-script script.scm] [--install-admin-script script.scm] [--uninstall-bin plug-in] [--uninstall-admin-bin plug-in] [--uninstall-script script.scm] [--unin- stall-admin-script script.scm] DESCRIPTION
gimptool-2.0 is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file. gimptool-2.0 can also be used by programs that need to know what libraries and include-paths GIMP was compiled with. gimptool-2.0 uses pkg- config for this task. For use in Makefiles, it is recommended that you use pkg-config directly instead of calling gimptool-2.0. OPTIONS
gimptool-2.0 accepts the following options: --version Print the currently installed version of GIMP on the standard output. --help Print out the help blurb, showing commonly used commandline options. --quiet Run quietly without echoing any of the build commands. --silent Run silently without echoing any of the build commands. Same as --quiet. -n Test mode. Print the commands but don't actually execute them. Useful for making dry runs for testing. --just-print Test mode. Print the commands but don't actually execute them. Same as -n. --dry-run Test mode. Print the commands but don't actually execute them. Same as -n. --recon Test mode. Print the commands but don't actually execute them. Same as -n. --msvc-syntax Useful on Windows. Outputs the compiler and linker flags in the syntax used by Microsoft's toolchain. Passed to the pkg-config com- mand that does most of gimptool-2.0's work. --bindir Outputs the bindir used to install the GIMP. --sbindir Outputs the sbindir used to install the GIMP. --libexecdir Outputs the libexecdir used to install the GIMP. --datadir Outputs the datadir used to install the GIMP. --sysconfdir Outputs the sysconfdir used to install the GIMP. --sharedstatedir Outputs the sharedstatedir used to install the GIMP. --localstatedir Outputs the localstatedir used to install the GIMP. --libdir Outputs the libdir used to install the GIMP. --infodir Outputs the infodir used to install the GIMP. --mandir Outputs the mandir used to install the GIMP. --includedir Outputs the includedir used to install the GIMP. --gimpdatadir Outputs the actual directory where the GIMP data files were installed. --gimpplugindir Outputs the actual directory where the GIMP plug-ins were installed. --build plug-in.c Compile and link plug-in.c into a GIMP plug-in. --build-strip plug-in.c Compile,link, and strip plug-in.c into a GIMP plug-in. --install plug-in.c Compile, link, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-strip plug-in.c Compile, link,strip, and install plug-in.c into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin plug-in.c Compile, link, and install plug-in.c into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin plug-in Install plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin-bin plug-in Install plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-bin-strip plug-in Install stripped plug-in into the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --install-admin-bin-strip plug-in Install stripped plug-in into the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --install-script script.scm Install script.scm into the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts) --install-admin-script script.scm Install script.scm into the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --uninstall-bin plug-in Uninstall plug-in from the user's personal GIMP plug-in directory ($HOME/.gimp-2.8/plug-ins) --uninstall-admin-bin plug-in Uninstall plug-in from the system-wide GIMP plug-in directory (/usr/lib64/gimp/2.0/plug-ins) --uninstall-script script.scm Uninstall script.scm from the user's personal GIMP script directory ($HOME/.gimp-2.8/scripts) --uninstall-admin-script script.scm Uninstall script.scm from the system-wide GIMP script directory (/usr/share/gimp/2.0/scripts) --libs Print the linker flags that are necessary to link a GIMP plug-in. --libs-noui Print the linker flags that are necessary to link a GIMP plug-in, for plug-ins that do not require the GTK+ libraries. --cflags Print the compiler flags that are necessary to compile a GIMP plug-in. --clags-noui Print the compiler flags that are necessary to compile a GIMP plug-in for plug-ins that do not require the GTK+ libraries. --prefix=PREFIX If specified, use PREFIX instead of the installation prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options. --exec-prefix=PREFIX If specified, use PREFIX instead of the installation exec prefix that GIMP was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options. ENVIRONMENT
CC to get the name of the desired C compiler. CFLAGS to get the preferred flags to pass to the C compiler for plug-in building. LDFLAGS to get the preferred flags for passing to the linker. LIBS for passing extra libs that may be needed in the build process. For example, LIBS=-lintl . PKG_CONFIG to get the location of the pkg-config program that is used to determine details about your glib, pango, gtk+ and gimp installation. SEE ALSO
gimp(1), gimprc(5), pkg-config(1) AUTHORS
gimptool was written by Manish Singh (yosh@gimp.org) and is based on gtk-config by Owen Taylor (owen@gtk.org). This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins (adrian@gimp.org) and Marc Lehmann (pcg@goof.com>). GIMP Manual Pages Version 2.8.10 GIMPTOOL-2.0(1)
All times are GMT -4. The time now is 07:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy