#20559 closed defect (invalid)
Ports won't install / self update doesn't work
Reported by: | vash_the__typhoon@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 1.6.0 |
Keywords: | Cc: | ||
Port: |
Description (last modified by mf2k (Frank Schima))
I have had macports working for a while, and decided to get the 'gimp - GNU image manipulation program'
'''#sudo port install gimp2''' ''Error: Unable to execute port: Could not find Portfile in /opt/local/var/macports/sources/rsync.macports.org/release/ports/graphics/openexr ''
I figured that its been a long time since I used it so I tried
'''#sudo port -d sync '''
which output a whole list of new ports, then tried to get the gimp again
'''#sudo port install gimp2 '''''Error: Requested variants do not match original selection. Please perform 'port clean gimp2' or specify the force option. Error: Status 1 encountered during processing.''
so i followed the instructions
'''#port clean gimp2''' ''Error: Unable to execute port: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_gimp2/work/.macports.gimp2.state is not writable - check permission on port directory''
Frustrated I tried to update the whole macports system
'''#sudo port selfupdate''' ''MacPorts base version 1.600 installed Downloaded MacPorts base version 1.710 Configuring, Building and Installing new MacPorts base Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command "cd /opt/local/var/macports/sources/rsync.macports.org/release/base && ./configure --prefix=/opt/local --with-install-user=root --with-install-group=admin --with-tclpackage=/Library/Tcl && make && make install" returned error 1 Command output: checking for /usr/bin/gnutar --no-same-owner support... yes checking how to mark unused variables... checking for gcc symbol visibility attribute... __attribute__((visibility("hidden"))) checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking if more special flags are required for pthreads... -D_THREAD_SAFE checking how to run the Objective C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking objc/objc.h usability... yes checking objc/objc.h presence... yes checking for objc/objc.h... yes checking if linking libobjc requires pthreads... no checking for Apple Objective-C runtime... yes checking for GNU Objective C runtime... no configure: Using Apple Objective-C runtime checking for Apple Foundation library... no configure: WARNING: GNUSTEP_SYSTEM_ROOT is not defined in your environment, preventing the use of GNUstep's Foundation library configure: error: Could not find a working Foundation implementation''
What does this mean, I've looked around but nothing made sense ... I already had a working version of Macports, now suddenly I can't update it?
What can I do?
Cheers
Attachments (2)
Change History (16)
comment:1 Changed 15 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|---|
Keywords: | Upgrading / Installing Fails removed |
comment:2 Changed 15 years ago by mf2k (Frank Schima)
Component: | ports → base |
---|
comment:3 Changed 15 years ago by mf2k (Frank Schima)
Sorry, I meant to ask "What version of Mac OS X are you running?" above.
comment:4 Changed 15 years ago by blb@…
Can you attach the config.log which should have been generated by configure? It should be in /opt/local/var/macports/sources/rsync.macports.org/release/base/
comment:5 Changed 15 years ago by vash_the__typhoon@…
Hey,
Running OS X 10.5.7
Attached (hopefully) is the config.log.
Cheers, B
comment:6 Changed 15 years ago by tobypeterson
Looks like you have a broken compiler installed as 'gcc' which is confusing things.
comment:7 Changed 15 years ago by vash_the__typhoon@…
I'm sorry, I don't understand how its broken, I have gcc as a compiler which works fine to compile my programs I write in C?
comment:8 Changed 15 years ago by blb@…
configure:2362: found /usr/bin/gcc configure:2373: result: gcc configure:2605: checking for C compiler version configure:2613: gcc --version >&5 gcc (GCC) 4.2.3
gcc 4.2.3 is not what /usr/bin/gcc should be (and for that matter, /usr/bin/gcc-4.2 is only 4.2.1) so you've modified things in /usr/bin which will definitely cause issues.
comment:9 Changed 15 years ago by tobypeterson
It looks like the configure script actually just runs 'gcc' - it's probably in /opt/local (via gcc_select). However, this particular one doesn't appear to be capable of passing the configure tests.
comment:10 Changed 15 years ago by vash_the__typhoon@…
Hey guys,
OK so now I'm a little bit confused. I have had some issues in the past with getting the 'right' gcc compiler that I need on my macbook, and so I have used macports to install some other versions of gcc compilers, plus which ever ones were already there by default. From macports i've got (>ports installed | grep gcc)
apple-gcc42 @5531_0 (active) gcc42 @4.2.3_0 (active) gcc_select @0.1_1+darwin_9 (active)
In /usr/bin i have (ls -l | grep gcc):
gcc -> /opt/local/var/macports/software/gcc42/4.2.3_0/opt/local/bin/gcc-mp-4.2 gcc-4.0 i686-apple-darwin9-gcc-4.0.1 powerpc-apple-darwin9-gcc-4.0.1
Can you help me out by telling me what to change? I am rather inexperienced with the inner-workings of unix systems but I can navigate around and make links etc.. which I hope can fix my problem.
Cheers,
comment:11 Changed 15 years ago by tobypeterson
Fix the /usr/bin/gcc link:
sudo ln -fs gcc-4.0 /usr/bin/gcc
comment:12 Changed 15 years ago by nerdling (Jeremy Lavergne)
Some additional thoughts from what I see up at the original description:
- You had an outdated version of MacPorts: do selfupdate instead of sync, as sync is a subset of selfupdate's operations
- You needed to run sudo for the clean operation:
sudo port selfupdate
- You should check for outdated ports once you get your compilers straightened about (which shouldn't have happened?):
sudo port upgrade outdated
comment:13 Changed 15 years ago by jmroot (Joshua Root)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Changed 15 years ago by vash_the__typhoon@…
Attachment: | new_error.txt added |
---|
New errors after "fixing" the gcc link
comment:14 Changed 15 years ago by vash_the__typhoon@…
Hey again, I hope someone still looks at this ...
I've fixed the link for gcc by doing what toby suggested (ln -fs gcc-4.0 /usr/bin/gcc) and now,
ls -l /usr/bin | grep gcc gcc -> gcc-4.0
Which I hoped would fix me up for the self update, but it didn't. Attached is a file called "new_error.txt" which is what i'm faced with now...
Any help/suggestions would be really appreciated....
B
Mac version of Mac OS X are you running? What version of Xcode?