r1104 breaks build @ "error: -fsanitize=address is incompatible with -fsanitize=thread"

Bug #1169311 reported by pgnd
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
libmemcached
Fix Committed
Medium
Brian Aker

Bug Description

on linux/64, with gcc version 4.8.0, r1100 builds OK.

r1101 (tip) breaks @ make ...

cd ~/TEST
rm -rf *
bzr branch lp:libmemcached -r 1100 libmemcached-BZR-r1100
bzr branch lp:libmemcached libmemcached-BZR-tip

echo $CFLAGS
 -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -march=amdfam10 -mtune=amdfam10
echo $CXXFLAGS
 -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -march=amdfam10 -mtune=amdfam10 -Wno-error

cd libmemcached-BZR-r1100
./bootstrap.sh autoreconf
./configure
make -j8
ldd ./libmemcached/.libs/libmemcached.so
        linux-vdso.so.1 (0x00007fffe7bff000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f436635d000)
        libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f4366140000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f4365e37000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f4365b39000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f436578c000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4365574000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f43667d8000)

cd ../libmemcached-BZR-tip
./bootstrap.sh autoreconf
./configure
make -j8
 ...
   CXX clients/utilities.lo
   CXXLD libhashkit/libhashkitinc.la
   CXXLD libmemcachedinternal/libmemcachedinternal.la
   CXXLD libtest/core-count
   CXXLD libtest/backtrace
 g++-4.8: error: -fsanitize=thread linking must be done with -pie or -shared
 make[1]: *** [libtest/core-count] Error 1
 make[1]: *** Waiting for unfinished jobs....
 g++-4.8: error: -fsanitize=thread linking must be done with -pie or -shared
 make[1]: *** [libtest/backtrace] Error 1
 copying selected object files to avoid basename conflicts...
 make[1]: Leaving directory `/root/TEST/libmemcached-BZR-tip'
 make: *** [all] Error 2

Revision history for this message
pgnd (pgnd) wrote :

updating to:

 ------------------------------------------------------------
 revno: 1104 [merge]
 committer: Continuous Integration <email address hidden>
 branch nick: workspace
 timestamp: Sun 2013-05-05 00:43:37 -0700
 message:
   Merge lp:~tangent-org/libmemcached/1.2-build/ Build: jenkins-Libmemcached-299
 ------------------------------------------------------------
 revno: 1103 [merge]
 committer: Continuous Integration <email address hidden>

build fails at:

./configure
make
 ...
 g++-4.8: error: -fsanitize=address is incompatible with -fsanitize=thread
 make[1]: *** [clients/memcapable] Error 1
 make[1]: Leaving directory `/usr/local/src/libmemcached-bzr'
 make: *** [all] Error 2

back to r1100 ...

pgnd (pgnd)
summary: - r1101 breaks build @ "error: -fsanitize=thread linking must be done with
- -pie or -shared"
+ r1104 breaks build @ "error: -fsanitize=address is incompatible with
+ -fsanitize=thread"
Revision history for this message
pgnd (pgnd) wrote :

still an issue with r1105

