also @ TechSpot: Nvidia interested in licensing graphics technology to other chip makers

Installing software in linux

Discussion in 'The Alternative OS' started by CrackedButter, Nov 5, 2002.

  1. CrackedButter Newcomer, in training Posts: 41

    sound silly and its probably why it isn't working but when i fire up the console all i get is:"meltedbutter@linux:~>"

    I thought it might be like DOS where if you open a command prompt in a folder it would automatically give the folders location all typed out. <<< edited.

    Okay so nobody bothered to tell me i should have the terminal icon on the knoqeuerer menu bar.
    I've added it now myself and its added the location for me.
  2. CrackedButter Newcomer, in training Posts: 41

    Damn, just realised i am not in root.

    Is this not a catch 22, i have to do this in root but i am asking for advice while on the net and i'm not supposed to be doing that am i?
  3. CrackedButter Newcomer, in training Posts: 41

    okay this is what i get in the terminal:

    linux:/home/meltedbutter/Download/Licq/licq-1.2.0a # ./configure
    loading cache ./config.cache
    checking host system type... i686-pc-linux-gnuoldld
    checking target system type... i686-pc-linux-gnuoldld
    checking build system type... i686-pc-linux-gnuoldld
    checking for a BSD compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking whether make sets ${MAKE}... no
    checking for working aclocal... missing
    checking for working autoconf... missing
    checking for working automake... missing
    checking for working autoheader... missing
    checking for working makeinfo... found
    checking for gcc... no
    checking for cc... no
    configure: error: no acceptable cc found in $PATH
    linux:/home/meltedbutter/Download/Licq/licq-1.2.0a #

    While i am at it, anybody know how to copy an paste this text into another text box without having to drag it all the time? I notice there is a paste function on the terminal menu but no copy function.

    Anyway, i type "make" and i then get this:bash: make: command not found
  4. Mictlantecuhtli TS Special Forces Posts: 4,916   +9

    If you want command line to display the directory path before the prompt, you need to edit a hidden file in your home directory, .bashrc or .profile.
    Add a line

    export PS1='$PWD>'

    there and you're done. However, I'm not sure if terminals started inside GUI use it..

    Those errors you're getting mean you haven't installed a C/C++ compiler - SuSE may have something like "development tools" or something you should install.

    The reason I sound a bit vague is that it's been a while since I used Linux and when I did, it was a version made from scratch, not a big distribution like Red Hat or SuSE.

    You can do stuff as root by using su command when you're logged in as a normal user.
  5. CrackedButter Newcomer, in training Posts: 41

    bah i have installed how ever many compilers there are. I'll try again.
    This is what i get:

    linux:/home/meltedbutter/Download/Licq/licq-1.2.0a # make
    make: *** No targets specified and no makefile found. Stop.

    okay with the "su" command, its quite neat and saves a load of time, thanks!

    life is a little easyier now.
  6. CrackedButter Newcomer, in training Posts: 41

    okay after installing ALL the C++ Compliers and now re ran the ./configure command, it goes running the linux stuff and ends with this:

    linux:/home/meltedbutter/Download/Licq/licq-1.2.0a # ./configure
    loading cache ./config.cache
    checking host system type... i686-pc-linux-gnu
    checking target system type... i686-pc-linux-gnu
    checking build system type... i686-pc-linux-gnu
    checking for a BSD compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking whether make sets ${MAKE}... yes
    checking for working aclocal... found
    checking for working autoconf... found
    checking for working automake... found
    checking for working autoheader... found
    checking for working makeinfo... found
    checking for gcc... gcc
    checking whether the C compiler (gcc ) works... yes
    checking whether the C compiler (gcc ) is a cross-compiler... no
    checking whether we are using GNU C... yes
    checking whether gcc accepts -g... yes
    checking how to run the C preprocessor... gcc -E
    checking for c++... c++
    checking whether the C++ compiler (c++ ) works... yes
    checking whether the C++ compiler (c++ ) is a cross-compiler... no
    checking whether we are using GNU C++... yes
    checking whether c++ accepts -g... yes
    checking whether c++ accepts -fno-exceptions -fno-check-new... yes
    checking how to run the C++ preprocessor... c++ -E
    checking for POSIXized ISC... no
    checking whether make sets ${MAKE}... (cached) yes
    checking for a BSD compatible install... /usr/bin/install -c
    checking for ranlib... ranlib
    checking for strip... /usr/bin/strip
    checking for size... /usr/bin/size
    Setting Linux compilation options
    checking for dirent.h that defines DIR... yes
    checking for opendir in -ldir... no
    checking for ANSI C header files... yes
    checking for errno.h... yes
    checking for fcntl.h... yes
    checking for getopt.h... yes
    checking for limits.h... yes
    checking for malloc.h... yes
    checking for pwd.h... yes
    checking for unistd.h... yes
    checking for paths.h... yes
    checking for inet_addr in -lxnet... no
    checking for socket in -lsocket... no
    checking for gethostbyname in -lnsl... yes
    checking for pthread_cancel in -lc_r... no
    checking for pthread_cancel in -lpthread... yes
    checking for dlopen in -lc_r... no
    checking for dlopen in -lc... no
    checking for dlopen in -ldl... yes
    checking for dlopen modes... RTLD_LAZY
    checking for inet_addr... yes
    checking for inet_aton... yes
    checking for mktime... yes
    checking for select... yes
    checking for strdup... yes
    checking for strerror... yes
    checking for hstrerror... yes
    checking for readdir_r... yes
    checking whether to enable SOCKS5 support... no
    checking if OpenSSL support is desired... yes
    checking for openssl/ssl.h... no
    checking if OpenSSL support can be enabled... no
    checking for vector.h... no
    configure: error: You need to have the libstdc++ headers installed

    Problem is, i do have the libstdc++ program installed and everything else called "libstdc++", if there is anything else then please i'm all ears.
     
  7. Mictlantecuhtli TS Special Forces Posts: 4,916   +9

    It probably expects certain version of that library. Some buggy apps do. They can be fooled by creating a link from existing libstdcc* to the one they want, I don't know what licq wants however.

    The problem could be that as you're using a new OS, libraries have been updated, which means that their filenames are changed, so applications don't find them anymore.

    Sorry that things are this difficult, usually apps compile with just a few commands.
  8. CrackedButter Newcomer, in training Posts: 41

    Difficult yes, i can see why its such a chore to install programs in linux as opposed to windows.
    Makes me think i am doing something wrong.