On Mon, Jun 20, 2016 at 9:42 AM, Stuart Henderson <[email protected]> wrote:
> On 2016/06/20 16:39, Rafael Sadowski wrote: > > On Mon Jun 20, 2016 at 10:03:27AM +0100, Stuart Henderson wrote: > > > https://www.openbsd.org/faq/current.html#r20160527 > > > 2016/05/27 - fstab needs wxallowed flag on /usr/local > > > > > > > I run in the same error with wxallowed flag on /usr/local. > > > > Perhaps I shouldn't have included the title - you need to read the > actual entry, the sentence starting "Some ports also..." > The build environment I have has separate partitions for -- * /usr * /usr/ports * /usr/ports/distfiles * /usr/ports/packages * /usr/ports/pobj A fresh install had the /usr partition set as wxallowed, & this is the scenario which generated the original build error cited earlier. From a suggestion sent to me privately, I decided to experiment by blindly setting wxallowed on all the other partitions mentioned above. This allowed me to finish building JDK 1.7 successfully. I suspect that the only other partition I really needed to set as wxallowed was /usr/ports/pobj, but I have not confirmed this as I am building other sizeable ports. Not exactly a definitive answer, but this may save others time from needless head scratching. I appreciate the cluestick pointing to wxallowed. I had not thought of this given that I had already built other ports successfully. I suspect the root cause is tools built & executed within /usr/ports/pobj which are being used to complete the build of JDK 1.7. Given that they violating W^X, the build failed. At least, this is my current hypothesis...
