Date: Sun, 26 Aug 2007 11:10:47 -0500 From: "Scot Hetzel" <swhetzel@gmail.com> To: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> Cc: ports@freebsd.org, ports-amd64@freebsd.org Subject: Re: [ports-amd64@freebsd.org: freehdl-0.0.4_1 failed on amd64 7] Message-ID: <790a9fff0708260910w1661cdap6e9523ce02da407a@mail.gmail.com> In-Reply-To: <46D15117.90706@gmx.de> References: <20070805184359.GD21980@rot26.obsecurity.org> <46D15117.90706@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/26/07, [LoN]Kamikaze <LoN_Kamikaze@gmx.de> wrote: > Kris Kennaway wrote: > > FYI; can you please investigate and/or report to the developers? If > > you are already aware of this problem but do not yet have a fix, > > please mark the port BROKEN in the appropriate case, so that users do > > not unexpectedly encounter it. > > > > See http://pointyhat.freebsd.org for the full log. > > > > Thanks, > > Kris > > I cannot find a PR about this. So I'm just replying to the mail. > > The problem only appears when the gcc4 branch is used. The freehdl > developers > as well as me are mystified, because the gcc output does not contain any > hints > about the nature of the problem. > > I didn't find a way to check the gcc version in bsd.gcc.mk, so I don't know > how > to mark it broken properly. > > I had something like: > > .if GCC_VERSION >= 40 > BROKEN= gcc3 branch required > .endif > > in mind. Just add the following after bsd.ports.pre.mk: if ${OSVERSION} >= 700042 USE_GCC= 3.4 .endif This will allow the port to build on 7-CURRENT, and give you and the freehdl developers time to determine why the port fails to build with GCC 4.x OSVERSION=700042 is when GCC 4.x was imported into -CURRENT. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0708260910w1661cdap6e9523ce02da407a>