Hi,
(Sorry for the delay I'm just back from a long sick leave)
There is this old patch submitted by Matthias on that same issue, if
its logic is the right one for you Joseph I can rebase/validate it
Joseph.
https://gcc.gnu.org/ml/gcc-patches/2012-02/msg00320.html
Yes, that seems better.
On 07/15/2015 02:34 AM, Yvan Roux wrote:
Hi,
(Sorry for the delay I'm just back from a long sick leave)
There is this old patch submitted by Matthias on that same issue, if
its logic is the right one for you Joseph I can rebase/validate it
Joseph.
Hi,
On 8 May 2015 at 00:07, Joseph Myers jos...@codesourcery.com wrote:
On Mon, 20 Apr 2015, Pavel Kopyl wrote:
Hi all,
To build a GCC-4.9.2 ARM cross-compiler for my setting I need to configure it
with --with-sysroot=/ --with-gxx-include-dir=/usr/include/c++/4.9.2.
But I found that gcc
On Thu, 21 May 2015, Yvan Roux wrote:
There is this old patch submitted by Matthias on that same issue, if
its logic is the right one for you Joseph I can rebase/validate it
Joseph.
https://gcc.gnu.org/ml/gcc-patches/2012-02/msg00320.html
Yes, that seems better.
--
Joseph S. Myers
On Mon, 20 Apr 2015, Pavel Kopyl wrote:
Hi all,
To build a GCC-4.9.2 ARM cross-compiler for my setting I need to configure it
with --with-sysroot=/ --with-gxx-include-dir=/usr/include/c++/4.9.2.
But I found that gcc driver removes the leading slash from resulting paths:
`gcc
Hi all,
To build a GCC-4.9.2 ARM cross-compiler for my setting I need to
configure it with --with-sysroot=/
--with-gxx-include-dir=/usr/include/c++/4.9.2.
But I found that gcc driver removes the leading slash from resulting paths:
`gcc -print-prog-name=cc1plus` -v
...
ignoring nonexistent
