Re: libc.so.66.0 (system): bad major

2012-08-27 Thread Scott McEachern

On 08/27/12 16:03, Stuart Henderson wrote:

On 2012/08/27 10:31, Matthew Dempsky wrote:

On Sun, Aug 26, 2012 at 10:25 PM, Scott McEachern  wrote:

===>  Installing groff-1.21p8 from /usr/ports/packages/amd64/all/
Can't install groff-1.21p8 because of libraries
|library c.65.0 not found
| /usr/lib/libc.so.66.0 (system): bad major
*** Error code 1

I suspect you compiled the groff package against an older snapshot
which had libc.so.65.0.  The new snapshots have libc.so.66.0 now, and
if you did a clean reinstall of base then you no longer have
libc.so.65.0.

I thought the ports tools are supposed to gracefully handle this, but
maybe not.  Try deleting the groff package and rebuilding it from
source to see if that helps.


If I were guessing, I'd say there are probably either old packages lying
around in /usr/ports/packages, old build directories in WRKOBJDIR (I
forget where this points by default as I always reset it), or FETCH_PACKAGES
is set and PKG_PATH is pointed at a mirror with old packages built against
libc.so.65.0.



Yes, it was a clean install on a "temp" SSD drive I have.  This box is 
my fastest, so I use it as a build machine.


However, the mistake I made was mounting a local file server holding all 
amd64 packages, including old ones, on /usr/ports/packages/amd64/all.  I 
guess the fresh install tried using (older) existing packages and barfed 
on it, so no, it isn't handled gracefully. :)


This time, I only mounted /usr/ports/distfiles and starting building 
from scratch, and it seems to be doing just fine.  (It'll be just a 
"few" hours before it finishes everything...)



FYI, dpb displays the following below the normal output during 
processing.  It doesn't seem to change or affect anything; as I write 
this over 120 packages have been successfully built.  I've seen it on a 
few recent snapshots but since they weren't clean installs, I figured it 
was something I broke.


print() on closed filehandle $fh at 
/usr/ports/infrastructure/lib/DPB/PortBuilder.pm line 171
DPB::PortBuilder::report('DPB::PortBuilder=HASH(0x20b74ea78)', 
'DPB::PkgPath=HASH(0x20b1b0100)', 'DPB::Job::Port=HASH(0x20b12c760)', 
'DPB::Core::Local=HASH(0x206ae0388)') called at 
/usr/ports/infrastructure/lib/DPB/PortBuilder.pm line 209
DPB::PortBuilder::__ANON__('DPB::Core::Local=HASH(0x206ae0388)') called 
at /usr/ports/infrastructure/lib/DPB/Job.pm line 149
DPB::Job::Normal::finalize('DPB::Job::Port=HASH(0x20b12c760)', 
'DPB::Core::Local=HASH(0x206ae0388)') called at 
/usr/ports/infrastructure/lib/DPB/Job/Port.pm line 568
DPB::Job::Port::finalize('DPB::Job::Port=HASH(0x20b12c760)', 
'DPB::Core::Local=HASH(0x206ae0388)') called at 
/usr/ports/infrastructure/lib/DPB/Core.pm line 325


(There may be more, but my screen ends there.)

Thanks everyone,

--
Scott McEachern

https://www.blackstaff.ca



Re: libc.so.66.0 (system): bad major

2012-08-27 Thread Stuart Henderson
On 2012/08/27 10:31, Matthew Dempsky wrote:
> On Sun, Aug 26, 2012 at 10:25 PM, Scott McEachern  wrote:
> > ===>  Installing groff-1.21p8 from /usr/ports/packages/amd64/all/
> > Can't install groff-1.21p8 because of libraries
> > |library c.65.0 not found
> > | /usr/lib/libc.so.66.0 (system): bad major
> > *** Error code 1
> 
> I suspect you compiled the groff package against an older snapshot
> which had libc.so.65.0.  The new snapshots have libc.so.66.0 now, and
> if you did a clean reinstall of base then you no longer have
> libc.so.65.0.
> 
> I thought the ports tools are supposed to gracefully handle this, but
> maybe not.  Try deleting the groff package and rebuilding it from
> source to see if that helps.
> 

If I were guessing, I'd say there are probably either old packages lying
around in /usr/ports/packages, old build directories in WRKOBJDIR (I
forget where this points by default as I always reset it), or FETCH_PACKAGES
is set and PKG_PATH is pointed at a mirror with old packages built against
libc.so.65.0.



Re: libc.so.66.0 (system): bad major

2012-08-27 Thread Matthew Dempsky
On Sun, Aug 26, 2012 at 10:25 PM, Scott McEachern  wrote:
> ===>  Installing groff-1.21p8 from /usr/ports/packages/amd64/all/
> Can't install groff-1.21p8 because of libraries
> |library c.65.0 not found
> | /usr/lib/libc.so.66.0 (system): bad major
> *** Error code 1

