Opened 9 years ago

Closed 9 years ago

#33911 closed defect (worksforme)

glib2 installation fails at configuration

Reported by: martin.kastner@… Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.0.4
Keywords: Cc:
Port: glib2

Description (last modified by ryandesign (Ryan Schmidt))

Lion 10.7.3
Xcode 4.3.2
macports 2.0.4

selfupdate, upgrade outdated -> glib2 2.30.3 fails

Attachments (4)

config (32.9 KB) - added by martin.kastner@… 9 years ago.
config.log
main.log (30.5 KB) - added by martin.kastner@… 9 years ago.
main.log
config.log (14.8 KB) - added by martin.kastner@… 9 years ago.
config.log
main.2.log (30.5 KB) - added by martin.kastner@… 9 years ago.
main.log

Download all attachments as: .zip

Change History (13)

Changed 9 years ago by martin.kastner@…

Attachment: config added

config.log

comment:1 Changed 9 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)
Owner: changed from macports-tickets@… to ryandesign@…
Port: glib2 added

Please also attach the main.log.

Changed 9 years ago by martin.kastner@…

Attachment: main.log added

main.log

comment:2 Changed 9 years ago by ryandesign (Ryan Schmidt)

Are you sure these two files were produced by the same MacPorts installation attempt? I'm having trouble matching them up. For example the main.log says the error is:

:info:configure checking whether the C compiler works... no

However looking at this particular test in the config.log, it says:

configure:3943: checking whether the C compiler works
configure:3965: gcc    conftest.c  >&5
configure:3969: $? = 0
configure:4017: result: yes

Could you "sudo port clean glib2" and try again, then attach the new main.log and config.log?

Changed 9 years ago by martin.kastner@…

Attachment: config.log added

config.log

Changed 9 years ago by martin.kastner@…

Attachment: main.2.log added

main.log

comment:3 in reply to:  2 Changed 9 years ago by martin.kastner@…

You are right the two files were created separately. The config.log was created by running the configuration manually with the same options as given in the main.log.

New files attached.

comment:4 Changed 9 years ago by ryandesign (Ryan Schmidt)

Ok, the config.log now says:

configure:3943: checking whether the C compiler works
configure:3965: /usr/bin/llvm-gcc-4.2 -pipe -O2 -fstrict-aliasing -arch x86_64 -I/opt/local/include -L/opt/local/lib -lresolv -bind_at_load -arch x86_64 conftest.c  >&5
cc1: error: /Developer/usr/llvm-gcc-4.2/lib/gcc/i686-apple-darwin11/4.2.1/include: Permission denied
cc1: error: /Developer/usr/llvm-gcc-4.2/i686-apple-darwin11/include: Permission denied
configure:3969: $? = 1
configure:4007: result: no

Sounds like something has gone amiss in your Xcode installation. A permissions error, I imagine, but I couldn't tell you what the correct permissions are for each of the thousands of items Xcode installs. I suggest you follow Apple's instructions to uninstall Xcode, then reinstall Xcode and its command line tools.

comment:5 Changed 9 years ago by martin.kastner@…

It seems like as if the Xcode path is not used/found in the configuration. I checked it using:

#sudo xcode-select -print-path
/Applications/Xcode.app/Contents/Developer

The paths /Developer/... do not exist that's why we have permission errors. The other ports seem to have worked properly. This one didn't. I'll create a link pointing to the appropriate directory at the location where the configuration script is looking for it and see what happens.

comment:6 in reply to:  5 Changed 9 years ago by martin.kastner@…

Using the link worked. Thanks for the pointer!

comment:7 Changed 9 years ago by ryandesign (Ryan Schmidt)

You should not have to make a symlink at /Developer. Are you sure you've not only installed Xcode 4.3.2 but also installed Xcode 4.3.2's command line tools? This is a separate install that must be performed from within the Xcode application. See our guide.

comment:8 in reply to:  7 Changed 9 years ago by martin.kastner@…

I reinstalled the command line tools. I forced uninstall on glib2, removed the /Development link and reinstalled glib2. Now it seemed to work alright without the extra symlinks. Not sure what went wrong in the first installation. Thanks!

comment:9 Changed 9 years ago by ryandesign (Ryan Schmidt)

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.