Date: Sun, 12 Feb 2012 13:17:44 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Chris Rees <utisoft@gmail.com> Cc: freebsd-ports@freebsd.org, Andriy Gapon <avg@freebsd.org> Subject: Re: Please test your commits Message-ID: <20120212211744.GC86775@troutmask.apl.washington.edu> In-Reply-To: <CADLo83_Ni55YqyM6H3Tn7gWMx1pWe6TqtvtRB-WVuiB5dU6KnA@mail.gmail.com> References: <20120212193927.GA86426@troutmask.apl.washington.edu> <CADLo83_UZR0K15LQWoXb-AAhd1wj25fbeKSAPch5ji_Q=41f8A@mail.gmail.com> <20120212201624.GA86650@troutmask.apl.washington.edu> <4F3820AD.4090702@FreeBSD.org> <20120212204118.GA86775@troutmask.apl.washington.edu> <CADLo83_w1A7tv3jgK_LQZCgi7odbEniE4Qfn1HJwgjWBNVn4ig@mail.gmail.com> <20120212204526.GB86775@troutmask.apl.washington.edu> <CADLo83_Ni55YqyM6H3Tn7gWMx1pWe6TqtvtRB-WVuiB5dU6KnA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Feb 12, 2012 at 08:52:56PM +0000, Chris Rees wrote: > On 12 Feb 2012 20:45, "Steve Kargl" <sgk@troutmask.apl.washington.edu> > wrote: > > > > > > laptop:root[252] uname -a > > FreeBSD laptop 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r230975M: Sat Feb 4 > 09:03:27 PST 2012 root@laptop:/usr/obj/usr/src/sys/MOBILE i386 > > Well, that immediately shows that this is a 10.0 error, which means it's > almost certainly due to freebsd1* being matched in some configure script. > Empirical evidence suggests that ghostscript9 developers are using a newer version of the autotools. laptop:root[262] find . -name configure | xargs grep -i "freebsd\[1" | more ./lcms/configure: freebsd[123].*) objformat=aout ;; ./lcms/configure: freebsd[12].*) ./lcms/configure: freebsd[123].*) objformat=aout ;; ./lcms/configure: freebsd[123].*) objformat=aout ;; ./lcms/configure: freebsd[123].*) objformat=aout ;; ./freetype/builds/unix/configure: freebsd[123].*) objformat=aout ;; ./lcms2/configure: freebsd[123].*) objformat=aout ;; ./lcms2/configure: freebsd[12].*) ./lcms2/configure: freebsd[123].*) objformat=aout ;; laptop:root[263] find . -name configure | xargs grep -i "freebsd1" | more ./lcms/configure: freebsd1.*) ./lcms/configure:freebsd1.*) ./lcms/configure:freebsd1.*) ./lcms/configure: freebsd1.*) ./lcms/configure:freebsd1.*) ./lcms/configure: freebsd1.*) ./lcms/configure:freebsd1.*) ./freetype/builds/unix/configure: freebsd1.*) ./freetype/builds/unix/configure:freebsd1.*) ./lcms2/configure: freebsd1.*) ./lcms2/configure:freebsd1.*) The malloc issue will not appear on amd64 because the problematic code is #elif !defined(__amd64__) && !defined(__APPLE__) #define HAVE_MEMALIGN #include <malloc.h> #endif with the obvious fix #elif !defined(__amd64__) && !defined(__APPLE__) && !defined(__FreeBSD__) #define HAVE_MEMALIGN #include <malloc.h> #endif But, the 2nd issue with too many arguments in a function call is clearly evident on amd64 because I justed test that on FreeBSD 10. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120212211744.GC86775>