7 replaced http://raspberrypi.stackexchange.com/ with https://raspberrypi.stackexchange.com/
source | link
6 added 291 characters in body
source | link

This is more or lessin part a duplicate of these questions:

Although since apt has a new, simplified, slightly snazzier interface I'll giveuse the new version here and make the common point more clear.

This is rarely necessary and should only be done as a last resort or because you need a particular version of something which is unavailable. In that case you install to /usr/local and subsequently run ldconfig for shared libraries so the linker will index them.

That's an odd one but I notice it's true on one of mineRaspbian even when gcc is installed. apt search gcc | grep doc turns up various doc packages.

Looking in /usr/share/man, you can see man pages on Raspbian are installed in gzipped form with a section number suffix, e.g., foobar.3.gz. The basename is the name of the man page; based onfrom the descriptiondescriptions of man page sections in man man section 1 ("Executable programs or shell commands") is a pretty good guess here, but apt-file search gcc.1.gz implies some odd things, one of which is that the gcc package includes a c89-gcc man page and a c99.-gcc man page -- but these are just short stubs.

Sometimes the online Debian search works better, and trying gcc.1.gz via Search the contents of packages does claim it's in gcc-doc, except here we have a rare discrepancy -- there is no such package in Raspbian. They've done something odd again. I believe this is consequent of the fact that the architecture doesn't correspond to any of the Debian ARM branches (including armhf -- don't get confused by this), and the core C library and compiler are very specifically for ARM1176JZ(F)-S.

But there is a gcc-4.9-doc, and subsequent to apt install gcc-4.9-doc (a zany 14 MB...), you'll have a man gcc. It may actually be in the dependency, gcc-doc-base but a further likely Raspbian specific flub is that dpkg -L doesn't show it in either one (or anything that would add up to 14 MB). Go figure. This is probably also why apt-file doesn't find it properly.

Dunno why you'd want the static lib, but theThe online Debian search claims it is in the -dev package. apt-file search on Raspbian doesn't find it, but as we've seen, it is imperfect. Since you're installing the dev package anyway, check to see if it's in /usr/lib subsequently:

This is more or less a duplicate of these questions:

Although since apt has a new simplified, slightly snazzier interface I'll give the new version and make the common point more clear.

This is rarely necessary and should only be done as a last resort or because you need a particular version of something which is unavailable. In that case you install to /usr/local and subsequently run ldconfig for shared libraries so the linker will index them.

That's an odd one but I notice it's true on one of mine. apt search gcc | grep doc turns up various doc packages.

Looking in /usr/share/man, you can see man pages on Raspbian are installed in gzipped form with a section number suffix, e.g., foobar.3.gz. The basename is the name of the man page; based on the description of man page sections in man man 1 is a pretty good guess here, but apt-file search gcc.1.gz implies some odd things, one of which is that the gcc package includes a c89-gcc man page and a c99.gcc -- but these are just short stubs.

Sometimes the online Debian search works better, and trying gcc.1.gz via Search the contents of packages does claim it's in gcc-doc, except here we have a rare discrepancy -- there is no such package in Raspbian. They've done something odd again.

But there is a gcc-4.9-doc, and subsequent to apt install gcc-4.9-doc (a zany 14 MB...), you'll have a man gcc. It may actually be in the dependency, gcc-doc-base but a further likely Raspbian specific flub is that dpkg -L doesn't show it in either one (or anything that would add up to 14 MB). Go figure.

Dunno why you'd want the static lib, but the online Debian search claims it is in the -dev package. apt-file search on Raspbian doesn't find it, but as we've seen, it is imperfect. Since you're installing the dev package anyway, check to see if it's in /usr/lib subsequently:

This is in part a duplicate of these questions:

Although since apt has a new, simplified, slightly snazzier interface I'll use the new version here and make the common point more clear.

This is rarely necessary and should only be done as a last resort or because you need a particular version of something which is unavailable. In that case you install to /usr/local and subsequently run ldconfig for libraries so the linker will index them.

That's an odd one but I notice it's true on Raspbian even when gcc is installed. apt search gcc | grep doc turns up various doc packages.

Looking in /usr/share/man, you can see man pages on Raspbian are installed in gzipped form with a section number suffix, e.g., foobar.3.gz. The basename is the name of the man page; from the descriptions of man page sections in man man section 1 ("Executable programs or shell commands") is a good guess, but apt-file search gcc.1.gz implies some odd things, one of which is that the gcc package includes a c89-gcc and c99-gcc man page -- but these are just short stubs.

