On Aug 17 12:19, Ruben Van Boxem wrote: > 2012/8/17 Corinna Vinschen <[email protected]> > > On Aug 16 08:16, NightStrike wrote: > > > Even if I agreed with the with-sysroot default, these should be > > > committed as two separate things. So, approved for the /include bug. > > > We should talk about the with-sysroot default. I'm interested to hear > > > what Ozkan and Ruben have to say. > > > > Thanks, I applied the /include fix. > > > > As for sysroot, I seriously don't understand what it's good for to set > > sysroot == prefix. This is not at all what sysroot is supposed to be. > > prefix is supposed to be relative to sysroot, the full path is > > $sysroot/$prefix. > > > > The default setting for sysroot is usually the system's root, which is > > "/" (or better "" for path evaluation reasons) or its non-POSIX > > counterpart. So, assuming prefix is /usr, for a native system the > > result of $sysroot/$prefix is /usr. For a cross toolchain you change > > the sysroot accordingly. For instance, for the Fedora Mingw cross > > you set sysroot to "/usr/${cpu}-w64-mingw32/sys-root" and prefix to > > "/mingw", so youll find the include and lib dirs under > > /usr/${cpu}-w64-mingw32/sys-root/mingw. > > > > For my Arch Linux cross-compilers I don't use a sysroot: there's no point. > Just install to prefix=/usr and be done with it. > Every prefixed binary is placed nicely in /usr/bin, every target dependent > thing is placed in /usr/$TARGET. There are no conflicts anywhere, and this > goes right alongside any other GCC install. > > I don't see the need for a sysroot except for when it's *equal* to prefix, > to get a relocatable toolchain. > > Why you would add an extra sys-root directory, and even use prefix /mingw > is beyond me.
sysroot is for the installation of target files. Your host tools are not supposed to go there. Corinna ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
