Subject: Re: has anyone else built firefox-220.127.116.11 with xsrc-current? (blows chunks compiling nsDeviceContextPS.cpp)
To: NetBSD Packages Technical Discussion List <tech-pkg@NetBSD.org>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 07/29/2006 18:19:49
Content-Type: text/plain; charset=US-ASCII
At Wed, 26 Jul 2006 23:27:03 +0200,
Joerg Sonnenberger wrote:
> On Wed, Jul 26, 2006 at 05:17:39PM -0400, Greg A. Woods wrote:
> > At Wed, 26 Jul 2006 22:53:10 +0200,
> > Joerg Sonnenberger wrote:
> > >=20
> > > On Wed, Jul 26, 2006 at 04:17:47PM -0400, Greg A. Woods wrote:
> > > > I'm trying to do what's probably a rather unorthodox build of
> > > > firefox-18.104.22.168 (from pkgsrc-2005Q4) on some netbsd-1-6 i386 and al=
> > > > machines with xsrc-current installed on them.
> > >=20
> > > Which GCC version are you using?
> > The standard version supplied in netbsd-1-6:
> > $ gcc -v
> > Using builtin specs.
> > gcc version 2.95.3 20010315 (release) (NetBSD nb3)
> That's what I wanted to make sure. C++ support in 2.95 is just so
> completely outdated and one area where hacking around doesn't make much
> sense or fun either. In fact, it is the one major reason why I consider
> 1.6 obsolete.
OK, well that figures. I'm no C++ guru, that's for sure.
I suppose I should work harder on upgrading systems to 3.x :-)
Then again it makes me wonder why the Mozilla team don't try harder to
make sure their code works with even more ancient compilers that are
still in production use in many places...... :-(
> > BTW, trying lang/gcc3 on the netbsd-1-6 machines is out of the question,
> > as per this comment I added some time ago in my pkgchk.conf file:
> > # XXX ARGH! binutils causes major havoc on alpha when gcc finds /usr/pk=
> > # XXX it also causes conflicts with gdb6 (which installs part of its ow=
> > #devel/binutils primary
> > #lang/gcc3-c primary
> > #lang/gcc3-c++ primary
> > #lang/gcc3-f77 primary
> > #lang/gcc3-objc primary
> Want to help fix it? :-)
I tried looking at why the _system_ GCC was even searching the path for
"ld" instead of just always using the _system_ "ld", but couldn't get
past even the first level of twisty little mazes all alike. Why does
GCC have to be so darn convluted and stupidly complex in so many places?
As for the binutils vs. gdb6 vs. gcc3 conflicts, well those should just
be a matter of fixing the package builds to always install unique names
(perhaps in unique sub-directories), no?
(getting them to all work together properly might be back to square-one
in the same boat as the system/gcc vs pkgsrc/binutils problem)
Greg A. Woods
H:+1 416 218-0098 W:+1 416 489-5852 x122 VE3TCP RoboHack <email@example.com>
Planix, Inc. <firstname.lastname@example.org> Secrets of the Weird <email@example.com>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
-----END PGP SIGNATURE-----