Sometimes the online Debian search works better, and trying gcc.1.gz via Search the contents of packages does claim it's in gcc-doc, except here we have a discrepancy -- there is no such package in Raspbian. They've done something odd again. I believe this is consequent of the fact that the architecture doesn't correspond to any of the Debian ARM branches (including armhf -- don't get confused by this), and the core C library and compiler are very specifically for ARM1176JZ(F)-S.

But there is a gcc-4.9-doc, and subsequent to apt install gcc-4.9-doc (a zany 14 MB...), you'll have a man gcc. It may actually be in the dependency, gcc-doc-base but a further likely Raspbian specific flub is that dpkg -L doesn't show it in either one (or anything that would add up to 14 MB). Go figure. This is probably also why apt-file doesn't find it properly.

The online Debian search claims it is in the -dev package. apt-file search on Raspbian doesn't find it, but as we've seen, it is imperfect. Since you're installing the dev package anyway, check to see if it's in /usr/lib subsequently:

5 added 387 characters in body
source | link

Library packages are usually installed as dependencies of other binaries. To serve at runtime, the headerinclude/header files (i.e., .h files) are not required, so these are kept in a separate -dev package (there may be other non-essential odds and ends as well, and possibly debugging symbols are in yet another package, but gdb should explain this to you when you need them).

So the headers can probably be installed via apt install libfcgi-dev. Likely in this case so are the static archives (see below).

Beware while this one works, it is dependent on the package database info being correct, which is sometimes not the case on Raspbian -- presumably it happens when lib packages must be split in odd ways but there is not the resources people wise to manage them all properly. There are a few examples of this coming up.

That's an odd one but I notice it's true on one of mine. apt search gcc | grep doc turns up various doc packagepackages.

But there is a gcc-4.9-doc, and subsequent to apt install gcc-4.9-doc (a zany 14 MB...), you'll have a man gcc. It may actually be in the dependency, gcc-doc-base but a further likely Raspbian specific flub is that dpkg -L doesn't show it in either one (or anything that would add up to 14 MB). Go figure.

If it's not, it has been left out and presumably either you make do with the .so or else build from source.

Library packages are usually installed as dependencies of other binaries. To serve at runtime, the header files (i.e., .h files) are not required, so these are kept in a separate -dev package (there may be other non-essential odds and ends as well, and possibly debugging symbols are in yet another package, but gdb should explain this to you when you need them).

So the headers can probably be installed via apt install libfcgi-dev.

That's an odd one but I notice it's true on one of mine. apt search gcc | grep doc turns up various doc package.

But there is a gcc-4.9-doc, and subsequent to apt install gcc-4.9-doc (a zany 14 MB...), you'll have a man gcc. It may actually be in the dependency, gcc-doc-base but a further likely Raspbian specific flub is that dpkg -L doesn't show it either one (or anything that would add up to 14 MB). Go figure.

Library packages are usually installed as dependencies of other binaries. To serve at runtime, the include/header files (i.e., .h files) are not required, so these are kept in a separate -dev package (there may be other non-essential odds and ends as well, and possibly debugging symbols are in yet another package, but gdb should explain this to you when you need them).

So the headers can probably be installed via apt install libfcgi-dev. Likely in this case so are the static archives (see below).

Beware while this one works, it is dependent on the package database info being correct, which is sometimes not the case on Raspbian -- presumably it happens when lib packages must be split in odd ways but there is not the resources people wise to manage them all properly. There are a few examples of this coming up.

That's an odd one but I notice it's true on one of mine. apt search gcc | grep doc turns up various doc packages.

But there is a gcc-4.9-doc, and subsequent to apt install gcc-4.9-doc (a zany 14 MB...), you'll have a man gcc. It may actually be in the dependency, gcc-doc-base but a further likely Raspbian specific flub is that dpkg -L doesn't show it in either one (or anything that would add up to 14 MB). Go figure.

If it's not, it has been left out and presumably either you make do with the .so or else build from source.

4 added 411 characters in body
source | link
3 added 996 characters in body
source | link
    Post Undeleted by goldilocks
2 added 996 characters in body
source | link
    Post Deleted by goldilocks
1
source | link