Sponsored Content
Operating Systems Linux SuSE Errors while trying to install software on SuSE 9.2 Pro Post 58092 by zazzybob on Saturday 13th of November 2004 06:57:27 AM
Old 11-13-2004
Do you have the kernel source installed?

Have a look at /usr/src/linux and see if it's populated.

When I installed SUSE, I installed all development packages (I think theres an option during the installation that'll allow you to specify that you want to install the "Development" group of packages.)

If you're going to be compiling a lot of programs from source, these require development packages to be installed. If you've got the hard disk space, then I'd definitely recommend installing as much as possible.

If you don't want the development/source packages, then your only option is to install from RPM.

Cheers
ZB
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to install Suse Linux 8.1?

Can anyone tell me how to install Suse Linux 8.1? :( (6 Replies)
Discussion started by: Micheal
6 Replies

2. UNIX for Dummies Questions & Answers

absolute beginner with suse 9.2 and XP Pro

I'm sure this is pretty infantile but I can't figute it out. How to I load the nVidia driver for SuSE 9.2? I have no idea what the X environment is or how to quit it or how to run the nVidia patch. Secondly how do I persuade my SuSE 9.3 computer to talk with my Windows XP network. Linux... (9 Replies)
Discussion started by: mrgmwsnow
9 Replies

3. SuSE

Best Repository for SUSE 10.1 install?

I've made a few attempts at an OpenSuse10.1 clean install using a boot.iso and network repository install dir. I've succesfully done a few network installs before and know what I'm doing with the procedure, however I seem to be getting problems with the connection to the remote repository. It's... (0 Replies)
Discussion started by: Mark Ward
0 Replies

4. UNIX for Dummies Questions & Answers

Reflections & Pro Com Software?

I am looking for a replacement to my Pro-Com software to use on UNIX based applications at work. I am a virtual remote employee who works from my home using a windows XP machine. On my company laptop, another Win XP, we use REFLECTION v12 for UNIX and OPEN VMS. I really like REFLECTIONS a lot... (3 Replies)
Discussion started by: dereckbc
3 Replies

5. Linux

install macbook pro fedora10 ???((<<if can install, how to install? >> ))

If may install can Tells everybody ??? (0 Replies)
Discussion started by: kzBSD
0 Replies

6. Red Hat

Install Suse from RedHat

Hi, There are two systems: (1) HP server under RedHat Linux with CD drive. (2) Notebook under Windows Vista with DVD drive. Now I want to install Suse Linux on the HP server, but the installation media is a DVD. How can I do it? Thank you much in advance! (3 Replies)
Discussion started by: aixlover
3 Replies

7. UNIX for Dummies Questions & Answers

How to use yast2 to install software in SUSE?

Hi I ssh to a remote server which is running in SUSE. And I want to install apache2.0 there. Then I used yast2 to install it. But after installing it, I go to the terminal and type" apache -version" to check if apache is installed there. And it said "-bash: apache: command not found" I don't... (0 Replies)
Discussion started by: AlexCheung
0 Replies

8. Fedora

Install memcached on Suse 11 SP2

hi guys I am trying to install this extension for php named memcached but I am not really able to do it PECL :: Package :: memcached I have Suse 11 SP2 installed without any registration (I mean installed not paying subscription) so my question is there a way to install it like in... (0 Replies)
Discussion started by: karlochacon
0 Replies

9. UNIX and Linux Applications

Pro*c file Compiling Issue in suse Linux

The existing .pc (pro *C) file is running successfully in UNIX. But when Iam trying to compile this same file in LINUX using proc iname filename.pc, Iam getting an error, proc file not recognized. Could someone help how to generate execute file from the proc*c file. what are the prerequisites... (2 Replies)
Discussion started by: vikrambharat
2 Replies

10. AIX

Install software in another directory with smitty install

Hello, I would like to ask if someone knows if is possible to install sofware via smitty or installp in another directorie , or we have to accept the default location? i would like to intall in /opt folder , but smitty installed it in /usr Thanks in advance (4 Replies)
Discussion started by: prpkrk
4 Replies
APT-SRC(1p)						User Contributed Perl Documentation					       APT-SRC(1p)

NAME
apt-src - manage debian source package trees SYNOPSIS
apt-src [options] command apt-src [options] install|remove pkg1 [pkg2 ...] apt-src location pkg DESCRIPTION
apt-src is a command line interface for downloading, installing, upgrading, and tracking debian source packages. It can be run as a normal user, or as root. Unlike binary packages, source packages are not installed into a canonical location. Instead, they are "installed" by unpacking their source tree into a directory, which can be anywhere you wish. A source package can be installed multiple times, in different locations. This program manages source packages installed in this way, and provides querying facilities to help find where a source package is installed. Unless the -h or --help option is given one of the commands below must be present. update Update the lists of available packages. Identical to apt-get update, really, and must be run as root in the default configuration. install Install the named source package or packages into the current directory. If a package in the current directory is already installed, it will attempt to upgrade it. This command will accept the names of binary packages, or source packages. Just like with apt-get install, you can prefix the name with =version or /release to specify what version to install or what release to take the source from. It will make sure that the build-dependencies of the source package are satisfied. If the --location option is given, the source package will be installed or upgraded into the given location instead of the current directory. If the --build option is given, each newly installed or upgraded package will be compiled. upgrade Upgrade all installed source packages, or, if the --location or --here options are used, update only source packages in the specified directory. If the --patch option is given (the default), apt-src will attempt to generate a patch containing any local changes made to the source package, and will apply this patch to the updated tree. This will allow your local changes to be preserved across package upgrades, but it may not always work, and you might sometimes have to merge in your changes by hand. If the --build option is given, each newly installed or upgraded package will be compiled. remove Remove the named source package or packages. The --location and --here options may be used to only remove packages in a particular directory. build Build the specified source or sources. If the source is not installed yet, it will first be installed. clean Clean the trees of the named source package or packages. The --location and --here options may be used to only clean packages in a par- ticular directory. import Use this option to let apt-src know about an existing, unpacked source tree. Besides the name under which it should be imported, you must specify the location of the source tree (with --location), and you may need to tell the version of the source (with --version). Don't expect the build command to work on this source, unless it has a debian/ directory. list With no other parameters, it will list all installed source packages; their status, and the directory they are installed in. If a pack- age's name is given, it will display only installed instances of that source package. If the --location or --here options are used, they will limit the list to packages in the specified directory. location Takes a single parameter; the name of a source package. If the package is installed, it will return the root of the package's source tree. This command can be used when you need to include files from another source package, or something like that. For example: -I`apt-src location pkg` version Takes a single parameter; the name of a source package. If the package is installed, it will return the version of the package that is installed. name Takes a single parameter; the name of a source package (may be specified with regexps). Returns the name of the source package installed matching that name, if any. OPTIONS
All command line options may be set using the configuration file, the descriptions indicate the configuration option to set. For boolean options you can override the defaults file by using something like -f-,--no-f, -f=no or several other variations. -h, --help Show this help text. -b, --build, --compile Build source packages after installing or upgrading them. Configuration Item: APT::Src::Compile. -i, --installdebs Install packages after building sources. Implies --build. Configuration Item: APT::Src::InstallDebs Note that if multiple packages are generated from a single source package, they will all be installed. -p, --patch Try to patch local changes into new source tree when upgrading. On by default, use --no-p to disable. Configuration Item: APT::Src::Patch. -l, --location Specify a directory; only operate on packages in that directory. Configuration Item: APT::Src::Location. -c, --cwd, --here Only operate on packages in the current directory. Configuration Item: APT::Src::Here. --upstream-version Only of use with the version command; makes it omit the debian version number from the version of the package output. -k, --keep-built Do not delete .debs and other built files after installing them with the --installdebs option. Configuration Item: APT::Src::KeepBuilt -n, --no-delete-source Do not delete source files when removing source package. Configuration Item: APT::Src:NoDeleteSource --version Specify a source tree version. Of use with the import command. -q, --quiet Direct all command output to /dev/null unless a command fails to run as expected. Configuration item: APT::Src::Quiet -t, --trace Output each command as it is run. Configuration item: APT::Src::Trace In addition to the above options, some less-used configuration items may only be specified in the config files, /etc/apt/apt.conf and ~/.apt-src/config. They are: APT::Src::BuildCommand The command to use to build a tree. Run in the tree to build, it defaults to "dpkg-buildpackage -b -us -uc", with "-rfakeroot" appended for non-root users. APT::Src::RootCommand The command to use if a non-root user needs to become root. This is used for, example, to satisfy build-deps. sudo is a good choice and the default. If you want to use su, you'll need to set it to "su -c". APT::Src::BuildDeps Controls whether apt-src makes sure a source package's build dependencies are installed when installing or upgrading it. Defaults to true, if you turn it off, packages may fail to build due to missing build dependencies. NOTE ON NAMES
You can use either binary package names, or source package names when installing a new source package. The rest of the time, when dealing with already installed packages, you currently have to use the source package names (this may later changes). However, you may use regexps as part of the names. ENVIRONMENT
This program sets APT_SRC_BUILD when it is building a package. EXAMPLES
To install the source to pine to /usr/src, build it, and install the resulting debs: apt-src install --location=/usr/src -i pine To track changes to said installed pine source package, and install debs whenever a new version comes out: apt-src install -i pine To install a local copy of package foo, which you are going to apply a local patch to: apt-src install foo cd foo-version patch <~/my-foo-patch apt-src build --installdebs foo To upgrade your local copy of foo, bringing your patch forward, and building and installing new debs: apt-src install -i foo To import the source tree in /usr/src/linux, which you unpacked from a ftp.kernel.org tarball (or from the kernel-source package) into apt-src, so it knows about it: apt-src import kernel --location=/usr/src/linux --version=2.4.18 In a debian/rules of a kernel module package that needs to figure out if it is being built by apt-src, and if so set the KVERS, KSRC. and KDREV variables that make-kpkg normally sets: ifdef APT_SRC_BUILD KDREV=$(shell apt-src version kernel(-source.*)?) KSRC=$(shell apt-src location kernel(-source.*)?) KVERS=$(shell apt-src name kernel(-source.*)? | sed s/kernel-source-//) endif FILES
/etc/apt/sources.list Locations to fetch packages from. ~/.apt-src/status apt-src's status file, lists installed packages. /etc/apt/apt.conf Global config file for apt-src (and apt). ~/.apt-src/config Per-user config file for apt-src. SEE ALSO
apt-get(8), sources.list(5), dpkg-source(1) AUTHOR
Copyright 2002 Joey Hess <joeyh@debian.org> This is free software; see the GNU General Public Licence version 2 or later for copying conditions. There is NO warranty. perl v5.8.8 2004-05-22 APT-SRC(1p)
All times are GMT -4. The time now is 04:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy