Bug 20199

Summary: ports/graphics/hdf patch failure
Product: Ports & Packages Reporter: Vivek Khera <khera>
Component: Individual Port(s)Assignee: Ade Lovett <ade>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Vivek Khera 2000-07-26 19:40:01 UTC
	
ports/graphics/hdf is required by the latest ImageMagick port, but it
will not build because the patch step fails:

[root@onceler]# make
===>  Extracting for hdf-4.1r3

Fix: 

Edit scripts/post-patch and replace "patch -p" with "patch $f"
everywhere.  However, this leads to several patch FAILURES, and most
of the successful patches result in large line offsets.  This can't be
the right way to do the file editing, can it?

Alternatively, just disable HDF for building ImageMagick by commenting
out the dependency in Makefile for ImageMagick.  The config step then
skips building HDF support into ImageMagick.
How-To-Repeat: 
	
cd /usr/ports/graphics/hdf
make
Comment 1 Jeroen Ruigrok van der Werven freebsd_committer freebsd_triage 2000-07-27 12:24:06 UTC
Responsible Changed
From-To: gnats-admin->freebsd-ports

Misfiled PR.
Comment 2 Ade Lovett freebsd_committer freebsd_triage 2000-09-18 22:46:46 UTC
State Changed
From-To: open->feedback
Comment 3 Ade Lovett freebsd_committer freebsd_triage 2000-09-18 22:49:40 UTC
Responsible Changed
From-To: freebsd-ports->ade

Hmm.. the text for the open->feedback just disappeared on me. 
Anyway, this port builds fine for me, bento reports it as 
successfully building on both 3.x and 4.x, and critical/high 
is not an appropriate level for something that doesn't have 
a concrete fix associated with it. 

This looks to be a localized problem.  Make sure that you don't 
have any other "patch" programs in your path ahead of the 
system one, and that your system is fully up-to-date, for both 
src/ and ports/
Comment 4 Ade Lovett freebsd_committer freebsd_triage 2000-10-02 23:22:57 UTC
State Changed
From-To: feedback->closed

Submitter hasn't bothered to get back to me on this one for 2 weeks, 
despite marking the problem as critical/high.  It's definitely 
a localized problem.  Bye-bye, PR.