g++-4.8: error: -fsanitize=address is incompatible with -fsanitize=thread
make[1]: *** [clients/memcapable] Error 1
make[1]: Leaving directory `/usr/local/src/libmemcached-BZR'
make: *** [all] Error 2

back to r1100, again.

Revision history for this message
Brian Aker (brianaker) wrote : Re: [Bug 1169311] r1104 breaks build @ "error: -fsanitize=address is incompatible with -fsanitize=thread"

Thanks, I need to update ddm4.

On Jul 12, 2013, at 10:04 PM, pgnet <email address hidden> wrote:

> still an issue with r1105
>
> g++-4.8: error: -fsanitize=address is incompatible with -fsanitize=thread
> make[1]: *** [clients/memcapable] Error 1
> make[1]: Leaving directory `/usr/local/src/libmemcached-BZR'
> make: *** [all] Error 2
>
> back to r1100, again.
>
> --
> You received this bug notification because you are subscribed to
> libmemcached.
> https://bugs.launchpad.net/bugs/1169311
>
> Title:
> r1104 breaks build @ "error: -fsanitize=address is incompatible with
> -fsanitize=thread"
>
> Status in libmemcached - A C and C++ client library for memcached:
> New
>
> Bug description:
> on linux/64, with gcc version 4.8.0, r1100 builds OK.
>
> r1101 (tip) breaks @ make ...
>
> cd ~/TEST
> rm -rf *
> bzr branch lp:libmemcached -r 1100 libmemcached-BZR-r1100
> bzr branch lp:libmemcached libmemcached-BZR-tip
>
> echo $CFLAGS
> -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -march=amdfam10 -mtune=amdfam10
> echo $CXXFLAGS
> -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -march=amdfam10 -mtune=amdfam10 -Wno-error
>
> cd libmemcached-BZR-r1100
> ./bootstrap.sh autoreconf
> ./configure
> make -j8
> ldd ./libmemcached/.libs/libmemcached.so
> linux-vdso.so.1 (0x00007fffe7bff000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007f436635d000)
> libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f4366140000)
> libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f4365e37000)
> libm.so.6 => /lib64/libm.so.6 (0x00007f4365b39000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f436578c000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4365574000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f43667d8000)
>
> cd ../libmemcached-BZR-tip
> ./bootstrap.sh autoreconf
> ./configure
> make -j8
> ...
> CXX clients/utilities.lo
> CXXLD libhashkit/libhashkitinc.la
> CXXLD libmemcachedinternal/libmemcachedinternal.la
> CXXLD libtest/core-count
> CXXLD libtest/backtrace
> g++-4.8: error: -fsanitize=thread linking must be done with -pie or -shared
> make[1]: *** [libtest/core-count] Error 1
> make[1]: *** Waiting for unfinished jobs....
> g++-4.8: error: -fsanitize=thread linking must be done with -pie or -shared
> make[1]: *** [libtest/backtrace] Error 1
> copying selected object files to avoid basename conflicts...
> make[1]: Leaving directory `/root/TEST/libmemcached-BZR-tip'
> make: *** [all] Error 2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/libmemcached/+bug/1169311/+subscriptions

Brian Aker (brianaker)
Changed in libmemcached:
milestone: none → 1.0.18
importance: Undecided → Medium
assignee: nobody → Brian Aker (brianaker)
status: New → Fix Committed
Revision history for this message
pgnd (pgnd) wrote :

I just pulled

 bzr branch lp:libmemcached

which still reports as r1105

 bzr log | head -n 10
 revno: 1105 [merge]
 committer: Continuous Integration <email address hidden>
 branch nick: workspace
 timestamp: Fri 2013-06-14 10:10:51 -0700
 message:
   Merge lp:~brianaker/libmemcached/update-1.2 Build: jenkins-Libmemcached-312

and, building returns the same error as above.

*where* is the commited src?

Revision history for this message
Seyfer (seyferseed) wrote :

I have this problem with libmemcached 1.0.17 just now

  CXX libtest/libtest_libtest_la-gearmand.lo
  CXXLD libtest/abort
g++: error: -fsanitize=address is incompatible with -fsanitize=thread
make[1]: *** [libtest/abort] Ошибка 1
make[1]: *** Ожидание завершения заданий...
make[1]: Выход из каталога `/home/seyfer/libmemcached-1.0.17'
make: *** [all] Ошибка 2

Revision history for this message
Brian Aker (brianaker) wrote : Re: [Bug 1169311] Re: r1104 breaks build @ "error: -fsanitize=address is incompatible with -fsanitize=thread"

Look at lp:libmencached/1.0

> On Nov 6, 2013, at 12:25, Seyfer <email address hidden> wrote:
>
> I have this problem with libmemcached 1.0.17 just now
>
> CXX libtest/libtest_libtest_la-gearmand.lo
> CXXLD libtest/abort
> g++: error: -fsanitize=address is incompatible with -fsanitize=thread
> make[1]: *** [libtest/abort] Ошибка 1
> make[1]: *** Ожидание завершения заданий...
> make[1]: Выход из каталога `/home/seyfer/libmemcached-1.0.17'
> make: *** [all] Ошибка 2
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1169311
>
> Title:
> r1104 breaks build @ "error: -fsanitize=address is incompatible with
> -fsanitize=thread"
>
> Status in libmemcached - A C and C++ client library for memcached:
> Fix Committed
>
> Bug description:
> on linux/64, with gcc version 4.8.0, r1100 builds OK.
>
> r1101 (tip) breaks @ make ...
>
> cd ~/TEST
> rm -rf *
> bzr branch lp:libmemcached -r 1100 libmemcached-BZR-r1100
> bzr branch lp:libmemcached libmemcached-BZR-tip
>
> echo $CFLAGS
> -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -march=amdfam10 -mtune=amdfam10
> echo $CXXFLAGS
> -O2 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -march=amdfam10 -mtune=amdfam10 -Wno-error
>
> cd libmemcached-BZR-r1100
> ./bootstrap.sh autoreconf
> ./configure
> make -j8
> ldd ./libmemcached/.libs/libmemcached.so
> linux-vdso.so.1 (0x00007fffe7bff000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007f436635d000)
> libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f4366140000)
> libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f4365e37000)
> libm.so.6 => /lib64/libm.so.6 (0x00007f4365b39000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f436578c000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f4365574000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f43667d8000)
>
> cd ../libmemcached-BZR-tip
> ./bootstrap.sh autoreconf
> ./configure
> make -j8
> ...
> CXX clients/utilities.lo
> CXXLD libhashkit/libhashkitinc.la
> CXXLD libmemcachedinternal/libmemcachedinternal.la
> CXXLD libtest/core-count
> CXXLD libtest/backtrace
> g++-4.8: error: -fsanitize=thread linking must be done with -pie or -shared
> make[1]: *** [libtest/core-count] Error 1
> make[1]: *** Waiting for unfinished jobs....
> g++-4.8: error: -fsanitize=thread linking must be done with -pie or -shared
> make[1]: *** [libtest/backtrace] Error 1
> copying selected object files to avoid basename conflicts...
> make[1]: Leaving directory `/root/TEST/libmemcached-BZR-tip'
> make: *** [all] Error 2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/libmemcached/+bug/1169311/+subscriptions

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.