Bug#851146: libcc1: COMPILER_NAME should be gcc

[Sergio Durigan Junior]

On Tuesday, November 21 2017, I wrote:

> 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:
>
>   
>   
> 

Cascardo kindly mentioned that the ChangeLog entries are not very useful
here.  Here's the link to the discussion thread.  Unfortunately the
mailing list archive software doesn't inter-month discussions, but this
message should contain all the relevant details:

  

Thanks,

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


signature.asc
Description: PGP signature

Bug#851146: libcc1: COMPILER_NAME should be gcc

[Sergio Durigan Junior]

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:

  
  


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/


signature.asc
Description: PGP signature

Bug#851146: libcc1: COMPILER_NAME should be gcc

[Matthias Klose]

clone 851146 -1
reassign -1 src:gdb
thanks

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.

Matthias

Bug#851146: libcc1: COMPILER_NAME should be gcc

[Thadeu Lima de Souza Cascardo]

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.

Thanks.
Cascardo.


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-rc5+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcc1-0 depends on:
ii  gcc-6-base  6.3.0-2
ii  libc6   2.24-8
ii  libgcc1 1:6.3.0-2
ii  libstdc++6  6.3.0-2

libcc1-0 recommends no packages.

libcc1-0 suggests no packages.

-- no debconf information