[MacPorts] #20775: gnustep-base: gnustep-config: command not found
MacPorts
noreply at macports.org
Mon Jun 18 17:39:55 PDT 2012
#20775: gnustep-base: gnustep-config: command not found
-------------------------------------+--------------------------------------
Reporter: ryandesign@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.7.1
Keywords: | Port: gnustep-base
-------------------------------------+--------------------------------------
Comment(by drh@…):
Replying to [comment:17 ryandesign@…]:
> Replying to [comment:16 drh@…]:
Many thanks for the reply. I seem to have progressed. On Mac OS X 10.7.4
the path is defined in /etc/paths and I fixed that. The "source" command
was suddenly found, having previously been "Command not found" (a path
problem???)
However, "sudo port install gnustep-base" now fails because it can't use
the gcc-4.2 compiler which is freshly installed in /usr/bin (AFAIK, that
is the right place). As this isn't gcc-3.x, libgcc_s and libobjc would
seem to be irrelevant, but what equivalents for gcc-4.2 are expected and
where should they be? There seem to be no equivalents on this machine
:info:configure configure: error: The Objective-C compiler does not work
or is not installed properly.
:info:configure Command failed: cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
.org_release_tarballs_ports_gnustep_gnustep-base/gnustep-base/work
/gnustep-base-1.19.1" && ./configure --prefix=/opt/local CC=/usr/bin/clang
GNUSTEP_MAKEFILES=/opt/local/share/GNUstep/Makefiles --disable-tls
--enable-libffi --with-ffi-include=/opt/local/include/gcc42 --with-ffi-
library=/opt/local/lib/gcc42
:info:configure Exit code: 1
:error:configure org.macports.configure for port gnustep-base returned:
configure failure: command execution failed
:debug:configure Error code: NONE
:debug:configure Backtrace: configure failure: command execution failed
while executing
"$procedure $targetname"
----------
> > ".profile" and ".rc" are either empty or don't exist,
>
> Use whatever file you use for shell startup commands. If you don't use
.profile, perhaps you use .bash_profile or .bashrc.
>
> > and "source" is not a recognisable command. Is the intention to
execute the .sh script?
>
> [http://superuser.com/questions/46139/what-does-source-do "source" is a
normal built-in bash command]. It executes the contents of a file as a
bash script.
--
Ticket URL: <https://trac.macports.org/ticket/20775#comment:18>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list