|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
||||
library mismatch for snapshots epdfview
In the snapshots i386 epdfview package
http://ftp.openbsd.org/pub/OpenBSD/s...ew-0.1.7p7.tgz the +CONTENTS file says there's a library dependence of @wantlib stdc++.51.0 but the included binary bin/epdfview wants a different library: epdfview: can't load library 'libstdc++.so.50.0' Oh dear, what's to become of this? |
|
|||
libstdc++ was bumped relatively recently, you need to install a new snapshot.. I don't see this problem on my system, with a recent snapshot and epdfview-0.1.7p7.
The problem is on your end. |
|
||||
Update: I just checked the strings in the epdfview binary, and it does say libstdc++.so.51.0, consistent with the +CONTENTS. So I must have a problem with some other dependency I think not being bumped up. I will track it down. Thanks again.
|
|
|||
It is never a good idea to link shared libraries with different major numbers, it is meant to indicate ABI breakage.
Indeed, you should make sure you've cleanly updated.. even if that means deleting every package and reinstalling. |
|
||||
Quote:
Quote:
Just my luck I guess the packages (which I downloaded some time after installing the snapshot) were not yet up to date with it. I guess this is a risk of -current. Looks like this should be workable now, thank you again for your help. EDIT: Trying to recall the sequence of events, the lack of sync may have had more to do with mirror lag than -current. FWIW. Last edited by IdOp; 24th May 2011 at 03:54 AM. |
|
|||
Quote:
Irregardless of whether installing a snapshot is the end goal or whether the snapshot is merely a baseline for installing source & building the system from a fully sanctioned code base (see Section 5.1 for more information...), matching kernel to userland to 3rd party applications is very important. Failure to synchronize everything will result in peculiarities ranging from subtle to overt. |
|
|||
Someone who is paying attention to changes of course would notice events in the kernel/userland that would require bulk rebuilds of ports.. i.e: major library bumps, kernel ABI changes.
As for synchronizing snapshots and packages, that's not always possible, they are built at different times. An unofficial site for tracking this: http://www.rhaalovely.net/up2date.html |
|
|||
Correct, but anyone who installs a snapshot, waits a few weeks, & then updates packages is taking undue chances. Install a newer snapshot first.
|
|
||||
There was a recent thread on this in misc@. It was quite active, with 53 responses to the original post. You may find the entire thing helpful, so here is the link to the first post in the thread.
I will quote from Ted Unangst, who posted this in reply in the midst of discussion: Quote:
|
|
||||
Thanks to everyone for the further helpful comments, they're much appreciated, and the thread linked by jggimi looks very relevant, I'll go through it soon.
I should clarify a bit the sequence of events because something I wrote above was confused (sorry about that). My statement that I downloaded the packages after the system snapshot is incorrect, and doesn't fully fit with the observed problem. I must have had in mind installing the packages after the snapshot (as must be) but that is of course irrelevant, what matters is when the packages were compiled relative to the snapshot. So here is what happened. 1) I downloaded the packages from a mirror (mirror.ece.vt.edu) to a shell account, bundled them up and put them on a website. 2) Within 24 hours of 1) I went to download that bundle and decided to get a new system snapshot. Here, I checked ftp.openbsd.org to see what the latest snapshot was. I was going to download it from mirror.ece.vt.edu, but the one there was still older, so I got the latest from the Chicago mirror. So you can see that due to the order of events, mirror lag, and the very questionable decision to do #2, it ended up with the packages being older than the snapshot, and by bad luck the library bump must have occurred in that gap. The rest is history. My takeaway from this is that, to minimize the chances of lack of sync, one should download the packages and snapshot from the same site at the "same time". If I want the latest, find a mirror that has the latest snapshot and use its packages too. Hope that is about right. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
OpenBSD OpenBSD 4.7 beta snapshots | J65nko | News | 0 | 29th January 2010 08:02 PM |
Tracking OpenBSD snapshots with some simple sh scripts | J65nko | Guides | 3 | 2nd December 2009 04:55 AM |
Script to update NetBSD using snapshots | s0xxx | Guides | 5 | 23rd November 2009 04:30 PM |
SHA256 replaces MD5 in OpenBSD snapshots | J65nko | OpenBSD General | 3 | 6th May 2009 04:36 PM |
gem Collisions, duplex mismatch? | tad1214 | FreeBSD General | 1 | 8th July 2008 02:32 AM |