Opened 9 years ago
Closed 9 years ago
#50849 closed defect (invalid)
libgcc +universal build failure
Reported by: | joy.757@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | libgcc |
Description
I was trying to install gcc5 +universal (having set universal_archs) in order to be able to use -m32. I got the following error:
---> Fetching distfiles for libgcc ---> Verifying checksums for libgcc ---> Extracting libgcc ---> Applying patches to libgcc ---> Configuring libgcc ---> Building libgcc Error: org.macports.build for port libgcc returned: command execution failed Please see the log file for port libgcc for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_distfiles.macports.org_ports_lang_gcc5/libgcc/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libgcc failed
Also tried to install just libgcc and got the same error. The logs mentioned in the error message (for gcc5 as well as libgcc) is attached.
Attachments (2)
Change History (6)
comment:1 Changed 9 years ago by joy.757@…
comment:2 Changed 9 years ago by mf2k (Frank Schima)
Keywords: | libgcc removed |
---|---|
Owner: | changed from macports-tickets@… to mww@… |
Port: | libgcc added; gcc5 removed |
Summary: | gcc5 @5.3.0 +universal: Error: Processing of port libgcc failed → libgcc +universal build failure |
In the future, please fill in the Port field with the port that actually fails to build and Cc that port's maintainers (port info --maintainers libgcc
), if any.
comment:3 Changed 9 years ago by joy.757@…
It's working fine now. I managed to compile properly. I think the problem was caused by running out of hard disk space, since it ran fine after freeing ~10 GBs.
Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | log_libgcc.txt.bz2 added |
---|
Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | log_gcc5.txt.bz2 added |
---|
comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Resolution: | → invalid |
Status: | new → closed |
I've replaced your enormous attachments with compressed versions of them.
Both of the logs you attached are build failures of the libgcc port, and they both say:
fatal error: can't write PCH file: No space left on device
This means your disk was full.
The commands i ran were:
and later
Also, after running
I freed up 4+ GB of space. Not sure if that's normal or has anything to do with the problem.