#49552 closed defect (duplicate)
problem for install libgcc on El capitan 10.11.1
| Reported by: | wanghaotian2280@… | Owned by: | mww@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.4 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | libgcc |
Description
Hello
I have a difficulty to build libgcc on my recent upgraded El Capitan 10.11.1. I did follow the Xcode and macports installation and run "sudo port install libgcc". However, it gives the error as
error:build org.macports.build for port libgcc returned: command execution failed
Details can be found in log (see attachment). Then I did the same way as Ticket #49060 but it still does not work. Thanks.
Attachments (1)
Change History (6)
Changed 9 years ago by wanghaotian2280@…
| Attachment: | main.log.zip added |
|---|
comment:1 follow-up: 2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added; mww@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to mww@… |
| Port: | libgcc added |
comment:2 Changed 9 years ago by wanghaotian2280@…
Replying to ryandesign@…:
The error in #49060 sounds unrelated to the error you're experiencing. Rather, your issue sounds like a duplicate of #40998. Does /usr/include/malloc.h exist on your system? It should not.
Yes, the malloc.h is there because previously I make a link to it. Now I'm try to delete it in /usr/include, by using both "rm" and "sudo rm", however it shows
rm: malloc.h: Operation not permitted
Could you help me? Thanks.
comment:3 follow-up: 4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
El Capitan introduces a new feature called System Integrity Protection which prevents you from modifying the contents of /usr and other system directories, even as root. The El Capitan installer should have removed foreign items from protected locations, but apparently it missed /usr/include/malloc.h. I'll file a bug report with Apple about this. You'll have to boot to the recovery partition, disable SIP, remove /usr/include/malloc.h (and if you've previously made any other changes in system directories, now would be a good opportunity to undo them, if they're still there), then re-enable SIP.
comment:4 follow-up: 5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ryandesign@…:
The El Capitan installer should have removed foreign items from protected locations, but apparently it missed /usr/include/malloc.h. I'll file a bug report with Apple about this.
I didn't file a bug report because I was not able to reproduce this problem. On a Yosemite system, I placed a malloc.h symlink (and another symlink, and a file) in /usr/include, then upgraded to El Capitan. The file I placed in /usr/include was moved to the QuarantineRoot, as it should have been. The symlinks I created and everything else in /usr/include were silently deleted, as they should be. I used the El Capitan 10.11.1 installer; maybe an earlier version of the installer had this problem but it has since been fixed.
comment:5 Changed 9 years ago by wanghaotian2280@…
Replying to ryandesign@…:
Replying to ryandesign@…:
The El Capitan installer should have removed foreign items from protected locations, but apparently it missed /usr/include/malloc.h. I'll file a bug report with Apple about this.
I didn't file a bug report because I was not able to reproduce this problem. On a Yosemite system, I placed a malloc.h symlink (and another symlink, and a file) in /usr/include, then upgraded to El Capitan. The file I placed in /usr/include was moved to the QuarantineRoot, as it should have been. The symlinks I created and everything else in /usr/include were silently deleted, as they should be. I used the El Capitan 10.11.1 installer; maybe an earlier version of the installer had this problem but it has since been fixed.
Thanks for the help. The problem found is due to the fact that El Capitan prevents users from modifying the contents under /usr. After disable SIP, it works fine. Thank you very much.
The error in #49060 sounds unrelated to the error you're experiencing. Rather, your issue sounds like a duplicate of #40998. Does /usr/include/malloc.h exist on your system? It should not.