Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Nov 2010 19:17:50 GMT
From:      Dimitry Andric <dim@FreeBSD.org>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/152268: [exp-run] check projects/binutils-2.17 for ports breakage
Message-ID:  <201011151917.oAFJHosF048286@www.freebsd.org>
Resent-Message-ID: <201011151920.oAFJK5oA000626@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         152268
>Category:       ports
>Synopsis:       [exp-run] check projects/binutils-2.17 for ports breakage
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Mon Nov 15 19:20:05 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Dimitry Andric
>Release:        9.0-CURRENT
>Organization:
The FreeBSD Project
>Environment:
FreeBSD vfbsd9.home.andric.com 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r214540: Sat Oct 30 02:08:56 CEST 2010     dim@vfbsd9.home.andric.com:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
I am working on a project to integrate binutils 2.17.50 into the FreeBSD
base system.  This is the last version that was released under GPLv2.

I created a branch from head, into:

svn://svn.freebsd.org/base/projects/binutils-2.17

where all this work has been integrated.  It has been last synchronized
with head at r215318, and can be built in exactly the same way as normal
head.

Obviously, changing binutils influences almost all executable, object
and library files in base.  I have several amd64 and i386 test machines
running without issues, and confirmation from people that arm, powerpc,
sparc64 etc also work.  I have also built all ports that I normally use
during daily work, on both amd64 and i386, and I have seen no issues at
all.

So now I want to request an exp-run using a world (and optionally
kernel) built from this project branch, to see if there any ports that
suffer from updated binutils.  For example, the version numbers that as,
ld, and so on report are now changed to 2.17.50, and most of the
binutils programs have gained a few, or even many, new features.  This
might trip up configure scripts, or other assumptions.

Instructions are roughly:

  svn co svn://svn.freebsd.org/base/projects/binutils-2.17
  make -C binutils-2.17 buildworld buildkernel installkernel
  [reboot]
  make -C binutils-2.17 installworld
  [reboot]
  [update ports tree]
  [rebuild all ports]

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011151917.oAFJHosF048286>