New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #32723 (closed defect: fixed)

Opened 17 months ago

Last modified 3 days ago

mysql5-devel: build failure with clang

Reported by: wanliqunn@… Owned by: ryandesign@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: clang Cc: jwa@…, hkroger@…, pixilla@…, elisko@…
Port: mysql5-devel

Description (last modified by ryandesign@…) (diff)

I'm trying to "port sudo install mysql5-devel", but failed with the errors bellow:

:info:build < #include <mysql/service_thd_alloc.h>
:info:build < #include <stdlib.h>
:info:build make[2]: *** [do_abi_check] Error 1
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_mysql5-devel/mysql5-devel/work/mysql-5.5.2-m2'
:info:build make[1]: *** [abi_check] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_mysql5-devel/mysql5-devel/work/mysql-5.5.2-m2'
:info:build make: *** [all-recursive] Error 1
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_mysql5-devel/mysql5-devel/work/mysql-5.5.2-m2'
:info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_mysql5-devel/mysql5-devel/work/mysql-5.5.2-m2" && /usr/bin/make -j4 -w all " returned error 2
:error:build Target org.macports.build returned: shell command failed (see log for details)
:debug:build Backtrace: shell command failed (see log for details)
    while executing
"command_exec build"
    (procedure "portbuild::build_main" line 8)
    invoked from within
"$procedure $targetname"

Attachments

main.log (11.5 KB) - added by wanliqunn@… 17 months ago.
ports error log

Change History

Changed 17 months ago by wanliqunn@…

ports error log

comment:1 Changed 17 months ago by wanliqunn@…

  • Cc wanliqunn@… added

Cc Me!

comment:3 Changed 17 months ago by ryandesign@…

  • Cc wanliqunn@… removed
  • Keywords mysql5-devel do_abi_check error removed
  • Description modified (diff)
  • Port set to mysql5-devel

comment:4 follow-up: ↓ 5 Changed 17 months ago by ryandesign@…

  • Owner changed from macports-tickets@… to ryandesign@…
  • Keywords clang added
  • Summary changed from mysql5-devel build failure like "[do_abi_check] Error 1" to mysql5-devel: build failure with clang

Probably a clang problem. Try using a different compiler, or try the much newer mysql55 port Bradley just committed to his private tree; see #25751.

comment:5 in reply to: ↑ 4 Changed 17 months ago by wanliqunn@…

Replying to ryandesign@…:

Probably a clang problem. Try using a different compiler, or try the much newer mysql55 port Bradley just committed to his private tree; see #25751.


Yeah, I tried to use some other compilers like "sudo ports install mysql5-devel configure.compiler=llvm-gcc-4.2" and "sudo ports install mysql5-devel configure.compiler=apple-gcc42", still failed. I'll try Bradley's private tree.

comment:6 follow-up: ↓ 7 Changed 17 months ago by ryandesign@…

You're sure? It built fine for me on Snow Leopard with Xcode 3 and the gcc-4.2 compiler when I committed it. Did you remember to clean before each new attempt? (The log you attached here is not clean, for example.)

comment:7 in reply to: ↑ 6 ; follow-up: ↓ 9 Changed 17 months ago by wanliqunn@…

Replying to ryandesign@…:

You're sure? It built fine for me on Snow Leopard with Xcode 3 and the gcc-4.2 compiler when I committed it. Did you remember to clean before each new attempt? (The log you attached here is not clean, for example.)

Yes, I "sudo port clean mysql5-devel" then "sudo port selfupdate" and then "sudo port upgrade outdated", still failed with the same error. Here is my device enriment: Mac os 10.6.7 XCode: 4.2. Forgot to mention, I have mysql installed: Server version: 5.1.59 MySQL Community Server (GPL). I need to install mysql5-devel for some project development.
Sorry to ask, I'm a newbie with mac ports, and I'm trying to use Bradley's private tree, but seems not so easy to find how to adjust my macports with this private tree, any links are really appreciated.

comment:8 Changed 17 months ago by ryandesign@…

For example:

svn co https://svn.macosforge.org/repository/macports/users/pixilla/dports/databases/mysql55
cd mysql55
sudo port install

comment:9 in reply to: ↑ 7 ; follow-up: ↓ 10 Changed 17 months ago by ryandesign@…

Replying to wanliqunn@…:

