Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 31 Dec 2004 14:17:44 -0800
From:      "David O'Brien" <obrien@FreeBSD.org>
To:        Trevor Johnson <trevor@jpj.net>
Cc:        ports-committers@FreeBSD.org
Subject:   Re: cvs commit: ports/emulators/linux_base-8 Makefile
Message-ID:  <20041231221744.GA15683@dragon.nuxi.com>
In-Reply-To: <20041231145300.K12851@blues.jpj.net>
References:  <200412301941.iBUJf2kF035884@repoman.freebsd.org> <20041231003456.GB23359@dragon.nuxi.com> <20041231145300.K12851@blues.jpj.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 31, 2004 at 03:11:09PM -0500, Trevor Johnson wrote:
> David O'Brien wrote:
> 
> > On Thu, Dec 30, 2004 at 07:41:02PM +0000, Trevor Johnson wrote:
> > > trevor      2004-12-30 19:41:02 UTC
> > >
> > >   FreeBSD ports repository
> > >
> > >   Modified files:
> > >     emulators/linux_base-8 Makefile
> > >   Log:
> > >   On amd64, the installation script contained in the glibc RPM fails.
> > >   Work around this by using the --noscripts option.
> > >
> > >   PR:             75645
> > >   Submitted by:   Carlos F. A. Paniago and Conrad J. Sabatier
> > >
> > >   Revision  Changes    Path
> > >   1.94      +1 -0      ports/emulators/linux_base-8/Makefile
> > > http://cvsweb.freebsd.org/ports/emulators/linux_base-8/Makefile.diff?r1=1.93&r2=1.94
> >
> > Please back this out -- it is wrong as you didn't add code to manually do
> > all the things glibc's script does.  There is a reason I have't made this
> > change -- it gives the perception that this port now cleanly installs and
> > runs on AMD64 -- it doesn't (even with this change).  I've put a lot of
> > time into trying to polish the linux32 compat experience on FreeBSD/AMD64
> > and this undoes some of that effort.
> 
> When I made the port, I marked it with "ONLY_FOR_ARCHS=i386".  Without
> discussing it with me, you added amd64 to that with the log message "First
> cut at supporting AMD64 (to give 32-bit support)" and without adding any
> kind of warning that it was broken.  I don't have access to an x86-64
> computer but I got the impression from your commit that it was supposed to
> work.  Then the next day Mr. Paniagua pointed out that in fact it didn't.
> Without ever having heard from you on the subject of the AMD support, I
> decided that a kludge would be preferable to something that did not work
> at all.

I enabled people to (1) see the framework for how 32-bit linux support
should be handled on AMD64, and (2) enabled others to participated in the
debugging of the problems which lead to multiple fruitfull threads on the
freebsd-amd64@ mailing list.

-- 
-- David  (obrien@FreeBSD.org)



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