From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) by sourceware.org (Postfix) with ESMTPS id 747483858026 for ; Mon, 7 Dec 2020 21:51:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 747483858026 Received: by mail-ed1-x52a.google.com with SMTP id b73so15377743edf.13 for ; Mon, 07 Dec 2020 13:51:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lrFLRNGewi/6oCRqjKwb47JddHJq/u95E0rH565gTSM=; b=FeSOLZf6Ug/WO53BrvzfAP7LFTivCGhNjmk6VKuA2+17//PCg4YxN+yqjef+BmcK7v DZGrIVfMDqhV614khQ7/Z4J4u9HC0erZcp8G247mk9NpktTGrhqd0Tz1jDAQkm2WjrVj f4hOyyLNwvkBRDCAzZ2L+t1lW7Lini6t+soYuGaiOJJ/ebJThOdhcEgC6XSuZZVBrQV5 w1TA+zJ8L8W7hyzgbUNt67+CoJCynhx+W/fZLfwtfO3tZzLrHVsh81CgZcBu8kmZU3N5 xGpFIIbz4umudvMlg6YAubGAxRrfZITsSmWtLBI1L92Gl5oI6uT7D31bh0BP/qk43xpH MMmw== X-Gm-Message-State: AOAM532ZQZVg/AJH/MSdggDnb0ABXHdyyrpWJ1eheN7MDE2R/3hNLBFD M2MPjvm9b6mFbOyfS/Br++VuXNkQ3ulpxD/0F9M= X-Google-Smtp-Source: ABdhPJxmLqcWD07EDWLkYlOl8PSuIGJXv83t75hqtP4KrPBo0tI1Wbq0X/c7aGPk25N8KBl9BBt2k0fotqtSAv225mc= X-Received: by 2002:a50:d1d3:: with SMTP id i19mr21848724edg.72.1607377877478; Mon, 07 Dec 2020 13:51:17 -0800 (PST) MIME-Version: 1.0 References: <20201207203033.GI2309743@redhat.com> <87sg8h8i2e.fsf@keithp.com> In-Reply-To: <87sg8h8i2e.fsf@keithp.com> From: Vladimir V Date: Mon, 7 Dec 2020 22:51:06 +0100 Message-ID: Subject: Re: Problem building libstdc++ for the avr target To: Keith Packard Cc: Jonathan Wakely , libstdc++@gcc.gnu.org X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: libstdc++@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++ mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2020 21:51:20 -0000 It looks like the existing stdio was at least sufficient to build the iostream. I was mostly focusing on basic headers so haven't yet tested if it is functional. =D0=BF=D0=BD, 7 =D0=B4=D0=B5=D0=BA. 2020 =D0=B3. =D0=B2 21:41, Keith Packar= d : > Jonathan Wakely via Libstdc++ writes: > > >>and was resolved for the newlib. The fix was not applied for the avr-li= bc > >>targets although the rationale behind the solution > >>seems to be applicable there as well. I would like to ask what do you > think > >>about extending the scope of the solution to work > >>with avr-libc based builds as well? > > > > Yes, I think it makes sense. > > I've been working on making libstdc++ work with picolibc, which shares a > bunch of stdio code with avr-libc. I haven't tried my patches with > avr-libc, but I wonder if that would be a good thing to do? With those > patches, I'm able to use libstdc++'s iostream. > > -- > -keith >