This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add Rust support to source highlighting
- From: Pedro Alves <palves at redhat dot com>
- To: Simon Marchi <simark at simark dot ca>, Tom Tromey <tom at tromey dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 2 Jul 2019 10:18:58 +0100
- Subject: Re: [PATCH] Add Rust support to source highlighting
- References: <20190624220539.16360-1-tom@tromey.com> <87ef3d2402.fsf@tromey.com> <8736jprcf0.fsf@tromey.com> <3b327ad7-36fe-018d-93aa-3d7ea541a80e@simark.ca>
On 7/2/19 1:29 AM, Simon Marchi wrote:
> On 2019-07-01 11:40 a.m., Tom Tromey wrote:
>>>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>>
>> Tom> I don't think there's anything wrong with the patch, so I guess this is
>> Tom> a Fedora bug somehow. I will see if I can write a test case and file
>> Tom> it.
>>
>> I debugged this a bit today, and the problem comes from the use of
>> "-static-libstdc++ -static-libgcc" when linking. Using just one of
>> these makes it work fine.
>>
>> Are these necessary for some reason?
>
> I never really knew the reason of using these in the first place.
>
IIRC, they're there for gcc, so that a newly built gcc does not depend
on system libstdc++/libgcc or something along those lines.
I.e., it's mainly a consequence of a shared top level. I think that
the ideal would be if linking with static-* was controllable some
configure switch, and, if it was only enabled by default if building gcc.
Combined gdb + gcc builds must be considered as well, since some people
still do that.
Thanks,
Pedro Alves