On Mon, 2006-02-27 at 15:17 +0100, Ralf Corsepius wrote: > On Mon, 2006-02-27 at 08:08 -0600, Joel Sherrill wrote: > > Ralf Corsepius wrote: > > > > >On Sun, 2006-02-26 at 18:29 -0500, Frank Ch. Eigler wrote: > > > > > > > > >>Hi - > > >> > > >>On Sun, Feb 26, 2006 at 10:54:09PM +0100, Gerald Pfeifer wrote: > > >> > > >> > > >>>On Sun, 26 Feb 2006, Ralf Corsepius wrote: > > >>> > > >>> > > >>>>Cross building and installing gcc-4.1.0 rc2 (--prefix=/usr/local) > > >>>>installs these headers: > > >>>>[...] > > >>>> > > >>>> > > >>>Related problems include Bugzilla #23935 ($PREFIX/include/ffi.h), > > >>>#25938 ($PREFIX/include/gomp.h), and #18244 (include/mf-runtime.h). > > >>>Frank, any chance you could look into the mudflup one? > > >>> > > >>> > > >>I'm not fresh on gcc configury details. If anyone can send a pointer > > >>to the relevant autoconf or derived value, that would be great. > > >> > > >> > > > > > >/me thinks this isn't a bug inside of the Makefile.am, but either > > >- a bug in toplevel configure script, which gets exposed in all the > > >library subpackages, mentioned above (you would have to call these > > >subpackages' configure with an explicit --includedir=<correct directory, > > >then) > > >- a bug inside of the subpackages' configure scripts (you would have to > > >compose the correct includedir inside, them). > > > I don't know what it is but I do hope this is considered a critical > > packaging error > > and fixed before a final release. > > Cf. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26473 > > I've just attached a patch that seems to solve this issue for me. Thinking about this once more, I think my patch is equally wrong. These headers shouldn't be installed to includedir at all, but should be installed into gcc's internal include dir ($libdir/gcc/$target_alias/$version/include)
Ralf
