Re: FreeBSD 9 recompile ports
George Kontostanos wrote: Greetings all and my apologies for cross posting! There seems to be a confusion regarding the ABI change in FreeBSD 9 and if this affects the usual upgrade path which includes a full port rebuild. The relevant post is here: http://forums.freebsd.org/showthread.php?t=28831 Frankly, I am also confused because I remember a relevant discussion a few months ago in the lists. Traditionally a major RELEASE upgrade requires a full ports rebuild, however this time there is no COMPAT_FREEBSD8 in GENERIC and most upgraded systems seem to be working fine. On the other hand this is stated in UPDATING: 20110828: Bump the shared library version numbers for libraries that do not use symbol versioning, have changed the ABI compared to stable/8 and which shared library version was not bumped. Done as part of 9.0-RELEASE cycle. Your input would be appreciated! Why can't it be that only shared libraries should be bumped, but no kernel incompatible changes were introduced? -- Sphinx of black quartz judge my vow. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9 recompile ports
On 01/13/2012 02:06, Volodymyr Kostyrko wrote: Why can't it be that only shared libraries should be bumped, but no kernel incompatible changes were introduced? Because one of the reasons we have major branches is so that we can change the various API/KPI/etc. in the newer branch. Doug -- You can observe a lot just by watching. -- Yogi Berra Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9 recompile ports
on 13/01/2012 12:19 Doug Barton said the following: On 01/13/2012 02:06, Volodymyr Kostyrko wrote: Why can't it be that only shared libraries should be bumped, but no kernel incompatible changes were introduced? Because one of the reasons we have major branches is so that we can change the various API/KPI/etc. in the newer branch. Are you saying that every major branch _has_ to introduce incompatibilities into a at least one system call? Otherwise, you are answering a question different from what Volodymyr asked :) -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9 recompile ports
On Fri, Jan 13, 2012 at 2:34 PM, Johan Hendriks joh.hendr...@gmail.com wrote: George Kontostanos schreef: On Fri, Jan 13, 2012 at 12:55 PM, Andriy Gapona...@freebsd.org wrote: on 13/01/2012 11:59 Doug Barton said the following: On 01/13/2012 01:52, George Kontostanos wrote: On Thu, Jan 12, 2012 at 8:42 PM, George Kontostanos gkontos.m...@gmail.com wrote: Greetings all and my apologies for cross posting! There seems to be a confusion regarding the ABI change in FreeBSD 9 and if this affects the usual upgrade path which includes a full port rebuild. The relevant post is here: http://forums.freebsd.org/showthread.php?t=28831 Frankly, I am also confused because I remember a relevant discussion a few months ago in the lists. Traditionally a major RELEASE upgrade requires a full ports rebuild, however this time there is no COMPAT_FREEBSD8 in GENERIC and most upgraded systems seem to be working fine. On the other hand this is stated in UPDATING: 20110828: Bump the shared library version numbers for libraries that do not use symbol versioning, have changed the ABI compared to stable/8 and which shared library version was not bumped. Done as part of 9.0-RELEASE cycle. Your input would be appreciated! Hmm, anyone :) ? If your question is, Do I need to rebuild my ports when doing a major OS version upgrade? the answer is always Yes. The method described at the end of the portmaster man page is preferred, whether you actually use portmaster to do the upgrade or not. (I.e., good backups, delete everything, start over from scratch.) I think that another part of the question was why there is no COMPAT_FREEBSD8 kernel option in 9? and I think that Volodymyr has tried to answer this part with another question. -- Andriy Gapon Hi guys, I am aware of the proper procedure which requires a full rebuild after a major upgrade. Doug, the question had to to with COMPAT_FREEBSD8 missing from GENERIC. It seems this and the fact that some upgrades from 8.2-STABLE worked fine without a recompile, has created the confusion. Did he do make delete-old-libs, if you leave them, then no recompile is needed, and the ports still have there old libs laying around.! If you do the make delete-old-libs command, your ports do not work anymore. regards Johan Hendriks Very good point! Still the question remains regarding COMPAT_FREEBSD8 and how does this affects ports/misc/compat8x/ Cheers -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9 recompile ports
on 13/01/2012 14:57 George Kontostanos said the following: Still the question remains regarding COMPAT_FREEBSD8 and how does this affects ports/misc/compat8x/ Looks like all the previous hints have not been clear enough. There is no direct relation between COMPAT_FREEBSD8 and misc/compat8x. COMPAT_FREEBSDX options are only needed when going from release X to release X+1 there was a change to an existing system call at the kernel-userland boundary. A side note: kernel options affect only what's in the kernel, quite obviously. misc/compatXx contains versions of shared libraries from release X that are no longer present in X+1. -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: FreeBSD 9 recompile ports
On Fri, Jan 13, 2012 at 04:11:22PM +0200, Andriy Gapon wrote: on 13/01/2012 14:57 George Kontostanos said the following: Still the question remains regarding COMPAT_FREEBSD8 and how does this affects ports/misc/compat8x/ Looks like all the previous hints have not been clear enough. There is no direct relation between COMPAT_FREEBSD8 and misc/compat8x. COMPAT_FREEBSDX options are only needed when going from release X to release X+1 there was a change to an existing system call at the kernel-userland boundary. A side note: kernel options affect only what's in the kernel, quite obviously. misc/compatXx contains versions of shared libraries from release X that are no longer present in X+1. Additional twist is that not every change at the kernel/usermode boundary is covered with backward-compatibility shims. Recent example is the CAM ABI change, which makes libcam.so.5 from the compat8x useless. pgpuaqFjafo46.pgp Description: PGP signature
Re: FreeBSD 9 recompile ports
On Fri, Jan 13, 2012 at 4:18 PM, Kostik Belousov kostik...@gmail.com wrote: On Fri, Jan 13, 2012 at 04:11:22PM +0200, Andriy Gapon wrote: on 13/01/2012 14:57 George Kontostanos said the following: Still the question remains regarding COMPAT_FREEBSD8 and how does this affects ports/misc/compat8x/ Looks like all the previous hints have not been clear enough. There is no direct relation between COMPAT_FREEBSD8 and misc/compat8x. COMPAT_FREEBSDX options are only needed when going from release X to release X+1 there was a change to an existing system call at the kernel-userland boundary. A side note: kernel options affect only what's in the kernel, quite obviously. misc/compatXx contains versions of shared libraries from release X that are no longer present in X+1. Additional twist is that not every change at the kernel/usermode boundary is covered with backward-compatibility shims. Recent example is the CAM ABI change, which makes libcam.so.5 from the compat8x useless. Thanks to all for your input. It looks quite obvious to me know and I think this clears any further confusion. Best Regards, George ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
FreeBSD 9 recompile ports
Greetings all and my apologies for cross posting! There seems to be a confusion regarding the ABI change in FreeBSD 9 and if this affects the usual upgrade path which includes a full port rebuild. The relevant post is here: http://forums.freebsd.org/showthread.php?t=28831 Frankly, I am also confused because I remember a relevant discussion a few months ago in the lists. Traditionally a major RELEASE upgrade requires a full ports rebuild, however this time there is no COMPAT_FREEBSD8 in GENERIC and most upgraded systems seem to be working fine. On the other hand this is stated in UPDATING: 20110828: Bump the shared library version numbers for libraries that do not use symbol versioning, have changed the ABI compared to stable/8 and which shared library version was not bumped. Done as part of 9.0-RELEASE cycle. Your input would be appreciated! Regards, -- George Kontostanos Aicom telecoms ltd ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
