[MacPorts] #29856: gcc44 @4.4.6 build failure
MacPorts
noreply at macports.org
Sun Jun 19 16:34:22 PDT 2011
#29856: gcc44 @4.4.6 build failure
----------------------------------+-----------------------------------------
Reporter: ryanopolis@… | Owner: mww@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: gcc44
----------------------------------+-----------------------------------------
Old description:
> Snow Leopard 10.6.7
> MacPorts: 1.9.2
> XCode: 4.02
>
> While trying to install gcc44, I receive a build error. This is a clean
> install of xcode and macports.
>
> Last part of log:
> {{{
> :info:build checking for iconv declaration...
> :info:build extern size_t iconv (iconv_t cd, char * *inbuf,
> size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
> :info:build updating cache ./config.cache
> :info:build configure: creating ./config.status
> :info:build config.status: creating Makefile
> :info:build config.status: creating config.h
> :info:build config.status: executing depdir commands
> :info:build mkdir .deps
> :info:build make[1]: *** [stage2-bubble] Error 2
> :info:build make: *** [bootstrap] Error 2
> :info:build shell command " cd
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/work/build"
> && /usr/bin/make -j2 bootstrap " returned error 2
> :error:build Target org.macports.build returned: shell command failed
> (see log for details)
> :debug:build Backtrace: shell command failed (see log for details)
> while executing
> "command_exec build"
> (procedure "portbuild::build_mai
> n" line 8)
> invoked from within
> "$procedure $targetname"
> }}}
> I have tried gcc43 and gcc45 with same results. Any help is greatly
> appreciated.
New description:
Snow Leopard 10.6.7 [[br]]
MacPorts: 1.9.2 [[br]]
XCode: 4.02
While trying to install gcc44, I receive a build error. This is a clean
install of xcode and macports.
Last part of log:
{{{
:info:build checking for iconv declaration...
:info:build extern size_t iconv (iconv_t cd, char * *inbuf,
size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
:info:build updating cache ./config.cache
:info:build configure: creating ./config.status
:info:build config.status: creating Makefile
:info:build config.status: creating config.h
:info:build config.status: executing depdir commands
:info:build mkdir .deps
:info:build make[1]: *** [stage2-bubble] Error 2
:info:build make: *** [bootstrap] Error 2
:info:build shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gcc44/work/build"
&& /usr/bin/make -j2 bootstrap " returned error 2
:error:build Target org.macports.build returned: shell command failed (see
log for details)
:debug:build Backtrace: shell command failed (see log for details)
while executing
"command_exec build"
(procedure "portbuild::build_mai
n" line 8)
invoked from within
"$procedure $targetname"
}}}
I have tried gcc43 and gcc45 with same results. Any help is greatly
appreciated.
--
Comment(by ryandesign@…):
Replying to [comment:5 ryanopolis@…]:
> My suspicion is that something in MacPorts is configured to look in
root/usr instead of opt/local/usr. Does that sound accurate to you?
No; in particular "opt/local/usr" doesn't make sense. "/usr" is a prefix
into which various core system files are installed, by Mac OS X and Xcode.
"/opt/local" is a prefix into which MacPorts and its ports install their
files. Most ports installed with MacPorts need to access some headers and
libraries from prefix /usr, and many need to access some headers and
libraries from prefix /opt/local. There is nothing to configure to make
this happen; this is just how things work. It ought to just work. We do
not understand why it is not working for you.
Replying to [comment:7 ryanopolis@…]:
> If you don't want to answer my questions farther than 'it works for me',
would you suggest a forum where I could post this and get a more robust
response?
I am not a gcc compilation expert so it's not that I don't want to answer
your questions further, it's that I do not know the answers. If the
MacPorts gcc maintainer, to whom this ticket is assigned, has time to
investigate, he might respond here. If not, you could try contacting the
gcc developers directly. You mentioned that you experienced the same
trouble with gcc43 and gcc45; you should probably also try gcc46 first
before reporting the problem upstream.
--
Ticket URL: <https://trac.macports.org/ticket/29856#comment:8>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list