Sponsored Content
Full Discussion: UNIX flavors
Special Forums UNIX Desktop Questions & Answers UNIX flavors Post 15815 by killerserv on Wednesday 20th of February 2002 12:50:59 AM
Old 02-20-2002
Almost all the unix variants are compatible and suits for the 3D rendering and 3D Animation. All depends on the user how to make use of it. You may try one of it depends on your H/Ware requirement.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX problem? Unix programm runs windows 2000 CPU over 100%

Okee problems...!! What is happening: Unix server with some programms, workstations are windows 2000, the workstations work good but when you start a programm on the Unix server the CPU of the workstations go to 100% usage resulting that the system gets very slow. The programm well its running so... (2 Replies)
Discussion started by: zerocool
2 Replies

2. What is on Your Mind?

Different flavors of Linux

What are the different flavors of Linux? (1 Reply)
Discussion started by: SubbaraoV
1 Replies

3. UNIX for Dummies Questions & Answers

What exactly is a Unix Flavors means??

could anybody tell me what is a unix flavor? (4 Replies)
Discussion started by: human
4 Replies

4. Shell Programming and Scripting

One Script on all the Unix flavors

Hi , I need to run a script on different flavors, namely 1) Linux 2) AIX 3) Solaris 4) HP-UX Almost the entire script is the same except at a few places where commands specific to that OS are to be run. Is it possible to have a single script that runs on all the platforms? Sth... (5 Replies)
Discussion started by: tcsprak
5 Replies

5. UNIX for Dummies Questions & Answers

How does unix system administration, unix programming, unix network programming differ?

How does unix system administration, unix programming, unix network programming differ? Please help. (0 Replies)
Discussion started by: thulasidharan2k
0 Replies

6. Shell Programming and Scripting

Get all types of shell supported on any unix flavors.

Hello - Is there a command/way we can find out, what shells are supported on a Unix machine? Please let me know. Thanks, Manju (3 Replies)
Discussion started by: manju--
3 Replies

7. UNIX for Dummies Questions & Answers

Unix flavors that run on x86, x86_64 bit processors?

Hello everyone. This is an awesome forum. Glad to have joined! :) I use Linux mostly, even for Desktop usage. I just love everything about it, all the way down to how the font looks while browsing. Its just so sleek and sexy. But I also boot Windows for those programs I just need that only... (23 Replies)
Discussion started by: insomnia
23 Replies

8. Shell Programming and Scripting

Time zone issues in UNIX flavors

Hello All, I am in process of migrating all my scripts from AIX box to Linux box. In one of my script I calculate my last week date with the below command $ TZ=EDT+172 date +%F 2012-12-13 $ uname -a AIX 1 7 000B29AAD400 Now when I tried running the same in Linux, it gives a false... (2 Replies)
Discussion started by: sathyaonnuix
2 Replies

9. Shell Programming and Scripting

File Transfer from Window server to UNIX and UNIX to UNIX

Dear All, Can someone help to command or program to transfer the file from windows to Unix server and from one unix server to another Unix server in secure way. I would request no samba client. (4 Replies)
Discussion started by: yadavricky
4 Replies
GPT-BUILD(8)						User Contributed Perl Documentation					      GPT-BUILD(8)

