Sponsored Content
Operating Systems OS X (Apple) Problems with path using UNIX tools in mac Post 302554156 by 454rocks on Saturday 10th of September 2011 11:22:24 AM
Old 09-10-2011
Problems with path using UNIX tools in mac

Hello,
Glad I found this forum....
Well I'm starting using UNIX tools in macOS for bioinformatics (Python....).
I know that in UNIX every installed tools go to usr/bin.... But since in mac I do not have access to it I wanted to know were to create and install tools? Can I recreate a pseudo UNIX pathway?
Right know I install new tool in / but for example boost and then the programs requiring them do not find them...

Sorry for this newbie question and thanx for help.....
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX mode in Mac OSX - problems

I am a Macintosh using OS 10.2 which has Unix underpinnings. When entering console mode (the root system where unix takes over) I get the following message - bootstrap_look_up () failed (ipc/send) invalid destination port I always used to get a localhost# prompt (and then can use unix... (1 Reply)
Discussion started by: ngilman
1 Replies

2. UNIX for Dummies Questions & Answers

Urgent help with web design problems - mac, safari and unix computer

Hi (Help, Help, Help) I am on a computer course and have designed a web site as one of my assignments. just before Xmas my college tutor "very kindly" viewed my site with a mac, safari browser and unix operating system computer. This is what she Emailed back to me, and I am trying to sort... (3 Replies)
Discussion started by: skylark167
3 Replies

3. UNIX for Advanced & Expert Users

UNIX monitoring tools

Guys, I would like to know who are using monitoring tools? I use Nagios before but it seems is more on Linux and Windows platform. - Nagios - BigBrother - BigSister - Cacti - MRTG - JFFNMS - anymore? Please give comment too I would like to have some comment on UNIX monitoring tools.... (2 Replies)
Discussion started by: dwarf007
2 Replies

4. UNIX for Dummies Questions & Answers

problems with aliases on Mac

so I have my .profile set up as such ## # DELUXE-USR-LOCAL-BIN-INSERT # (do not remove this comment) ## echo $PATH | grep -q -s "/usr/local/bin" if ; then PATH=$PATH:/usr/local/bin export PATH fi # Aliases ALIAS=~/.alias export ALIAS .$ALIAS and my .alias as (2 Replies)
Discussion started by: blowFish@ubuntu
2 Replies

5. UNIX for Dummies Questions & Answers

Problems installing a program through Terminal in Mac OS X

Hey all.. I have a problem with the BitTorrent client called Deluge. (Deluge BitTorrent Client). Followed the guide on their homepage, but can't get it to work. First of all I have installed Xcode Tools 3.0 and MacPorts. I did the "sudo port install deluge" command, and all packages seemed to... (1 Reply)
Discussion started by: Sixmax
1 Replies

6. Shell Programming and Scripting

Problems with Space at path

Hi everyone, I create script for seaching count of differrent file types at my FS. My script: #! /bin/sh #OLD_IFS=$IFS #export IFS=$(echo "\n\t ") echo "Wait a minute... Seaching is performed" d=0;b=0;c=0;p=0;s=0;l=0;f=0 non=0 for fl in $(find /opt/google/picasa/3.0/wine/drive_c... (8 Replies)
Discussion started by: babi4
8 Replies

7. UNIX for Dummies Questions & Answers

Problems with my PATH

I've been googling all morning and i cannot for the life of me find the answer :) Basically, i'm setting my path in my .profile as: #!/bin/bash # export ORACLE_HOME=/oracle/product/10.2 export ORACLE_HOME=/oracle/product/9.2/ export TNS_ADMIN=/oracle/network/clients... (1 Reply)
Discussion started by: gman
1 Replies

8. Cybersecurity

File encryption tools with MAC address as an encryption key

Hi all, I'm looking for secure file encryption tools that use MAC address as encryption key. FYI, I'm using Red Hat Enterprise Linux OS. For example: when A wants to send file to B A will encrypt the file with B's computer MAC/IP address as an encryption key This file can only be decrypted... (2 Replies)
Discussion started by: sergionicosta
2 Replies

9. Programming

File Path in Mac OS

Suppose I have file in linux OS the absolute path of which is: /media/OS_Files/myfile What will be the absolute path of this file in MAC OS? Any good link which which explain the absolute path format in MAC? (1 Reply)
Discussion started by: rupeshkp728
1 Replies

10. What is on Your Mind?

Google Webmaster Tools Shows Problems with Soft 404 Errors

Well, Sorry, but I cannot seem to fix the problem with the steady decline of ranking for unix.com pages with Google. Google Webmaster Tools show that they are dropping our pages from the indexes more and more because of "Soft 404" errors which started after we moved to the new data center. ... (18 Replies)
Discussion started by: Neo
18 Replies
ATTILA(1)						  Alliance - attila User's Manual						 ATTILA(1)

