From owner-freebsd-ports@FreeBSD.ORG Mon Mar 30 14:32:59 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C34D558D for ; Mon, 30 Mar 2015 14:32:59 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F925B52 for ; Mon, 30 Mar 2015 14:32:59 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2UEX5uL014419 for ; Mon, 30 Mar 2015 07:33:11 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: References: From: "Chris H" Subject: Re: devel/hub build failed on 8.4, how to proceed? Date: Mon, 30 Mar 2015 07:33:11 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <2f9b32561bce9916b208f3a6d3e5c200@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 14:32:59 -0000 On Mon, 30 Mar 2015 13:25:47 +0300 Kostantinos Koukopoulos wrote > Hello, > I'm maintaining devel/hub, and for the first time while doing so, a build > has failed: > > http://beefy5.nyi.freebsd.org/data/84i386-default/382532/logs/hub-2.2.0.log > > I have a couple of questions about how I should proceed. First: are we > (port maintainers) responsible for addressing this type of issue, where the > build fails only on a legacy release of FreeBSD? Second, assuming we don't > have the time to investigate the cause ourselves, is it acceptable to > simply open an issue with the upstream provider? Third, if and when we have > the time, is running a 8.4 jail on poudriere the easiest way to go about > debugging the issue? Since you are the maintainer, the answer is ultimately your choice. But your answers to the above questions will largely determine the ultimate value of your port. :) You needn't open a pr(1). [personally] I would wait to see if the problem actually manifests itself in "real life". poudriere is one option. But there is no good reason you can't create a jail, use a VM, or use any other means to create a suitable environment as a test bed, to isolate the problem/issue. Lastly; If you truly believe the problem exists in the source, you should report it upstream. Unless you want to fix it for them. :) P.S. don't forget that you can always mark the port broken for ARCH, or OSVERSION, or any combination of the two. > > Last, if anyone has any idea why a Golang build would fail with these > errors please share it with me: > > /var/tmp/go-link-ejdAoV/go.o(.text+0x1cc44): In function > 'runtime.mallocinit': /usr/local/go/src/runtime/malloc.c:219: relocation > truncated to fit: R_386_32 runtime.end > /var/tmp/go-link-ejdAoV/go.o(.debug_info+0x10f493): In function > 'time.Time.IsZero': > /usr/local/go/src/time/time.go:242: relocation truncated to fit: > R_386_32 runtime.end Purely a guess; maybe not 100% 32bit compatible? But I have no idea. --Chris > > > Thank you, > Konstantinos > > -- > |/ |/ Konstantinos > |\ |\ Koukopoulos > > VSRE messages are welcome*, Thanks! > * for more information see: http://vsre.info > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"