Bug#644990: NEWS.Debian.gz: s/$arch/<triplet>
Sedat Dilek wrote:
> I am unsure how to interpret "you might try to pass the following
> option to your: -B/usr/lib/<triplet> -I/usr/include/<triplet>"?
> Normally, I would expect to do:
> export CFLAGS="$CFLAGS -B/usr/lib/<triplet> -I/usr/include/<triplet>"
> But in case of gcc-trunk upstream this change impacts:
It means that you might want to pass those flags to the compiler.
The compiler doesn't examine any environment variables, so your
"export CFLAGS" incantation isn't going to do that, depending on the
When building a compiler, there is a bootstrap step, meaning there are
multiple compilers to pass the flags to. I thought there was already
a bug report about making this easier (#637232) which unfortunately no
one seems to be working on.
> The generated compiler needs a wrapper-script to use -B and -I options.
> BTW, I could compile mesa, but not use the same wrapper-script with
> kernel-buildsystem from Debian Kernel Team.
That's probably because in debian/config.defines, we have
So if your gcc-4.5 comes from upstream, you would need to install a
/usr/local/bin/gcc-4.5 wrapper, too.
But what does this have to do with the "<triplet>" text in libc6-dev's