I suspect you compiled the groff package against an older snapshot
which had libc.so.65.0.  The new snapshots have libc.so.66.0 now, and
if you did a clean reinstall of base then you no longer have
libc.so.65.0.

I thought the ports tools are supposed to gracefully handle this, but
maybe not.  Try deleting the groff package and rebuilding it from
source to see if that helps.



Re: libc.so.66.0 (system): bad major

2012-08-27 Thread Kenneth R Westerback
On Mon, Aug 27, 2012 at 01:25:01AM -0400, Scott McEachern wrote:
> Hi, I performed a clean install of the latest snapshot (Aug 26) with
> the matching ports file and tried building a handful of ports via
> DPB.
> 
> After a bunch of failures (eg. net/libproxy; x11/gnome/librsvg;
> lang/gcc/4.6,-c++; devel/orc; devel/libusb1) I tried building those
> and a few others by hand (eg. firefox; thunderbird) and got errors
> such as this:
> 
> ===>  Checking files for firefox-14.0.1p0
> `/usr/ports/distfiles/mozilla/firefox-14.0.1.source.tar.bz2' is up to date.
> >> (SHA256) mozilla/firefox-14.0.1.source.tar.bz2: OK
> ===> firefox-14.0.1p0 depends on: unzip-* - not found
> ===>  Verifying install for unzip-* in archivers/unzip
> Link to /usr/ports/packages/amd64/ftp/unzip-6.0p0.tgz
> Link to /usr/ports/packages/amd64/cdrom/unzip-6.0p0.tgz
> ===> unzip-6.0p0 depends on: groff->=1.21 - not found
> ===>  Verifying install for groff->=1.21 in textproc/groff
> Link to /usr/ports/packages/amd64/ftp/groff-1.21p8.tgz
> Link to /usr/ports/packages/amd64/cdrom/groff-1.21p8.tgz
> ===>  Verifying specs: c m stdc++
> ===>  found c.66.0 m.7.1 stdc++.55.0
> ===>  Installing groff-1.21p8 from /usr/ports/packages/amd64/all/
> Can't install groff-1.21p8 because of libraries
> |library c.65.0 not found
> | /usr/lib/libc.so.66.0 (system): bad major
> *** Error code 1
> 
> Stop in /usr/ports/textproc/groff (line 1737 of
> /usr/ports/infrastructure/mk/bsd.port.mk).
> *** Error code 1
> 
> That same error regarding bad major can be found for every package
> I've mentioned.
> 
> Am I missing something, or is something out of sync?

Major (as in large) changes are rippling through library handling in
the os, and I think you just encountered one of the ripples. A newer
snapshot will likely work for you.

 Ken

> 
> Thanks,
> 
> -- 
> Scott McEachern
> 
> https://www.blackstaff.ca
> 



libc.so.66.0 (system): bad major

2012-08-26 Thread Scott McEachern
Hi, I performed a clean install of the latest snapshot (Aug 26) with the 
matching ports file and tried building a handful of ports via DPB.


After a bunch of failures (eg. net/libproxy; x11/gnome/librsvg; 
lang/gcc/4.6,-c++; devel/orc; devel/libusb1) I tried building those and 
a few others by hand (eg. firefox; thunderbird) and got errors such as this:


===>  Checking files for firefox-14.0.1p0
`/usr/ports/distfiles/mozilla/firefox-14.0.1.source.tar.bz2' is up to date.
>> (SHA256) mozilla/firefox-14.0.1.source.tar.bz2: OK
===> firefox-14.0.1p0 depends on: unzip-* - not found
===>  Verifying install for unzip-* in archivers/unzip
Link to /usr/ports/packages/amd64/ftp/unzip-6.0p0.tgz
Link to /usr/ports/packages/amd64/cdrom/unzip-6.0p0.tgz
===> unzip-6.0p0 depends on: groff->=1.21 - not found
===>  Verifying install for groff->=1.21 in textproc/groff
Link to /usr/ports/packages/amd64/ftp/groff-1.21p8.tgz
Link to /usr/ports/packages/amd64/cdrom/groff-1.21p8.tgz
===>  Verifying specs: c m stdc++
===>  found c.66.0 m.7.1 stdc++.55.0
===>  Installing groff-1.21p8 from /usr/ports/packages/amd64/all/
Can't install groff-1.21p8 because of libraries
|library c.65.0 not found
| /usr/lib/libc.so.66.0 (system): bad major
*** Error code 1

Stop in /usr/ports/textproc/groff (line 1737 of 
/usr/ports/infrastructure/mk/bsd.port.mk).

*** Error code 1

That same error regarding bad major can be found for every package I've 
mentioned.


Am I missing something, or is something out of sync?

Thanks,

--
Scott McEachern

https://www.blackstaff.ca