libgcc 4.8.1 errors on a fresh install macports for Mavericks (OS X 10.9)

Ryan Schmidt ryandesign at macports.org
Fri Nov 1 20:33:28 PDT 2013


On Nov 1, 2013, at 20:28, William Capehart wrote:

> I went back through the error messages and saw that the conflict was with the module:  
> 
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc48/libgcc/work/gcc-4.8.1/gcc/fortran/module.c  
> 
> And 
> 
>  /usr/include/mach/vm_types.h 
> 
> I did something that I DON’T think was the smartest thing and commented out  line 40 of the vm_types file.
> 
>  typedef vm_offset_t           pointer_t;
> 
> And left the module.c line intact.  
> 
> This seems to have worked.  libgcc finally completed the build  with no other errors and I am proceeding to build gcc48 and the rest of my working science resources.
> 
> I have misgivings as to editing something in /usr/include and am planning restoring line 40 once all my builds are complete .  And additionally I am still apprehensive as to why my system seems to be the only rig around here that has been impacted.  
> 
> If what I did is a really bad idea.. Uh.. This would be the time to tell me. :-) 
> 
> I am reluctant to report this patch on the macports bug tracking site until I have confidence that this working for my critical software.

Certainly you should never edit files in /usr/include.




More information about the macports-users mailing list