From owner-freebsd-ports@freebsd.org Tue Sep 1 12:12:55 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8771E3C5721 for ; Tue, 1 Sep 2020 12:12:55 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BgmDQ2pqZz4Qyl for ; Tue, 1 Sep 2020 12:12:54 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 4BgmDN4Xpbz3n48; Tue, 1 Sep 2020 12:12:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1598962371; bh=T/k2/Em/7gIPXcs5fRQVq0A3 FnZ53CNLPPQt5IqGrfs=; b=fCA4iNjmwhVU+Rwf+comvuNbDnn2pnwu231loMTJ uosD2CzbO8z62UetZWHDRgofZckS0TGj2r66TsPjZkL/smw9XiQ8pktY2rJ/1t38 SEYcUqfNobhqOcU6GpIpLmlaVla0wfa+jj/xAV/QhuUYNdY8kBB4uohgrmr9775y yi4= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id cK3aox-d764G; Tue, 1 Sep 2020 12:12:51 +0000 (UTC) Received: from garnet.daemonic.se (unknown [94.136.80.38]) by mail.daemonic.se (Postfix) with ESMTPSA id 4BgmDM5m7sz3myt; Tue, 1 Sep 2020 12:12:51 +0000 (UTC) Subject: Re: pkg-fallout on one of the ports I maintain To: Bob Eager , freebsd-ports@freebsd.org References: <20200901104652.6159b223@raksha.tavi.co.uk> From: Niclas Zeising Message-ID: <2076493f-45dc-4c8f-16b4-4e62b056866a@daemonic.se> Date: Tue, 1 Sep 2020 14:12:50 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <20200901104652.6159b223@raksha.tavi.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4BgmDQ2pqZz4Qyl X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=daemonic.se header.s=20151023 header.b=fCA4iNjm; dmarc=pass (policy=none) header.from=daemonic.se; spf=pass (mx1.freebsd.org: domain of zeising@daemonic.se designates 176.58.89.161 as permitted sender) smtp.mailfrom=zeising@daemonic.se X-Spamd-Result: default: False [-3.01 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[daemonic.se:s=20151023]; FREEFALL_USER(0.00)[zeising]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-0.99)[-0.995]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[daemonic.se:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[daemonic.se,none]; NEURAL_HAM_SHORT(-0.02)[-0.025]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:36236, ipnet:176.58.89.0/24, country:US]; TAGGED_FROM(0.00)[freebsd]; MAILMAN_DEST(0.00)[freebsd-ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2020 12:12:55 -0000 On 2020-09-01 11:46, Bob Eager wrote: > Almost certainly the -fno-common problem with clang 11. > > This now defaults to -fno-common, which causes multiply defined symbols > at link time if something is declared global in more than one module > (instead of extern in all but one module). There is a similar problem > with gcc. > > Declaring -fno-common on your existing build will trigger the problem. > > What you are seeing (success) is because clang 11 isn't actually in > -CURRENT yet. When I fixed my ports, I had to install (build) clang 11 > (from llvm11) to do the testing. llvm 11 is imported into FreeBSD 13-currrent since about two weeks. If you have an older current, or are on a release, you can either add -fno-common to CFLAGS to trigger the issue, or install llvm11 from ports and use that. Regards Niclas > > On Tue, 1 Sep 2020 19:35:44 +1000 > Sean Greven wrote: > >> Hi there >> >> I have received a number of messages from pkg-fallout regarding the >> port I maintain, and pkg-fallout maintains that my port is broken. >> >> The really strange thing here is that I am able to build it in all the >> versions up till 13.0-CURRENT. >> The port builds without any errors. Any one with any ideas on how to >> troubleshoot this further? >> >> Below is the last piece of the error returned from pkg-fallout. >> >> cc: error: linker command failed with exit code 1 (use -v to see >> invocation) *** [fwknop] Error code 1 >> >> make[3]: stopped in >> /wrkdirs/usr/ports/security/fwknop/work/fwknop-2.6.10/client >> 1 error >> >> make[3]: stopped in >> /wrkdirs/usr/ports/security/fwknop/work/fwknop-2.6.10/client >> ===> Compilation failed unexpectedly. >> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the >> failure to the maintainer. >> *** Error code 1 >> > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >