SH script, variable built command fails, but works at command line
I am working with a sh script on a solaris 9 zone (sol 10 host) that grabs information to build the configuration command line. the variables Build64, SSLopt, CONFIGopt, and CC are populated in the script. the script includes
When i run the sh -x script.sh i get the following output.
Code:
+sh ./configure CC="gcc -m64 -mcpu=v9" --prefix=/ --exec-prefix=/usr \
--libexecdir=/usr/lib/libexec --includedir=/usr/include --with-random=/dev/random --with-openssl=/usr/local/openssl-1.0.0j-pkcs11
checking build system type... sparc-sun-solaris2.9
checking host system type... sparc-sun-solaris2.9
checking for gcc... "gcc -m64 -mcpu=v9"
checking whether the C compiler works... no <-------- FAILURE
configure: error: in `/bind-9.9.1-P2':
configure: error: C compiler cannot create executables
See 'config.log' for more details
config.log just has: configure:4078: "/usr/local/bin/gcc: No such file or directory.
BUT if I copy that command line and paste it to the prompt everything works.
if i put that expanded command line into the script, it works
Hey there, I'm a total newbie unix guy here and just picking this stuff up. Have a very small script I put together that works fine from the command line but not once I put it in a cron job. Searched and found this thread and am wondering it it has something to do with setting variables, though the... (7 Replies)
I have a very basic script that essentially sends a log file, via FTP, to a backup server. My cron entry to run this every night is:
55 23 * * * /usr/bin/archive_logs
The script runs perfectly when executed manually, and actually worked via cron for about three weeks. However, it mysteriously... (3 Replies)
Hi all-
I'm trying to search through some .gz log files to verify certain feeds have passed through our app.
I have a small script that I wrote in hopes that I could automate the checking but haven't been able to get the zgrep to work. When I copy it to the command line directly it works... (2 Replies)
When I run this code from the command line works
spinel.middlebury.edu:/u02/sct/banner/bandev2/middlebury/shl:DEV2$ ls ef*
eftseq.dat
spinel.middlebury.edu:/u02/sct/banner/bandev2/middlebury/shl:DEV2$ file_seq=$( < eftseq.dat) ... (1 Reply)
Hi everyone,
when executing this command in unix:
echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error.
here is content of my script:
tdbsrvr$ vi hc.sh
"hc.sh" 22 lines, 509... (4 Replies)
Hey guys. Hopefully this is an easy one but having reference similar problems on the web I still can't fix it.
I am doing a recursive find and replace from a script. Of course I could just run the damn thing from the command line but it's bugging me now and want to get it working.
grep -rl... (4 Replies)
Hi guys. My first post, so be gentle...
On my Solaris 10 machine vnc server is running. I need a command to extract most recent client session number (screen). So with:
Code:
bash-3.2# ps -ef | grep vnc | grep Xaut
root 19805 19797 0 15:41:44 ? 0:01 Xvnc :4 -inetd -once... (5 Replies)
OSX 10.9
I am building a script that evaluates the difference between 2 files. Here is a command that does not work transparently.
Running this command in Terminal yields great results; however when I put that line in a .sh script, I get the errors shown below. Am I doing something silly?
... (1 Reply)
Hi,
I am looking for a generic find command that works on both Linux and Solaris.
I have the below command that works fine on Linux but fails on solaris.find /web/config -type f '(' -name '*.txt' -or -name '*.xml' -name '*.pro' ')' Fails on SunOS mysolaris 5.10 Generic_150400-61 sun4v sparc... (1 Reply)
I wish to replace "\\n" with a single white space.
The below does the job on command-line:
$ echo '/fin/app/scripts\\n/fin/app/01/sql' | sed -e 's#\\\\n# #g';
/fin/app/scripts /fin/app/01/sql
However, when i have the same code to a shell script it is not able to get me the same output:... (8 Replies)
Discussion started by: mohtashims
8 Replies
LEARN ABOUT SUSE
gimptool-2.0
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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.
DESTDIR to add a prefix to the install/uninstall path.
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.6.8 GIMPTOOL-2.0(1)
09-14-2012