Replying to ryandesign@…:

You're sure? It built fine for me on Snow Leopard with Xcode 3 and the gcc-4.2 compiler when I committed it. Did you remember to clean before each new attempt? (The log you attached here is not clean, for example.)

Yes, I "sudo port clean mysql5-devel" then "sudo port selfupdate" and then "sudo port upgrade outdated", still failed with the same error. Here is my device enriment: Mac os 10.6.7 XCode: 4.2. Forgot to mention, I have mysql installed: Server version: 5.1.59 MySQL Community Server (GPL).

If you mean the mysql5 port, then you're out of date; the current version is 5.1.60.

If you mean a standalone MySQL package installed elsewhere, then I can't help you with that, and might even suggest that you uninstall it, since having software installed outside of MacPorts can sometimes interfere with MacPorts. I don't think the standard MySQL distribution installs into any problematic locations, however, so you're probably fine.

I need to install mysql5-devel for some project development.

What do you mean, exactly? I am worried you may be under the mistaken impression that MacPorts adheres to the naming convention of Linux package managers where a package "foo" contains binaries and libraries and a package "foo-devel" contains development headers. That is not how MacPorts works. In MacPorts, all packages always contain development headers already. Instead, we use "-devel" ports to indicate development/unstable versions. So, if what you're after is the development headers for MySQL 5.1.x, just install the normal mysql5 port, not the mysql5-devel port.

comment:10 in reply to: ↑ 9 Changed 17 months ago by wanliqunn@…

Replying to ryandesign@…:

Replying to wanliqunn@…:

Replying to ryandesign@…:

You're sure? It built fine for me on Snow Leopard with Xcode 3 and the gcc-4.2 compiler when I committed it. Did you remember to clean before each new attempt? (The log you attached here is not clean, for example.)

Yes, I "sudo port clean mysql5-devel" then "sudo port selfupdate" and then "sudo port upgrade outdated", still failed with the same error. Here is my device enriment: Mac os 10.6.7 XCode: 4.2. Forgot to mention, I have mysql installed: Server version: 5.1.59 MySQL Community Server (GPL).

If you mean the mysql5 port, then you're out of date; the current version is 5.1.60.

If you mean a standalone MySQL package installed elsewhere, then I can't help you with that, and might even suggest that you uninstall it, since having software installed outside of MacPorts can sometimes interfere with MacPorts. I don't think the standard MySQL distribution installs into any problematic locations, however, so you're probably fine.

I need to install mysql5-devel for some project development.

What do you mean, exactly? I am worried you may be under the mistaken impression that MacPorts adheres to the naming convention of Linux package managers where a package "foo" contains binaries and libraries and a package "foo-devel" contains development headers. That is not how MacPorts works. In MacPorts, all packages always contain development headers already. Instead, we use "-devel" ports to indicate development/unstable versions. So, if what you're after is the development headers for MySQL 5.1.x, just install the normal mysql5 port, not the mysql5-devel port.


Yeah, the mysql installed was installed outside of MacPorts. Sorry, I did mistake *-devel package as development package. You are right, I need to recheck my need. BTW, the private tree works well here. Thanks for the tip anyway!

comment:11 Changed 15 months ago by hkroger@…

  • Cc hkroger@… added

Cc Me!

comment:11 Changed 11 months ago by ryandesign@…

Has duplicate #35079. Use the mysql55 port instead.

comment:12 Changed 11 months ago by jmr@…

  • Cc jwa@… added

comment:13 follow-up: ↓ 15 Changed 11 months ago by ryandesign@…

  • Cc pixilla@… added

This is presumably already fixed in the mysql55 port, which replaces the mysql5-devel port. mysql5-devel isn't being updated anymore.

comment:14 Changed 10 months ago by elisko@…

  • Cc elisko@… added

Cc Me!

comment:15 in reply to: ↑ 13 Changed 3 days ago by jmr@…

Replying to ryandesign@…:

This is presumably already fixed in the mysql55 port, which replaces the mysql5-devel port. mysql5-devel isn't being updated anymore.

Shouldn't it be marked as replaced_by then?

comment:16 Changed 3 days ago by pixilla@…

  • Status changed from new to closed
  • Resolution set to fixed

mysql5-devel has been replaced_by mysql55. See r106256

Note: See TracTickets for help on using tickets.