configure advertises the --with-pic (--without-pic) option, but it doesn't have any effect because the PIC/PIE flags are always enabled in configure.in if the compiler supports them.
Should remove the flag then.
Or they part of stock autoconf?
--with-pic, --without-pic are provided by libtool, which normally generates PIC for shared libraries, but not for static libraries. We link dbus-daemon and other D-Bus executables to a static version of libdbus, which lets them use certain APIs that aren't normally public.
We try to use -fPIE for dbus-daemon, so we can have a PIE (position-independent executable) dbus-daemon, which is good for avoiding system-bus exploits (you have to use PIC or PIE code for address space layout randomization to be effective). However, this requires us to force PIC code to be used in the static version of libdbus.
Why don't you want PIC code to be generated?
My use case for --without-pic was that gdb didn't have PIE support on at least one of the platforms I tried debugging dbus on (probably x86, but might have been armel; both machines are running Debian Squeeze). This has since changed (at least for x86 - haven't tried on armel recently).
No matter whether you're going to support this use case, please don't offer an option that doesn't work. Either make it work or remove the option. The current state is rather confusing.
We can't remove the option; it's one of the generic options offered by libtool.
However, if we resolve Bug #16621 by removing the goo that forces -fPIE to be used, that'll also resolve this bug.
*** This bug has been marked as a duplicate of bug 16621 ***