mysql5 fails with Xcode 4.2 (clang)

[thomas.visser@…]

Instaling the mysql5 port fails with the following error:

:info:build ld: in ../libmysqld.a(), archive member '' with length 0 is not mach-o or llvm bitcode for architecture x86_64

See ​http://pastebin.com/rA4wUvfD for a larger portion of the main.log file.

I also tried installing the port using +universal. That, and installing mysql5-devel, resulted in the same error.

I am running XCode 4.2 on Snow Leopard on a 2011 MacBook Pro.

[thomas.visser@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

This problem is new to me. Please clean and try again and attach the entire main.log to this ticket.

[ryandesign (Ryan Carsten Schmidt)]

Replying to thomas.visser@…:

I am running XCode 4.2 on Snow Leopard on a 2011 MacBook Pro.

I assume you mean 4.0.2, the latest version? I haven't tried Xcode 4 yet but I haven't heard any other reports of mysql5 breaking with Xcode 4.

[thomas.visser@…]

mysql5 main.log

[thomas.visser@…]

I cleaned and tried again; it resulted in the same error. I have uploaded the entire main.log as an attachment. I am running Xcode 4.2, it comes with the iOS5 beta and was released last monday.

I have had some more problems with macports recently. My previous install was completely broken, a 'port install' always resulted in an immediate segmentation fault. I deinstalled macports, removed all ports and reinstalled it. After the reinstall I still ran into some problems, e.g. building python27 failed unless I added +universal. Might be related, might be a clue?

[ryandesign (Ryan Carsten Schmidt)]

Thanks. But we can't really help with beta releases of Mac OS X, Xcode, or related Apple products. (Most of us don't have access to them.) Sorry, I don't know how to help with this. You could try reporting the problem to the developers of MySQL (​http://bugs.mysql.com/ -- it may be a MySQL bug) and/or to Apple (​https://bugreport.apple.com/ -- it may be an Xcode 4.2 bug).

[thomas.visser@…]

Thanks for your help. I'll try to get help from mysql/apple.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #29811.

[thomas.visser@…]

I was able to install mysql5-server just fine with XCode 4.2 beta2. I think this issue can be closed.

[ryandesign (Ryan Carsten Schmidt)]

Thanks for letting me know.

[page.agent@…]

Replying to thomas.visser@…:

I was able to install mysql5-server just fine with XCode 4.2 beta2. I think this issue can be closed.

Have you also tried to install mysql5?

I'm experiencing the same problem although using Xcode 4.0.2 on SnowLeopard. Was able to compile and install apache2, php, mysql5-server but mysql5 gives me the same error as reported above. Also tried +universal (after cleaning and uninstalling all packages).

Here is a excerpt of the log:

:info:build libtool: link: /Developer/usr/bin/llvm-g++-4.2 -O2 -fPIC -arch x86_64 -fno-implicit-templates -fno-exceptions -fno-rtti -D_P1003_1B_VISIBLE -DSIGNAL_WITH_VIO_CLOSE -DSIGNALS_DONT_BREAK_READ -DIGNORE_SIGHUP_SIGQUIT -DDONT_DECLARE_CXA_PURE_VIRTUAL -arch x86_64 -o mysqltest_embedded mysqltest.o  -L/opt/local/lib ../libmysqld.a -ldl ../../regex/libregex.a -lm -lm -L/opt/local/lib/ -lssl -lcrypto -lz
:info:build ld: in ../libmysqld.a(H‰ùˆHÿÁHÿÈuöH), archive member 'H‰ùˆHÿÁHÿÈuöH' with length 0 is not mach-o or llvm bitcode for architecture x86_64
:info:build collect2: ld returned 1 exit status

[macports@…]

try:

sudo ln -s /usr/bin/gcc /usr/bin/gcc-4.2

allowed me to selfupdate and build.

MBP 2011, XCode 4.2 (4C199), Snow Leopard 10.6.8

[ryandesign (Ryan Carsten Schmidt)]

Absolutely do not mess around in /usr/bin. Please undo whatever you did.

To the best of my knowledge, /usr/bin/gcc-4.2 doesn't even exist anymore in Xcode 4.2.

Now that Xcode 4.2 final is out, it would be interesting to hear from people using it. If you're having trouble building mysql5 with clang (which is the default compiler on Xcode 4.2), try with llvm-gcc-4.2:

sudo port clean mysql5
sudo port install configure.compiler=llvm-gcc-4.2

Please let us know here if that works.

[macports@…]

sudo port -v selfupdate

Failed because it couldn't find gcc-4.2. If you have a fix that would allow me to run selfupdate on 10.6.8 and XCode 4.2 I'd love to hear it. Since /usr/bin/gcc is gcc 4.2, I thought I'd try the hack I posted and it worked. I was dead in the water. The only information I can find on here related to this issue is "it works for me - issue closed", or "no it still doesnt work" from 4 months ago. This fix worked for me.

monster:~ jamie$ /usr/bin/gcc -v
Using built-in specs.
Target: i686-apple-darwin10
Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2336.1~3/src/configure --disable-checking --enable-werror --prefix=/Developer/usr/llvm-gcc-4.2 --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --enable-llvm=/private/var/tmp/llvmgcc42/llvmgcc42-2336.1~3/dst-llvmCore/Developer/usr/local --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 --with-gxx-include-dir=/usr/include/c++/4.2.1
Thread model: posix
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)

[macports@…]

I realized I'm hijacking someones ticket, so I made my own: #31619

[ryandesign (Ryan Carsten Schmidt)]

That's not gcc-4.2. That's llvm-gcc-4.2.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #30442.

[larryv (Lawrence Velázquez)]

Compiling mysql5 with clang fails for me, on OS X 10.7.2 (11C74) with Xcode 4.2. Attaching build log.

[larryv (Lawrence Velázquez)]

Build failure with Apple's clang 3.0 on OS X 10.7.2

[ryandesign (Ryan Carsten Schmidt)]

Does using llvm-gcc-4.2 or gcc 4.2 fix it?

[ryandesign (Ryan Carsten Schmidt)]

Larry, please see my remark above.

[larryv (Lawrence Velázquez)]

Replying to ryandesign@…:

Larry, please see my remark above.

Builds fine with llvm-gcc-4.2. The port already defaults to llvm-gcc-4.2 on systems with clang (r80074); I had to specify clang explicitly to test it. I guess I just verified that the clang issue is still around.