I recently upgraded to Mac OS X Lion 10.7.2. I also installed the latest version of Xcode (version 4.2) in order to build MacPorts. After doing this, I had no problems executing
sudo port selfupdate, which downloaded the latest version of MacPorts (version 2.0.3). However, I saw a LOT of compile warnings, especially for packages/ports like Python, when executing
sudo port upgrade outdated. For other packages/ports I noticed that a couple of compiler options were obsolete and/or ignored. Otherwise, I had no problem rebuilding MacPorts.
Are the compile warnings generated during the build a result of poor programming, or are they a product of the (possible) changes to the
gcc compiler? If the compile warnings are a result of poor programming and, as I didn't notice such warnings when initially installing MacPorts under Snow Leopard, have the compiler options to suppress such warnings changed?
As for those compiler options that were obsolete and/or ignored, is this also a result to (possible) changes to the
gcc compiler, or is this a feature of the script used for rebuilding major releases of MacPorts?