[Bug 206910] x11-toolkits/scintilla & editors/scite: Update to 3.6.3

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Feb 5 00:46:20 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206910

--- Comment #5 from lightside <lightside at gmx.com> ---
Hello, Naram Qashat.

(In reply to comment #4)
> I've already submitted this update as bug #206751 albeit without the edit for
> the PIC flags in the scintilla port.

Sorry, I didn't see this on PortsMon on time of checking the port update (may
be because of outdated information):
http://portsmon.freebsd.org/portoverview.py?category=x11-toolkits&portname=scintilla

(In reply to comment #4)
> I'll ask for this bug to be closed because I already submitted it, but is the
> PIC flags patch absolutely necessary? There were no issues with building it
> for amd64 or i386.

Sure, I can close it or it could be marked as duplicate of bug #206751.

I also didn't have issues on amd64 for build and run without changes for PIC
flags, but after reading the build log I found "-fPIC" added, along with "-DPIC
-fpic", which was strange from the logic of the port's Makefile. Then I found
following commit, which was cause of this:
http://sourceforge.net/p/scintilla/code/ci/255c6d20fa88b2aa1ebbc67c0a139f6f1595d126/

After reading parts of GCC documentation, the svn logs for
x11-toolkits/scintilla port, related to sparc64 architecture,  I decided to
propose current solution. Unfortunately, I can't test this on other
architectures to be sure.

Anyway, there is a possibility to use the proposed sed patch for PICFLAGS
define, if you find it useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list