Front page | perl.perl5.porters |
Postings from April 2010
On Apr 27, 2010, at 7:11 AM, Andy Dougherty wrote: > On Thu, 22 Apr 2010, Andy Dougherty wrote: > >> On Thu, 22 Apr 2010, H.Merijn Brand wrote: >> >>> On Thu, 22 Apr 2010 08:38:35 -0400 (EDT), Andy Dougherty >>> <doughera@lafayette.edu> wrote: >>> >>>> On Wed, 21 Apr 2010, Todd Rinaldo wrote: >>>> >>>>> # New Ticket Created by Todd Rinaldo >>>>> # Please include the string: [perl #74564] >>>>> # in the subject line of all future correspondence about this issue. >>>>> # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=74564 > >>>>> >>>>> >>>>> When running configure on FreeBSD 7+, the following error message is printed when hints are run: >>>>> >>>>> ./hints/freebsd.sh: /usr/bin/objformat: not found >>>>> >>>>> The reason for this is outlined in this email from Feb 2007 >>>>> http://lists.freebsd.org/pipermail/freebsd-ports/2007-February/038523.html >>>>> >>>>> As hints run now, it should be executing the non-a.out code, so the below patch should be applied to fix this. >>>> >>>> Thanks. Applied as commit a8ca765fc246174faebe5c6c3eae7c25b571ece2 >>> >>> +1 for 5.12.1 >> >> I don't really care either way. It's a quite safe fix, but the warning it >> silences was a harmless warning too. (The hints already had the correct >> forward-thinking fallback.) > > On further thought, I'll vote +1 for 5.12.1 here -- it's probably easier > in the long run if the hints files don't drift apart, much like we try > not to let Configure drift. > While we're at it, I've discovered that ports is also applying this patch to perl for 5.10. Since this hints file is arguably the property of the ports folks, I'd argue for it being committed into blead. Same drift argument. I've amended the ports patch to deal with the recent blead changes to this file only. From what I can tell, the patch forces threads on and also makes some library inclusion changes. I assume 5.12 didn't have any significant library dependency issues that would make this patch invalid. The only thing I'm unsure about is whether we should be forcing threads on the way they're doing it. I don't have any strong feelings either way if this goes into 5.12.1 but it probably ought to go into blead. Todd.Thread Previous | Thread Next