Issue : overwriting libstdc++ for a default target during building libraries for armv5te/mthumb-interwork

Issue : overwriting libstdc++ for a default target during building libraries for armv5te/mthumb-interwork

[Filip Bascarevic]

[-- Attachment #1: Type: text/plain, Size: 688 bytes --]

Dear GCC team,



I noticed that during building multilib for armv5te/mthumb-interwork,
libstdc++ and libsup++ are generated in a folder for a default target
(arm_none_eabi/lib) instead of arm_none_eabi/lib/armv5te/interwork. I think
an image from a log will be sufficient for describing a bug, please look at
the image in the attachment. It happens only for armv5te. For example armv7
doesn’t have this issue.

I have tried with releases gcc_9.2.0 and gcc_10.1.0. In both of the
releases, I noticed this problem. I tried to update the source file, but I
couldn’t find it.

Please let me know if I can assist any further.



With best regards,

Filip Bascarevic

[-- Attachment #2: part_of_gcc_log_armv5te.png --]
[-- Type: image/png, Size: 247661 bytes --]

Re: Issue : overwriting libstdc++ for a default target during building libraries for armv5te/mthumb-interwork

[Jonathan Wakely]

On 04/06/20 10:41 +0200, Filip Bascarevic via Libstdc++ wrote:
>Dear GCC team,
>
>
>
>I noticed that during building multilib for armv5te/mthumb-interwork,
>libstdc++ and libsup++ are generated in a folder for a default target
>(arm_none_eabi/lib) instead of arm_none_eabi/lib/armv5te/interwork. I think
>an image from a log will be sufficient for describing a bug, please look at
>the image in the attachment. It happens only for armv5te. For example armv7
>doesn’t have this issue.
>
>I have tried with releases gcc_9.2.0 and gcc_10.1.0. In both of the
>releases, I noticed this problem. I tried to update the source file, but I
>couldn’t find it.
>
>Please let me know if I can assist any further.

Could you please report this to bugzilla, so it doesn't vanish into
the mail archives? I don't know the reason for this behaviour, and the
ARM maintainers don't usually read this list.

Please provide details of exactly how you configured GCC and the
commands used to build it after configure. And plase provide the log
file (or the relevant part) in the bug, but as plain text not a PNG.

Thanks!