https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
Sebastian Huber changed:
What|Removed |Added
CC||sebastian.huber@embedded-br
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #10 from Chris Johns ---
(In reply to Joel Sherrill from comment #9)
> Yes. I believe it is the same bug. Use of GNU sed specifics on a system
> without GNU sed.
>
> I don't know if that changes the resolution.
For this bug that is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
Joel Sherrill changed:
What|Removed |Added
CC||joel at gcc dot gnu.org
--- Comment #9 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #8 from joel.sherrill at oarcorp dot com ---
Yes. I think they are exactly the same.
--joel
On Sep 9, 2017, at 5:50 PM, chrisj at rtems dot org
mailto:gcc-bugzi...@gcc.gnu.org>> wrote:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #7 from Chris Johns ---
Is this bug the same as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62097
As that bug states this issue is present on darwin and the patch I posted fixes
the issues on that host.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #6 from Chris Johns ---
Created attachment 41380
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41380&action=edit
Use awk to create compile args as sed is not working on FreeBSD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #5 from Chris Johns ---
I have decided to revisit this bug and see what the issue is. I cannot see how
to reopen the issue?
Using GNU sed on FreeBSD is not straight forward. It requires either building
by hand to a custom prefix with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
Andrew Pinski changed:
What|Removed |Added
Target||mips-rtems4.11
Status|UNCONF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #3 from Chris Johns ---
Built GNU sed from source and added to my path:
ruru rtems $ sed --version
GNU sed version 4.2
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #2 from Chris Johns ---
(In reply to Andrew Pinski from comment #1)
> Have you tried GNU sed rather than BSD sed?
No and a good idea. I will.
FYI I tend to keep the machines used for testing builds clean and minimal to
minimised th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66032
--- Comment #1 from Andrew Pinski ---
Have you tried GNU sed rather than BSD sed?
11 matches
Mail list logo
