Re: Problems are a Curl upgrade on 12.0 current of Sun Oct 2
On 5-12-2016 21:54, Willem Jan Withagen wrote: > On 5-12-2016 20:21, Ed Schouten wrote: >> Basename@FBSD_1.5 is the new symbol. Did you by any chance downgrade your >> system? > > Hi Ed, > > Not that I know of. But then again things are sometimes not obvious. > I just typed: pkg upgrade cmake, because I wanted to see if the new > cmake had code for Boost 1.62 (But didn't) > > My system is 12.0 current, which I do not really want to upgrade atm. > since I've just completed the first consistent successful set of tests > for Ceph. And every I upgraded, things started to unglue, and I needed > to start fixing stuff over again. > > So my guess is that I have a system that is too old to run what I > fetched from pkg. This, because pkg-builder for 12-current actually > builds on the newest and shiniest code that includes the version. > > I could try locally rebuilding curl in the hope that it fixes itself > because it does not (yet) have the versioning?? Right, Manual, local, building fixes the versioning problem. --WjW ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problems are a Curl upgrade on 12.0 current of Sun Oct 2
On 5-12-2016 20:21, Ed Schouten wrote: > Basename@FBSD_1.5 is the new symbol. Did you by any chance downgrade your > system? Hi Ed, Not that I know of. But then again things are sometimes not obvious. I just typed: pkg upgrade cmake, because I wanted to see if the new cmake had code for Boost 1.62 (But didn't) My system is 12.0 current, which I do not really want to upgrade atm. since I've just completed the first consistent successful set of tests for Ceph. And every I upgraded, things started to unglue, and I needed to start fixing stuff over again. So my guess is that I have a system that is too old to run what I fetched from pkg. This, because pkg-builder for 12-current actually builds on the newest and shiniest code that includes the version. I could try locally rebuilding curl in the hope that it fixes itself because it does not (yet) have the versioning?? --WjW > > On 5 Dec 2016 6:59 p.m., "Dimitry Andric" wrote: > >> On 05 Dec 2016, at 15:44, Willem Jan Withagen wrote: >>> >>> Now some of my lining attempts give me: >>> >>> /usr/local/lib/libcurl.so: undefined reference to `basename@FBSD_1.5 >>> I guess that that libc has become versioned, of the version number got >>> bumpped? >>> >>> So would I need to rebuild world? >> >> Yes, this was changed by Ed in r308264: >> >> https://svnweb.freebsd.org/base?view=revision&revision=308264 >> >> Although I would think there might have been a backwards compat symbol... >> >> -Dimitry >> >> > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problems are a Curl upgrade on 12.0 current of Sun Oct 2
> On 5 Dec 2016, at 17:21, Ed Schouten wrote: > > Basename@FBSD_1.5 is the new symbol. Did you by any chance downgrade your > system? t happened to me as well. I didn’t downgrade the system but I’ve installed curl package, that was built on a more recent version. After upgrade world to recent -CURRENT it was fixed -- Renato Botelho ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problems are a Curl upgrade on 12.0 current of Sun Oct 2
Basename@FBSD_1.5 is the new symbol. Did you by any chance downgrade your system? On 5 Dec 2016 6:59 p.m., "Dimitry Andric" wrote: > On 05 Dec 2016, at 15:44, Willem Jan Withagen wrote: > > > > Now some of my lining attempts give me: > > > > /usr/local/lib/libcurl.so: undefined reference to `basename@FBSD_1.5 > > I guess that that libc has become versioned, of the version number got > > bumpped? > > > > So would I need to rebuild world? > > Yes, this was changed by Ed in r308264: > > https://svnweb.freebsd.org/base?view=revision&revision=308264 > > Although I would think there might have been a backwards compat symbol... > > -Dimitry > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problems are a Curl upgrade on 12.0 current of Sun Oct 2
On 05 Dec 2016, at 15:44, Willem Jan Withagen wrote: > > Now some of my lining attempts give me: > > /usr/local/lib/libcurl.so: undefined reference to `basename@FBSD_1.5 > I guess that that libc has become versioned, of the version number got > bumpped? > > So would I need to rebuild world? Yes, this was changed by Ed in r308264: https://svnweb.freebsd.org/base?view=revision&revision=308264 Although I would think there might have been a backwards compat symbol... -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Problems are a Curl upgrade on 12.0 current of Sun Oct 2
Now some of my lining attempts give me: /usr/local/lib/libcurl.so: undefined reference to `basename@FBSD_1.5 I guess that that libc has become versioned, of the version number got bumpped? So would I need to rebuild world? Any suggestions, --WjW ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
