Date: Thu, 23 Jul 1998 18:30:02 -0700 (PDT) From: Adrian Penisoara <ady@warpnet.ro> To: freebsd-ports@FreeBSD.ORG Subject: Re: ports/7382: Pine4 does not co-exist with older installed version of pine. Message-ID: <199807240130.SAA27162@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/7382; it has been noted by GNATS.
From: Adrian Penisoara <ady@warpnet.ro>
To: Satoshi Asami <asami@FreeBSD.ORG>
Cc: ady@freebsd.ady.ro, freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: ports/7382: Pine4 does not co-exist with older installed version of pine.
Date: Fri, 24 Jul 1998 04:28:00 +0300 (EEST)
Hi,
On Thu, 23 Jul 1998, Satoshi Asami wrote:
> * If they'll use the new/future pine4 port then yes, they will be able to
> * compile , install & run Pine 3.96 (after doing this they will have either
> * to use "pine4" or reconstruct the symlink pine -> pine4 to run Pine 4.x)
>
> Sorry for being so dense, but let me clarify a bit. If the pine build
> pulls in a library using -lpico or something, it will NOT pick up a
> shared library with a smaller version.
Don't be sorry, I'm lucky you are dense, or else I could miss this
aspect...
>
> Thus, if there exists a /usr/local/lib/libpico.so.2.0, a pine build,
> expecting libpico.so.1.3 from the build directory, could get linked to
> libpico.so.2.0 if the Makefile is not very careful.
Here's the culprit code from pico/makefile.bsf for Pine 3.96:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
libpico.so.1.3: osdep.c osdep.h $(SOFILES)
ld -Bshareable -x -o libpico.so.1.3 $(SOFILES)
pico: main.c libpico.so.1.3
$(CC) $(CFLAGS) main.c -L. -lpico $(LIBS) -o pico
pilot: pilot.c libpico.so.1.3
$(CC) $(CFLAGS) pilot.c -L. -lpico $(LIBS) -o pilot
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
.. it must be modified to support compiling while Pine 4.x is installed;
so not only mail/pine4 but mail/pine3 too will have to be modified for
this to be supported...
Would somehing like the following line do the job for us (reliably) ?
$(CC) $(CFLAGS) main.c libpico.so.x.y $(LIBS) -o pico
And there is more: there are some files common to both ports (pgp* files
and the manpages) which will be deleted with the first uninstall of one
port leaving the other without them. I don't know how we're going to
handle correctly this (the same situation like netscape-3 vs.
netscape-4)...
>
> Satoshi
>
Starting to wonder wether it's worth the pain,
Ady (@freebsd.ady.ro)
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?199807240130.SAA27162>