On Nov 18, 2019, at 15:36, Ces VLC wrote:

> Just issued a "sudo port install mingw-w64" on 10.6.8. Most needed 
> dependencies are downloaded prebuilt, except for gcc 9.2.0, which needs to be 
> built from source.

It is interesting that you were able to build i686-w64-mingw32-gcc-bootstrap 
@9.2.0 on 10.6. Our regular gcc9 port is programmed to error out on 10.6 and 
earlier saying it doesn't work. But if i686-w64-mingw32-gcc-bootstrap @9.2.0 
works on 10.6, maybe the normal gcc9 @9.2.0 would work too.

> When building the bootstrap stage, I get this warning:
> 
> [...]
> --->  Attempting to fetch gcc-9.2.0.tar.xz from 
> http://mirror.cc.columbia.edu/pub/software/gnu/gcc/gcc-9.2.0/
> --->  Verifying checksums for i686-w64-mingw32-gcc-bootstrap                  
>        
> --->  Extracting i686-w64-mingw32-gcc-bootstrap
> --->  Applying patches to i686-w64-mingw32-gcc-bootstrap
> --->  Configuring i686-w64-mingw32-gcc-bootstrap
> --->  Building i686-w64-mingw32-gcc-bootstrap
> --->  Staging i686-w64-mingw32-gcc-bootstrap into destroot
> Warning: i686-w64-mingw32-gcc-bootstrap installs files outside the common 
> directory structure.
> --->  Installing i686-w64-mingw32-gcc-bootstrap @9.2.0_0
> --->  Activating i686-w64-mingw32-gcc-bootstrap @9.2.0_0
> --->  Cleaning i686-w64-mingw32-gcc-bootstrap
> [...]
> 
> And then the build continues with the next dependency. It's still building in 
> this moment. No errors for the moment.
> 
> Should I worry about that "Warning: i686-w64-mingw32-gcc-bootstrap installs 
> files outside the common directory structure.", or is it expected?

It is expected, and it is just a notification to you that, unlike most ports 
which confine their file installations to /Applications/MacPorts and a small 
standardized list of directories within /opt/local, this port does not, for 
whatever reason. All of the cross-compiling gcc ports do this because they 
install to a nonstandard directory within /opt/local, presumably so that they 
do not conflict with the normal non-cross-compiling gcc.

Reply via email to