#31536: openldap fails build in liblber : multiple target patterns -----------------------------------------+---------------------------------- Reporter: from-macports.org@… | Owner: landonf@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: openldap -----------------------------------------+---------------------------------- Old description:

My /Developer partition is on another drive. Therefore, the path to the drive is /Volumes/750gb HDD/Developer.

When compiling openldap (gnupg requires this) it fails due to a:

:info:build Makefile:402: *** multiple target patterns. Stop.

error. This appears to be due to a path problem in the library makefiles. Example excerpt from the Makefile: assert.lo: ../../include/portable.h assert.lo: assert.c assert.lo: ../../include/ldap_cdefs.h assert.lo: ../../include/ac/fdset.h assert.lo: ../../include/ac/assert.h

When you combine the lines: assert.lo: /Volumes/750gb\HDD/Developer/usr/llvm- gcc-4.2/bin/../lib/gcc/i686-apple-darwin10/4.2.1/include/stddef.h

It compiles normally.

Other makes in libraries seem to have this as well.

Attached: Full error log, makefile excerpt.

New description: My /Developer partition is on another drive. Therefore, the path to the drive is /Volumes/750gb HDD/Developer. When compiling openldap (gnupg requires this) it fails due to a: {{{ :info:build Makefile:402: *** multiple target patterns. Stop. }}} error. This appears to be due to a path problem in the library makefiles. Example excerpt from the Makefile: {{{ assert.lo: ../../include/portable.h assert.lo: assert.c assert.lo: ../../include/ldap_cdefs.h assert.lo: ../../include/ac/fdset.h assert.lo: ../../include/ac/assert.h }}} When you combine the lines: {{{ assert.lo: /Volumes/750gb\HDD/Developer/usr/llvm- gcc-4.2/bin/../lib/gcc/i686-apple-darwin10/4.2.1/include/stddef.h }}} It compiles normally. Other makes in libraries seem to have this as well. Attached: Full error log, makefile excerpt. -- Comment(by ryandesign@…): Having spaces in the path to your compiler, or in the path to MacPorts, is not a good idea; a lot of software projects have not been tested in that configuration and will probably fail. So you will have a better experience if you rename your paths (in this case your "750gb HDD" volume) so that they do not contain spaces. -- Ticket URL: <https://trac.macports.org/ticket/31536#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS