ragel @6.8_0 did not build cleanly on Mavericks

[hardwhack]

Trying to install textmate2 om Mavericks. Got hung up on install of ragel-6.8 (among other things).

Went into ragel build directory and gave build command manually. Error was

/usr/bin/clang++ -DHAVE_CONFIG_H -I. -I../aapl  -I/opt/local/include -Wall -pipe -Os -arch x86_64 -MT ragel-rbxgoto.o -MD -MP -MF .deps/ragel-rbxgoto.Tpo -c -o ragel-rbxgoto.o `test -f 'rbxgoto.cpp' || echo './'`rbxgoto.cpp
javacodegen.cpp:1187:20: error: use of undeclared identifier 'setiosflags'; did you mean
      'std::setiosflags'?
        out << setw(5) << setiosflags(ios::right) << item;
                          ^~~~~~~~~~~
                          std::setiosflags
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/iomanip:110:1: note: 
      'std::setiosflags' declared here
setiosflags(ios_base::fmtflags __mask)
^
1 error generated.
make[2]: *** [ragel-javacodegen.o] Error 1
make[2]: *** Waiting for unfinished jobs....
mv -f .deps/ragel-rubyflat.Tpo .deps/ragel-rubyflat.Po
mv -f .deps/ragel-rubyftable.Tpo .deps/ragel-rubyftable.Po
mv -f .deps/ragel-rubyfflat.Tpo .deps/ragel-rubyfflat.Po
mv -f .deps/ragel-rbxgoto.Tpo .deps/ragel-rbxgoto.Po
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ragel/ragel/work/ragel-6.8/ragel'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ragel/ragel/work/ragel-6.8/ragel'
make: *** [all-recursive] Error 1
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_ragel/ragel/work/ragel-6.8'

I changed line 1187 in javacodegen.cpp from setiosflags to std::setiosflags and then ragel built and installed without problems. Textmate2 worked as well-- sort of (will describe in more detail in Textmate2 ticket).

[ryandesign (Ryan Carsten Schmidt)]

Run sudo port selfupdate. This has already been fixed. Duplicate of #40856.