NAME
gpt-build - Builds and installs GPT source packages and bundles. SYNOPSIS
gpt-build [options] [macros] [source packages] flavors ... Options: -verbose Print copious output -help Print usage -man Print man page. -version Print GPT version. -installdir=path_to_installation Override $GLOBUS_LOCATION -builddir=path_to_build directory Directory to unpack tarfiles -logdir=log_file_directory Directory for package logs -srcdir=source_directory Directory containing a source package -static Build static executables -force Force rebuilds -update Rebuild if newer -disable-version-checking Ignore versions in package dependencies. -std-flavors Build all std flavors. -all-flavors Build all of the flavors -coresrc Override installed globus_core pkg -nosrc Only install the flavors [macro=value] Macro definitions [list of flavors to build] Flavors that define the build options [list of source packages] Tarfiles of source bundles or packages DESCRIPTION
gpt-build Builds and installs software from source distributions. The script reads the build instructions for each source distribution from a package metadata file called pkg_data_src.gpt. If no instructions are found the script uses the default instructions described in Grid::GPT::PkgMngmt::Build. Multiple packages can be built by passing in multiple -srcdir arguments or multiple source packages and or bundles. For now these have to be passed in in dependent order ie. if package foo needs package fee's headers to build then fee should come first. gpt-build does not create binary packages as globus-build does. This is done by a seperate script called gpt-pkg. FLAVORS
Build flavors are character string labels that represent a set of compiler and linker options defined during the building of the globus_core package. Packages can be built with any installed flavor. globus_core can only be built with pre-defined flavors. globus_core needs to be built by hand (i.e. ./configure|make|make install) to install a custom build flavor. FILES IN PGM PACKAGES
Installed files such as executables that are found in pgm and pgm_static packages will overwrite one another when multiple flavors of the same package are built. Thus only the files from the last flavor built will be present after a gpt-build run. To preserve multiple flavors of these files, they are automatically copied into flavored subdirectories. For example, the program $GLOBUS_LOCATION/bin/foo will be copied into the location $GLOBUS_LOCATION/bin/gcc32/shared if it was built with dynamically with the gcc32 flavor. These files are retrieved by gpt-pkg. OPTIONS
-srcdir Specifies the where the source directory is. This is used by developers to build out of a repository.. -installdir Specifies the where the install directory is. This directory will be where the targets are installed before being archived. Note that this directory needs contain the installation targets of all of the packages which satisfy build dependencies in addition to the installation targets of the package being built. Because of this, installation targets are not removed after the package is archived. Because different flavors of program packages conflict with each other, the last flavor built is the flavor of the installed files. For each flavor, gpt-build makes a copy of each installed file in a program package and puts the copy in a flavored subdirectory. -builddir Specifies the where the source tar files should be untarred and the code is built. -force Tells gpt-build to rebuild a package even if it is already installed. The default behavior is to skip any packages that have been built before. -update Tells gpt-build to build even if an older version is installed. -verbose Prints out all of the build messages. -std-flavors Build the globus_core package with all of the flavor choices marked as standard in the flavor configuration file. All of the other packages will be built with all of the flavors sucessfully installed by globus_core. -all-flavors Build the globus_core package with all of the flavor choices marked as standard in the flavor configuration file. All of the other packages will be built with all of the flavors sucessfully installed by globus_core. -nosrc Just install the listed flavors. Don't build any source code. -coresrc Use this version of globus_core source rather than the one found in ${datadir}/globus/gpt/globus_core-src.tar.gz -flavor-cfg=FILE Use the flavor configurations found in FILE. The default configuration file is ${datadir}/globus/gpt/globus_flavor_labels.conf -logdir=DIRECTORY Store package logs of build messages in DIRECTORY. This option also sets -verbose. The default directory is ./logs. -help Print a brief help message and exits. -man Prints the manual page and exits. -version Prints the version of GPT and exits. MACROS
Build macros are perl routines and variables that are used by gpt-build while building packages. These macros are embedded in the build instructions part of the package's metadata file. Some of these macros can be set from the command line using the following format: <NAME>_GPTMACRO='new value' Note that even though this feature seems extremely flexible, it has not been thoroughly tested mainly because the authors have not been able to figure out what people will want to do with these macros. Further details are found in the Grid::GPT::PkgMngmt::BuildMacros manpage. SEE ALSO
gpt-pkg(8) gpt-bundle(8) gpt-install(8) BuildMacros(3) AUTHOR
Michael Bletzinger <mbletzin.ncsa.uiuc.edu> and Eric Blau <blau.mcs.anl.gov> perl v5.14.2 2012-04-30 GPT-BUILD(8)
All times are GMT -4. The time now is 04:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy