From nobody Sat Mar 04 07:43:50 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PTH0z22Qnz3vhTT for ; Sat, 4 Mar 2023 07:44:35 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Received: from smtp6.goneo.de (smtp6.goneo.de [IPv6:2001:1640:5::8:31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PTH0x6YKTz3qZF; Sat, 4 Mar 2023 07:44:33 +0000 (UTC) (envelope-from freebsd@walstatt-de.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=walstatt-de.de header.s=DKIM001 header.b=T80j10BL; spf=none (mx1.freebsd.org: domain of freebsd@walstatt-de.de has no SPF policy when checking 2001:1640:5::8:31) smtp.mailfrom=freebsd@walstatt-de.de; dmarc=none Received: from hub1.goneo.de (hub1.goneo.de [85.220.129.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by smtp6.goneo.de (Postfix) with ESMTPS id 5D61C10A1EA8; Sat, 4 Mar 2023 08:44:26 +0100 (CET) Received: from hub1.goneo.de (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPS id BFDD410A1E96; Sat, 4 Mar 2023 08:44:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walstatt-de.de; s=DKIM001; t=1677915864; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KUs+u0dpg/bRmAHl+MFLYASGZxvo7KsVcc0cy6gcjGQ=; b=T80j10BLdrhMOsXdwOY1xAgaFTcyYunKstoAAAYTh2GH/z6J4arxFEWI58od3z2afNfJMY /k598cUP8VLlMCEuOrKGOjBQWfai0n3quL4eN8FK6gH/qL6ksqvqRTmrLNJa+K1FAmD28l yqJIsRSujMNcSNk+bH6F3RnM7X6WDtGlgIFfHZCLsTGFFD0+7LBhVCTtm3GMKM0zRRDDY2 FxVtuqYDBhpM5IL5z7FrMNDYUkQLH4KihaoccWHb6bHKccY0r2UkA0QnNvhRiGDBb0RrFw 0B+1gaZvSpda8S7SttYm37zrSmWo7j5W58Qe86/Birs8sXn7t/SNbJDssTjYZw== Received: from thor.intern.walstatt.dynvpn.de (dynamic-077-011-067-177.77.11.pool.telefonica.de [77.11.67.177]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hub1.goneo.de (Postfix) with ESMTPSA id 8447210A1E83; Sat, 4 Mar 2023 08:44:24 +0100 (CET) Date: Sat, 4 Mar 2023 08:43:50 +0100 From: FreeBSD User To: Dimitry Andric Cc: FreeBSD CURRENT Subject: Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C Message-ID: <20230304084417.69b7c461@thor.intern.walstatt.dynvpn.de> In-Reply-To: <6321CA49-A38A-4FC6-A41E-E9964C2A94E3@FreeBSD.org> References: <20230227192011.08f7aa8e@thor.intern.walstatt.dynvpn.de> <720721A7-B1ED-405B-98EB-04A3AFCA7FD5@gromit.dlib.vt.edu> <1F3F20A1-C2BC-4A33-ABFD-D20F4ADB67E8@FreeBSD.org> <20230302064153.12940fa8@thor.intern.walstatt.dynvpn.de> <6321CA49-A38A-4FC6-A41E-E9964C2A94E3@FreeBSD.org> Organization: walstatt-de.de List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/Xiwu.2GI9Hq9PaT4VuZMLFk"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Rspamd-UID: aba3a7 X-Rspamd-UID: 663b97 X-Spamd-Result: default: False [-5.37 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.97)[-0.969]; R_DKIM_ALLOW(-0.20)[walstatt-de.de:s=DKIM001]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; RCPT_COUNT_TWO(0.00)[2]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[walstatt-de.de:+]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_ALL(0.00)[]; HAS_ORG_HEADER(0.00)[]; ASN(0.00)[asn:25394, ipnet:2001:1640::/32, country:DE]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; R_SPF_NA(0.00)[no SPF record]; DMARC_NA(0.00)[walstatt-de.de]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4PTH0x6YKTz3qZF X-Spamd-Bar: ----- X-ThisMailContainsUnwantedMimeParts: N --Sig_/Xiwu.2GI9Hq9PaT4VuZMLFk Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 2 Mar 2023 11:13:51 +0100 Dimitry Andric schrieb: > On 2 Mar 2023, at 06:41, FreeBSD User wrote: > >=20 > > Am Mon, 27 Feb 2023 23:46:21 +0100 > > Dimitry Andric schrieb: =20 > ... > >=20 > > I tried to find some documentation on my CURRENT host regarding "WITH_= SYSTEM_COMPILER". > > None found via man src.conf, nor via make make.conf. Please delegate me= to some place > > where I can find such infos. =20 >=20 > Ah I was confused, WITH_SYSTEM_COMPILER is actually the default, and it > means that you want to skip building the bootstrap compiler, and just > use the host compiler. The src.conf(5) man page documents the inverse > settings instead: >=20 > WITHOUT_SYSTEM_COMPILER > Do not opportunistically skip building a cross-compiler duri= ng > the bootstrap phase of the build. Normally, if the currently > installed compiler matches the planned bootstrap compiler ty= pe > and revision, then it will not be built. This does not prev= ent a > compiler from being built for installation though, only for > building one for the build itself. The WITHOUT_CLANG option > controls that. >=20 > WITHOUT_SYSTEM_LINKER > Do not opportunistically skip building a cross-linker during= the > bootstrap phase of the build. Normally, if the currently > installed linker matches the planned bootstrap linker type a= nd > revision, then it will not be built. This does not prevent a > linker from being built for installation though, only for > building one for the build itself. The WITHOUT_LLD option > controls that. >=20 > This option is only relevant when WITH_LLD_BOOTSTRAP is set. >=20 > I find the double negative phrasing "do not skip" always confusing. But > the logic is normally: >=20 > * The early phase of buildworld retrieves the versions of your host's > compiler and linker > * It compares it against the versions in the source tree > * If the host compiler and linker are deemed "good enough", they are > used as-is > * If the host compiler or linker are not suitable, the compiler or > linker are bootstrapped from the source tree >=20 > But WITH_SYSTEM_COMPILER turns off all these checks and forces it to use > the host compiler, which might or might not work, depending on the > circumstances. You may have to use NO_WERROR or other tricks. Thank you for the explanation. I read the man page of src.conf in a haste s= olving my problem and did not spend much time in reading carefully. I'd appreciate to see YOU= R explanation in the official man page, or at least a more non-logical-twisted version. ;-) oh >=20 >=20 > ... > >> The safest solution is to let cross-tools do its thing, which will che= ck > >> the host compiler, and automatically build an appropriate version of t= he > >> compiler and linker for the stable branch, if required. =20 > >=20 > > I had a misunderstanding in the terminus "cross compiling", I check now= the build with this > > option set to be enabled. =20 >=20 > Yes, this is a bit confusing, but in fact it *can* be a real cross > compiler, if you are targeting another architecture, for example doing > "make buildworld TARGET=3Darm64" from an x86_64 host. >=20 > And of course if you are building natively, it is 'just' a regular > bootstrap compiler. >=20 > -Dimitry >=20 --=20 O. Hartmann --Sig_/Xiwu.2GI9Hq9PaT4VuZMLFk Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCZAL20QAKCRCxzvs8Oqok rwd5AQCe8KolJV0SYDQOsvtzAGi/Yzmq070tB7b/eRy9apLCVQEA8MknPQCx2+Uc se1SjTA2RalPExEVUNtmVpPFP+jqVg8= =9Ilg -----END PGP SIGNATURE----- --Sig_/Xiwu.2GI9Hq9PaT4VuZMLFk--