NAME
attila - A Tool Installer SYNOPSIS
attila [ -h ] [ -S ] [ -U ] [ -F ] [ -A ] [ --help ] [ --ssh ] [ --user ] [ --asim ] [ --prefix=INSTALL_DIR ] [ --builddir=BUILD_DIR ] --tool=name1 [ --tool=name2... ] [ -c- configure_arg1 [ configure_arg2 ... ] ] [ -m- make_arg1 [ make_arg2... ] ] DESCRIPTION
attila automates the process of compiling and installing one or more Alliance tools. The tool can be installed either in the user's account (during the devellopment stage) or in the Alliance system wide tree (for instance /asim/alliance) when a new version is made avalaible to all. attila proceed with the following steps : 1. Checks if the sources of tools are present in the user's account. If not, check them out from the Alliance CVS tree. Note that you must have access to it. 2. In case of --asim or --full installations, attila will fork itself on one Linux computer (currently bip) and on one Solaris computer (beny). As to connect on thoses computer it will uses rsh so you must setup your ~/.rhosts to access them whithout passwords. You also can uses ssh (but the procedure to allow automatic login is more complicated). 3. Run autostuff for the tool in the ~/alliance/src directory. 4. Run configure in the build directory (see below). 5. Install the tool in the local install directory (see below) or in the system-wide Alliance directory rooted under /asim/alliance. After an --asim install: the build directory tree of the tool will be removed to avoid messing with further local installations. DIRECTORY STRUCTURE attila relies on the following tree structure : (all paths below are given relative to the user's home directory) o ~/alliance/src where the tools sources are to be found. o ~/alliance/Linux/build/$TOOL : the top directory under which the tool will be compiled for Linux. This is where the configure script will be run. o ~/alliance/Linux/install : the top of the install tree when the tool is compiled locally for Linux. Under this directory you will found (at least) : ./bin, ./lib and ./include. o ~/alliance/Solaris/build/$TOOL : the tool's build directory for Solaris. o ~/alliance/Solaris/install : top of the local install tree for Solaris. CVS CHECKOUT If the sources of the requested tool(s) are not found under ~/alliance/src/ attila will try to check them out. So, as says above, you must have access rights to the Alliance CVS tree. In addition to the tool(s) sources, it will also checks for the minimal set of files needed for configure to run. As for now : o autostuff o alliance.m4 o motif.m4 o Makefile.am GUESSING CVSROOT The root of the CVS tree will be set according to the following rules : 1. Uses the user's environment variable CVSROOT if sets. 2. Uses the attila default value sets in attila.conf (variable ATTILA_CVSROOT). GUESSING ALLIANCE_TOP The root of the Alliance installed distribution tree will be set according to the following rules : 1. Uses the user's environment variable ALLIANCE_TOP if sets. 2. Uses the attila default value sets in attila itself (variable ATTILA_ALLIANCE_TOP). ALLIANCE_TOP: is set in attila itself because its value is a prerequisite to load the configuration file attila.conf which is in the directory $ALLIANCE_TOP/etc/. ARGUMENTS
attila accepts the followings arguments : o -h, --help : print help. o -S, --ssh : uses ssh instead of rsh to connect to the remote computers (in case of --asim or --full). o -U, --user : perform a local installation. o -F, --full : install for all avalaibles architectures (currently Linux and Solaris). o -A, --asim : install in the system-wide directory (/asim/alliance). o --prefix=INSTALL_DIR : override the default installation directory. o --builddir=BUILD_DIR : override the default building directory. o --tool=name1 : name of the tool to be installed. o -c- configure_arg1 : all arguments following -c- (until a -m- is encountered) are passed as is to the subsequent call to configure. For example, if you want to first use your local libraries, give --enable-devel. If you want to link or install dynamic libraries, give --enable-alc-shared for alliance libraries and give --enable-shared for other libraries. o -m- make_arg1 : all arguments following -m- are passed as is to the subsequent call to make. If no -m- argument is given, then install is assumed. If you want to completly uninstall a tool and clean it's build directory you can pass uninstall clean CONFIGURATION FILE ATTILA.CONF The configuration file is located in $ALLIANCE_TOP/etc. This file is to be read by the sh shell. It sets up the following variables : o LINUX_TARGET : the computer where to compile for the Linux architecture (default bip). o LINUX_CC : the name or full path to to the C compiler for Linux system (default gcc3). o LINUX_CXX : the name or full path to to the C++ compiler for Linux system (default g++3). o SOLARIS_TARGET : the computer where to compile for the Solaris architecture (default beny). o SOLARIS_CC : the name or full path to to the C compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o SOLARIS_CXX : the name or full path to to the C++ compiler for Solaris system (default /usr/local/gcc-3.0.4/bin/g++3). o ATTILA_CVSROOT : the root of the Alliance CVS tree (default /users/outil/alliance/cvsroot). o CVS_STARTUP_FILES : the minimal set of files needed to run configure. EXAMPLES
Compile & install nero tool on the local computer (must be either a Linux or a Solaris one) : $ attila --tool=nero Compile & install nero tool for all architectures (currently only Linux and Solaris are supported) : $ attila --full --tool=nero Compile & install nero tool in the system-wide directory (a new version for everyone to use) : $ attila --asim --tool=nero Compile & install mbk then genlib (the order is significant) in a row for a local install on the current computer : $ attila --tool=mbk --tool=genlib Compile nero tool and link it against the locally installed libraries (if any). $ attila --tool=nero -c- --enable-devel Remove poire tool from the system-wide tree. (poire is the old name of nero). $ attila --asim --tool=poire -m- uninstall ASIM
/LIP6 13 October 2002 ATTILA(1)
All times are GMT -4. The time now is 04:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy