Hi,
any news on this one, as the issue with --with-sysroot and
--with-gxx-include-dir is still present in 4.8 ?
http://gcc.gnu.org/ml/gcc-patches/2012-02/msg00320.html
Thanks,
Yvan
PS. Sorry for the re-post, I don't have the original one in my history
On 08.02.2012 02:01, Joseph S. Myers wrote:
On Wed, 8 Feb 2012, Matthias Klose wrote:
there is one more issue, when configuring
--with-sysroot=/ --with-gxx-include-dir=/usr/include/c++/4.7
in that the leading / is stripped away in configure.ac. This case needs an
explicit check. Ok for the
On Wed, 8 Feb 2012, Matthias Klose wrote:
> there is one more issue, when configuring
>
> --with-sysroot=/ --with-gxx-include-dir=/usr/include/c++/4.7
>
> in that the leading / is stripped away in configure.ac. This case needs an
> explicit check. Ok for the trunk?
This looks like a case where
On 26.01.2012 18:57, Joseph S. Myers wrote:
On Thu, 26 Jan 2012, Matthias Klose wrote:
On 25.01.2012 17:45, Joseph S. Myers wrote:
On Wed, 25 Jan 2012, Matthias Klose wrote:
This can end up in generation for dependency files, and other files
parsing
the output. The solution I came up with is
On Thu, 26 Jan 2012, Matthias Klose wrote:
> On 25.01.2012 17:45, Joseph S. Myers wrote:
> > On Wed, 25 Jan 2012, Matthias Klose wrote:
> >
> > > This can end up in generation for dependency files, and other files
> > > parsing
> > > the output. The solution I came up with is to check for sysroot
On 25.01.2012 17:45, Joseph S. Myers wrote:
On Wed, 25 Jan 2012, Matthias Klose wrote:
This can end up in generation for dependency files, and other files parsing
the output. The solution I came up with is to check for sysroot set to '/' and
special case this in two places. Afaics, there are no
On Wed, 25 Jan 2012, Matthias Klose wrote:
> This can end up in generation for dependency files, and other files parsing
> the output. The solution I came up with is to check for sysroot set to '/' and
> special case this in two places. Afaics, there are no other places.
I could imagine a sysroot
when setting sysroot to / (for whatever reason), then search directories and
headers start with a double-slash, as seen with gcc -v.
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-linux-gnu/4.6/include
//usr/local/include
/usr/lib/gcc/x86_64-linux-gn
