| Message ID | 87zk2lzgv7.fsf@redhat.com |
|---|---|
| State | New |
| Headers | show |
On Tue, Nov 13, 2012 at 10:01 AM, Dodji Seketeli <dodji@redhat.com> wrote: > Hello, > > This patch builds libsanitizer only on x86_64 and i?86 linux targets > for now. I guess The build can be enabled on other targets when they > are ready. > > OK for trunk? > > ChangeLog: > > * configure.ac: Enable libsanitizer just on x86 linux for now. > * configure: Re-generate. OK. Thanks. Diego.
> This patch builds libsanitizer only on x86_64 and i?86 linux targets > for now. I guess The build can be enabled on other targets when they > are ready. Note that, even on these platforms, it cannot be installed: libtool: install: error: cannot install `libasan.la' to a directory not ending in /usr/gnat/lib make[4]: *** [install-toolexeclibLTLIBRARIES] Error 1 make[4]: Leaving directory
On Tue, Nov 13, 2012 at 04:14:10PM +0100, Eric Botcazou wrote: > > This patch builds libsanitizer only on x86_64 and i?86 linux targets > > for now. I guess The build can be enabled on other targets when they > > are ready. > > Note that, even on these platforms, it cannot be installed: > > libtool: install: error: cannot install `libasan.la' to a directory not ending > in /usr/gnat/lib > make[4]: *** [install-toolexeclibLTLIBRARIES] Error 1 > make[4]: Leaving directory > > -- > Eric Botcazou I also noticed while trying to regenerate the libsanitizer Makefile.in on darwin that libsanitizer/configure.ac has... AC_PREREQ([2.68]) instead of the expected... AC_PREREQ([2.64]) Not good. Jack
On 11/13/2012 04:53 PM, Jack Howarth wrote: > I also noticed while trying to regenerate the libsanitizer Makefile.in > on darwin that libsanitizer/configure.ac has... AC_PREREQ([2.68]) > instead of the expected... AC_PREREQ([2.64]) This is other/55304, isn't it? Paolo.
On Tue, 13 Nov 2012, Dodji Seketeli wrote: > * configure.ac: Enable libsanitizer just on x86 linux for now. > * configure: Re-generate. Note that the preferred approach is the approach used for libatomic and libitm, of the toplevel script using a script fragment from the subdirectory to determine what architectures are supported - ideally a script fragment designed to be shared by toplevel and by the subdirectory's own configure script, if the subdirectory has existing case statements over targets. (It would be good to convert more existing projects that share the common toplevel to that scheme as well.) That way, you don't have a toplevel change that needs merging to the src repository for every individual change to the systems supported in a particular subdirectory.
Dodji Seketeli <dodji@redhat.com> writes:
> I guess The build can be enabled on other targets when they are ready.
How to test that? There doesn't seem to be a testsuite included.
Andreas.
diff --git a/configure b/configure index c387e92..39df09f 100755 --- a/configure +++ b/configure @@ -3208,12 +3208,11 @@ case "${target}" in ;; esac -# Disable libsanitizer for some systems. +# Disable libsanitizer on all systems but x86 linux for now. case "${target}" in - cris-*-* | crisv32-*-* | mmix-*-*) - noconfigdirs="$noconfigdirs target-libsanitizer" + x86_64-*-linux-* | i?86-*-linux-*) ;; - powerpc-*-aix* | rs6000-*-aix*) + *) noconfigdirs="$noconfigdirs target-libsanitizer" ;; esac diff --git a/configure.ac b/configure.ac index 1d958b4..6c1b008 100644 --- a/configure.ac +++ b/configure.ac @@ -550,12 +550,11 @@ case "${target}" in ;; esac -# Disable libsanitizer for some systems. +# Disable libsanitizer on all systems but x86 linux for now. case "${target}" in - cris-*-* | crisv32-*-* | mmix-*-*) - noconfigdirs="$noconfigdirs target-libsanitizer" + x86_64-*-linux-* | i?86-*-linux-*) ;; - powerpc-*-aix* | rs6000-*-aix*) + *) noconfigdirs="$noconfigdirs target-libsanitizer" ;; esac