Date: Sat, 10 Aug 2002 18:30:04 -0700 (PDT) From: Sean Chittenden <sean@chittenden.org> To: freebsd-ports@FreeBSD.org Subject: Re: ports/41436 net/spread did not build the shared libs Message-ID: <200208110130.g7B1U4uc055851@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/41436; it has been noted by GNATS. From: Sean Chittenden <sean@chittenden.org> To: Joshua Goodall <joshua@roughtrade.net> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/41436 net/spread did not build the shared libs Date: Sat, 10 Aug 2002 18:24:22 -0700 > > net/spread can be built to include shared libs but was not > > currently doing so. The included patch fixes this. > > Any particular reason why it's required? Yeah, I'm working on ruby-spread and it's preferred/ideal to use a shared lib instead. > All of the Spread applications I've seen use the static libs, which > the authors themselves recommend. Yup. For the reasons that Jonathan Stanton points out on the spread-users list, I use static libs sometimes too... it's just a PITA to upgrade spread and then have to recompile all programs that have spread libs statically compiled into them. > I'd rather they were installed as libspread.so to avoid potential > runtime conflict with the textproc/sp package but the upstream > doesn't care very much about this :) Hrm. That's a different issue that maybe I'll bring up in a few months time. :~) > OTOH maybe you have a demonstrable need for the .so's! Please > follow up. ping. ::grin:: -sc -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200208110130.g7B1U4uc055851>