latest merge breaks compiling against mysql-5.1

Reported by Alexey Bychko on 2013-03-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Low
Laurynas Biveinis
2.0
Low
Laurynas Biveinis
2.1
Low
Laurynas Biveinis

Bug Description

to reproduce:
* bzr branch lp:percona-xtrabackup/2.0
* AUTO_DOWNLOAD=yes ./utils/build.sh 5.1

result: a lot of errors, build failed

last 2 commits:

revno: 502 [merge]
committer: Alexey Kopytov <email address hidden>
branch nick: 2.0
timestamp: Sat 2013-03-02 15:22:59 +0400
message:
  Merge trunk.
------------------------------------------------------------
revno: 501
committer: Alexey Kopytov <email address hidden>
branch nick: 2.0
timestamp: Mon 2013-02-04 11:32:47 +0400
message:
  Bug #1114955: xtrabackup_pid remains existed after execution

  Fix a regression introduced by the fix for bug #1055989: in case the
  xtrabackup process has finished copying the log file and terminated
  before wait_for_ibbackup_finish() is called, remove the stale
  xtrabackup_pid file.

Alexey Bychko (abychko) wrote :
Alexey Bychko (abychko) wrote :
Alexey Kopytov (akopytov) wrote :

I can build it. The errors in the attached log should not happen when CXXFLAGS contains -fpermissive. It does contain it for me.

Changed in percona-xtrabackup:
status: New → Incomplete
Alexey Kopytov (akopytov) wrote :

Oh, that's actually a regression introduced by https://code.launchpad.net/~laurynas-biveinis/percona-xtrabackup/BT-28340-cpp-2.0/+merge/149810

-fpermissive is added for "innodb51_builtin" and "innodb50" targets, but not for their synonyms, "5.0" and "5.1".

Alexey Kopytov (akopytov) wrote :

Workaround: use "build.sh innodb51_builtin" instead of "build.sh 5.1"

Alexey Kopytov (akopytov) wrote :

Never appeared in any released version, does not need to be reflected in release notes.

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

Other bug subscribers