[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#851146: libcc1: COMPILER_NAME should be gcc



Control: tags -1 + fixed-upstream 

On Thursday, January 12 2017, Matthias Klose wrote:

> On 12.01.2017 13:16, Thadeu Lima de Souza Cascardo wrote:
>> Package: libcc1-0
>> Version: 6.3.0-2
>> Severity: normal
>> 
>> When using the compile option in gdb, I get:
>> 
>> Could not find a compiler matching "^(x86_64|i.86)(-[^-]*)?-linux(-gnu)?-x86_64-linux-gnu-gcc-6$"
>> 
>> gdb already adds the arch and os. Then libcc1 adds it again. By default,
>> COMPILER_NAME in libcc1 is simply gcc. I was not able to dig deeper and
>> find out why it's built with x86_64-linux-gnu-gcc-6, but that seems to
>> be the cause of that failure in gdb.
>
> that's because GCC is configured using --program-prefix=x86_64-linux-gnu- (and
> it always was configured with --program-suffix=-6).  gdb should expect suffix
> and prefix.
>
> I'm working around that in gcc-6 now, but that should be fixed in gdb.

Hi there,

The patch has been finally accepted upstream:

  <https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=254838>
  <https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=a053adad92d7f3d26f1e5c6055ccef4525e4e39b>

With this, Debian GDB should work fine and not require any more hacks on
the GCC side.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Attachment: signature.asc
Description: PGP signature


Reply to: