|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
||||
Quote:
To repair this, you can upgrade your -current to the most recent snapshot, or reinstall completely. If you decide to upgrade, you will want to remove all installed packages (# pkg_delete /var/db/pkg/*), eliminate all built packages (# rm -rf /usr/ports/packages), and clean out any remaining WORKOBJDIR structures ( # rm -rf /usr/ports/pobj). |
|
|||
All thanks to you Teacher Jgimmi !
I did the aforementioned steps .. do you suggest I download the installation snapshots or the current iso ? the kernel version : Code:
$ sudo sysctl kern.version deraadt@i386.openbsd.org:/usr/src/sy...ile/GENERIC.MP Last edited by daemonfowl; 2nd February 2012 at 06:32 PM. |
|
||||
Your OpenBSD-current system is, as I had suspected, from a time when libc 61.0 was in use. It is now out-of-date and unusable for ports building with an up-to-date tree.
Your solution is one of the two choices I recommended above. Upgrade and remove installed and built packages, or re-install. You must always keep your ports tree in sync with your system. The ports tree tarball you are using is posted daily for convenience; but it is still your responsibility to keep things in sync, and, when errors occur like this one, it is your responsibility to discover the root cause for yourself, and correct them yourself. Even if you were to build -current from source and match your ports tree to the same time time window, you are not guaranteed to be free from all possible sync issues, due to the nature of development activity with the base code and the ports tree. In one of my quotes from FAQ 15, above, you should note that ports are not even guaranteed to build. And that may happen to you even when libraries are in sync. There are many interdependent components within the ports tree and /usr/lib. ---- Normally, only an upgrade would be needed. But I am recommending a clean out of the packages you had built and installed because you did so when the base was significantly behind the ports tree. Those successful packages are suspect, and it is safer to replace them. |
|
|||
Quote:
Code:
ftp> cd pub/OpenBSD/snapshots/i386 250 CWD command successful. ftp> dir 150 Opening ASCII mode data connection for '/bin/ls'. total 936428 -rw-r--r-- 1 0 0 98707 Feb 2 08:56 INSTALL.i386 -rw-r--r-- 1 0 0 22581 Feb 2 08:56 INSTALL.linux -rw-r--r-- 1 0 0 2075 Feb 2 08:57 SHA256 -rw-r--r-- 1 0 0 55332319 Feb 2 08:56 base51.tgz -rwxr-xr-x 1 0 0 8989107 Feb 2 08:56 bsd -rwxr-xr-x 1 0 0 9008741 Feb 2 08:56 bsd.mp -rwxr-xr-x 1 0 0 6427696 Feb 2 08:56 bsd.rd -rw-r--r-- 1 0 0 6547456 Feb 2 08:56 cd51.iso -r-xr-xr-x 1 0 0 45592 Feb 2 08:56 cdboot -r-xr-xr-x 1 0 0 2048 Feb 2 08:56 cdbr -rw-r--r-- 1 0 0 3012608 Feb 2 08:56 cdemu51.iso -rw-r--r-- 1 0 0 58622559 Feb 2 08:56 comp51.tgz -rw-r--r-- 1 0 0 525012 Feb 2 08:56 etc51.tgz -rw-r--r-- 1 0 0 1474560 Feb 2 08:56 floppy51.fs -rw-r--r-- 1 0 0 1474560 Feb 2 08:56 floppyB51.fs -rw-r--r-- 1 0 0 1474560 Feb 2 08:56 floppyC51.fs -rw-r--r-- 1 0 0 2629817 Feb 2 08:56 game51.tgz -rw-r--r-- 1 0 0 1607 Feb 2 08:57 index.txt -rw-r--r-- 1 0 0 232476672 Feb 2 08:56 install51.iso -rw-r--r-- 1 0 0 9721591 Feb 2 08:56 man51.tgz -r-xr-xr-x 1 0 0 53732 Feb 2 08:56 pxeboot -rw-r--r-- 1 0 0 11622731 Jan 26 16:01 xbase51.tgz -rw-r--r-- 1 0 0 63814 Jan 26 16:01 xetc51.tgz -rw-r--r-- 1 0 0 39802408 Jan 26 16:01 xfont51.tgz -rw-r--r-- 1 0 0 26051704 Jan 26 16:01 xserv51.tgz -rw-r--r-- 1 0 0 3444369 Jan 26 16:01 xshare51.tgz 226 Transfer complete. ftp> |
|
|||
I've already done the following :
# pkg_delete /var/db/pkg/* # rm -rf /usr/ports/packages # rm -rf /usr/ports/pobj and removed all unnecesary shortcuts ,groups .. users etc .. so I proceed to download the snapshots bsd.rc and follow the faq or maybe you offer a shorter howto like the prevous ones .. Thanks Ocicat ! In fact this is the first current-going experience which I hope will succeed then I will have to assume future builds and updates myself .. |
|
||||
To upgrade:
Edited to add a most important step Step 0: Review the following -current FAQ, make note of architectural changes between your existing -current and today. If anything is needed that is not managed by sysmerge(8) -- you will need to make those changes by hand. |
|
|||
Quote:
If you want to effectively use OpenBSD, don't cheat yourself. The FAQ offers a wealth of information -- much which would have answered many of your previous questions. Consider understanding the FAQ to be a fundamental requirement. Yes, it takes time to digest the information contained. But learning to problem-solve yourself is a marketable skill in comparison to asking others to solve your problems for you. |
|
|||
Thanks Jgimmi !!
Thanks Ocicat , I approve of what you said and agree .. simply we slightly differ in one point : I've been considering Jgimmy's helpful guidance a learn-by-example strategy which for the likes of me -with no unix background- proves to be efficient .. in some months time I can imagine the prospect of being-toward-OpenBSD a success story and then hopefully I will be starting to contribute feedbacks and such .. with time .. after grokking this Pure OS .. contribute as generously as does the team .. I am trying to prove to myself as to others that newbs from GUI-oriented windows.world or mac.world do not have to waste time passing through a friendly-linux experience as a bridging necessity to BSD.world ... |
|
|||
it succeeded .. much thanks to Daemonforums .. and special thanks to Jggimi .. in this post I've learnt many things for the first time ..
Code:
$ uname -a OpenBSD volla.my.domain 5.1 GENERIC.MP#178 i386 $ sudo sysctl kern.version kern.version=OpenBSD 5.1-beta (GENERIC.MP) #178: Thu Feb 2 02:44:59 MST 2012 deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP and I am building geany and codeblocks .. to start learning c .. the ancestral and unique prog lge .. |
|
||||
Congratulations!
Quote:
When your ports were failing to build and producing strange results, I knew to look at your libraries. That's from experience, and helping a lot of people who never read FAQ 15.4.1 over the years. I noted for you the date ranges when libc's 61.0 had been active in -current. Q: What facility does the OpenBSD project have where I could go to look up those dates for you? For EXTRA Extra Credit: Q: There are two tools available to obtain the information. Can you name them both? Here is a hint: one is graphical, the other is not. For a Gold Star: Q: Using one of the two tools, find the same information and copy/paste it here. For a Hall of Fame award: Q: Using the other tool, find the information and copy/paste it here. Class dismissed! |
|
||||
We have a second hall of fame winner; ocicat.
In addition, our noble admin pointed out a very interesting update for libc 62.0, applicable to those of us with amd64 and i386 architectures -- where some assembly languge (machine code) is being replaced by C code, because the latter is faster. I promised him a cookie: |
|
|||
Thanks Men , you *ALL* deserve all world's goodness,kindness,generosity ..
Maybe the following sentence is a refreshing Mnemosynic token not only to Mr Rocket357 , but also to Sir Ocicat : Code:
And just for the record, following CURRENT is easier than STABLE (IMHO) because of binary snapshots. ;-) .. this simple sentence motivated a complete newbie to try current .. and I still remember how I came to BSDHeim .. please allow me to share this .. in brief : I was using windows .. one day , I read an article about Sams II project and NetBSD as its embedded system .. so I googled the OS , downloaded an iso and installed it on my dell laptop .. it succeeded but failed for some reason I was unable to fetch packages (the *no route to host* famous message) .. then I was lucky enough to go back to wikipedia bottom page and noticed NetBSD's twinbrother .. OpenBSD .. did the same .. IT SUCCEEDED PAINLESSLY !! when I ignited X , that was a point of epiphany for me ! there is a looooot to learn though (unicode issue+wi0 issue+pf+apache ....+c programming .. ) where is there a will there is a way .. nothing escapes change except change and with time a newbie is gonna slough off his newbie skin and rejoin an Upper Land .. Viva Daemonforums ! |
|
|||
Teacher , I am still trying to solve the quiz ..
too dumb to hasten for solutions .. sorry .. |
|
||||
Bump.
I have decided to close the loop on my little "class" for OpenBSD admins, as nearly four months has elapsed since the last attempted answers. Quote:
Quote:
Quote:
Patch 1.137 to src/lib/libc/shlib_version initiated the bump to 61.0, October 16: Code:
--- src/lib/libc/shlib_version 2011/07/18 18:29:49 1.136 +++ src/lib/libc/shlib_version 2011/10/16 14:23:10 1.137 @@ -1,4 +1,4 @@ -major=60 -minor=1 +major=61 +minor=0 # note: If changes were made to include/thread_private.h or if system # calls were added/changed then libpthread must also be updated. Code:
--- src/lib/libc/shlib_version 2011/10/16 14:23:10 1.137 +++ src/lib/libc/shlib_version 2012/01/17 02:34:18 1.138 @@ -1,4 +1,4 @@ -major=61 +major=62 minor=0 # note: If changes were made to include/thread_private.h or if system # calls were added/changed then libpthread must also be updated. Quote:
Code:
Revision 1.138: download - view: text, markup, annotated - select for diffs Tue Jan 17 02:34:18 2012 UTC (3 months, 4 weeks ago) by guenther Branches: MAIN CVS tags: OPENBSD_5_1_BASE, OPENBSD_5_1 Diff to: previous 1.137: preferred, coloured Changes since revision 1.137: +1 -1 lines Reimplement mutexes, condvars, and rwlocks to eliminate bugs, particularly the "consume the signal you just sent" hang, and putting the wait queues in userspace. Do cancellation handling in pthread_cond_*wait(), pthread_join(), and sem_wait(). Add __ prefix to thr{sleep,wakeup,exit,sigdivert}() syscalls; add 'abort" argument to thrsleep to close cancellation race; make thr{sleep,wakeup} return errno values via *retval to avoid touching userspace errno. Revision 1.137: download - view: text, markup, annotated - select for diffs Sun Oct 16 13:23:10 2011 UTC (7 months ago) by stsp Branches: MAIN Diff to: previous 1.136: preferred, coloured Changes since revision 1.136: +2 -2 lines Bump libc major; wscanf and wcsftime were added |
|
|||
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Enlightenment e17 on OpenBSD (Question about current ports) | uptonm | OpenBSD Packages and Ports | 2 | 17th June 2009 09:12 PM |
How to get 'make' to accept all defaults for dependent packages | Xeon | FreeBSD Ports and Packages | 1 | 12th February 2009 01:54 AM |
Compile ports in parallel? | MetalHead | FreeBSD Ports and Packages | 9 | 9th October 2008 11:37 PM |
Patch and compile bind94 on FreeBSD ports collection | dylan912 | FreeBSD Ports and Packages | 2 | 4th July 2008 12:23 PM |
remove kde and kde dependent apps | ccc | FreeBSD Installation and Upgrading | 2 | 12th May 2008 02:11 PM |