From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50917 invoked by alias); 30 Mar 2017 13:08:57 -0000 Mailing-List: contact newlib-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: newlib-owner@sourceware.org Received: (qmail 50907 invoked by uid 89); 30 Mar 2017 13:08:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=BAYES_50,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*F:D*t-online.de, H*r:sk:mailout, H*r:sk:newlib@, crt0o X-HELO: mailout12.t-online.de Received: from mailout12.t-online.de (HELO mailout12.t-online.de) (194.25.134.22) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 30 Mar 2017 13:08:55 +0000 Received: from fwd05.aul.t-online.de (fwd05.aul.t-online.de [172.20.27.149]) by mailout12.t-online.de (Postfix) with SMTP id C939F41FBE02 for ; Thu, 30 Mar 2017 15:08:53 +0200 (CEST) Received: from [192.168.2.28] (rPbfrkZYrhgxUgXUBuPTiAVpY4V0AFLV8ECNtbWHSOLu7mEp-B9PwvznATaTbUWwS-@[91.59.15.253]) by fwd05.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1ctZog-0zYTmi0; Thu, 30 Mar 2017 15:08:42 +0200 Subject: Re: ARM EABI -specs=nosys crt0.o not being linked in To: "newlib@sourceware.org" References: From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= Message-ID: Date: Thu, 30 Mar 2017 13:08:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017/txt/msg00234.txt.bz2 Am 30.03.2017 um 08:54 schrieb Schwarz, Konrad: > To my thinking, nosys.specs, rdimon.specs, rdpmon.specs, linux.specs, > pid.specs, ... are mutually exclusive, since each defines an > interface to a "BIOS". It follows that nosys.specs should be > properly defining startfile. Is that correct? I'd say no, it's not. The name "nosys" should be read at face value: it says that there is _no_ system assumed. Which gives you the opportunity to specify the details of how the system is get up out of reset, by specifying your own choice of start-up file explicitly, on the command line. But that also gives you the _obligation_ to actually do it. Specs files exist to assist you with tailoring the compiler and tools to your system --- not to assume 100% of the job for every imaginable use case.