Bug 65468 - zsh 4.2.0 port incorrectly registers TCP functions if NOSHARED=yes
Summary: zsh 4.2.0 port incorrectly registers TCP functions if NOSHARED=yes
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Sergei Kolobov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-12 22:50 UTC by Dimitry Andric
Modified: 2004-06-30 11:18 UTC (History)
0 users

See Also:

Attachments
file.diff (1.88 KB, patch)
2004-04-12 22:50 UTC, Dimitry Andric 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitry Andric 2004-04-12 22:50:14 UTC 
When you install the zsh 4.2.0 port using NOSHARED=yes, to get a
statically linked version, the tcp module is not compiled, just as
some other dynamic-only modules.  Therefore, the TCP functions in
Functions/TCP are not installed by the main Makefile.  However, they
are still listed in the pkg-plist file, so packaging the port will
fail, and uninstalling the port will complain about non-existing files
in ${PREFIX}/share/zsh/4.0.2/functions/TCP.

Fix: Simply put %%NO_STATIC%% in front of all functions/TCP related stuff.
Here is a patch.
How-To-Repeat: cd ${PORTSDIR}/shells/zsh
make NOSHARED=yes package
make NOSHARED=yes deinstall
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2004-04-13 04:10:29 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->sergei

Over to maintainer.
Comment 2 Volker Stolz freebsd_committer freebsd_triage 2004-06-30 11:18:02 UTC 
State Changed
From-To: open->closed

Committe, thanks!