ports/134568: openoffice.org-3-RC build fails - with fix

Michael L. Squires mikes at siralan.org
Fri May 15 23:40:02 UTC 2009


>Number:         134568
>Category:       ports
>Synopsis:       openoffice.org-3-RC build fails - with fix
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 15 23:40:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Michael L. Squires
>Release:        7.2-STABLE
>Organization:
Self
>Environment:
FreeBSD mikesxeon.familysquires.net 7.2-STABLE FreeBSD 7.2-STABLE #9: Wed May 13 10:57:41 EDT 2009     root at mikesxeon.familysquires.net:/usr/obj/usr/src/sys/MIKESXEON  i386

>Description:
Both the openoffice.org-3 and openoffice.org-3-RC ports have a problem with patch files containing MS-DOS EOR markers (extra ^M or CTL-M).  openoffice-3 has this only in the patch file for "curl"; openoffice-3-RC has this with both "curl" and "neon".

The openoffice.org-3 pr is "ports/134305".


>How-To-Repeat:
Rebuild without patching
>Fix:
The fix is to start the build, then edit the two patch files ("./curl/curl-7.12.2.patch" and "./neon/neon.patch") and eliminate the extra "^M" characters.  I used "vi" and ":1,$?^V^M??" ("?" followed by control-V and control-M and another two "?" characters).  There is plenty of time to do this after the build starts, at least on a dual 2Ghz Xeon.

>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list