Ask Fedora is community maintained and Red Hat or Fedora Project is not responsible for content. Content on this site is licensed under a CC-BY-SA 3.0 license.
| 2014-01-14 08:28:44 -0600 | received badge | ● Popular Question (source) |
| 2014-01-14 08:28:44 -0600 | received badge | ● Famous Question (source) |
| 2014-01-14 08:28:44 -0600 | received badge | ● Notable Question (source) |
| 2013-07-23 17:57:01 -0600 | commented answer | *-static library packages without -fPIC Thanks for info, but it doesn't seem to address the -fPIC question. |
| 2013-07-23 17:51:07 -0600 | commented answer | I tried to update fedora17 but when i restarted it is showing oh no something went wrong ,unable to start Don't worry if you get a message about failed spawn of dbus-launch. I believe this just means the new setting isn't applied yet. For me the new setting was applied once I logged off and back in. |
| 2012-07-29 14:02:50 -0600 | received badge | ● Editor (source) |
| 2012-07-29 14:01:48 -0600 | asked a question | *-static library packages without -fPIC Is it official policy that the *-static library packages are compiled without -fPIC? I've tried using libstdc++-static and libboost-static to statically link specific versions of these libraries into a shared module and neither of them had -fPIC so I had to start from scratch. I realize there are some disadvantages to -fPIC, but are they significant? If the *-static packages cannot be used for the purpose outlined above, would there be any support for providing *-static-fpic or something like that? I'm not sure how this is handled by other distros. I've noticed that the macports *-static packages seem to build with -fPIC. |
| 2012-07-05 01:42:20 -0600 | answered a question | lock/protect terminal in non-GUI mode Could you run in GNU Screen? |
Ask Fedora is community maintained and Red Hat or Fedora Project is not responsible for content. Content on this site is licensed under a CC-BY-SA 3.0 license.