Why did the email subject say: Subject: ports/140805: Update port: www/mod_wsgi Upgrade to 2.6
when it was for 2.7? http://groups.google.com/group/lucky.freebsd.ports.bugs.digest/browse_frm/thread/1d5e5b72eb25f258/8efe0ec2aa02104f?q=mod_wsgi Was it meant to imply upgrade to existing 2.6 to replace it with 2.7. Just thought it was strangely described. Graham 2009/11/23 Douglas Thrift <[email protected]>: > Ack! > > I just got 2.7 into FreeBSD ports with your patch and 3.0 was compiling > with the patch. > -- > Douglas William Thrift > <[email protected]> > <http://douglasthrift.net/> > > Graham Dumpleton wrote: >> If people just want to validate that 2.8 and 3.1 in subversion work >> for builds done by package installers, I'll quickly roll some new >> versions to address the CFLAGS issue. Details at: >> >> http://code.google.com/p/modwsgi/wiki/ChangesInVersion0208 >> http://code.google.com/p/modwsgi/wiki/ChangesInVersion0301 >> >> Graham >> >> 2009/11/23 Graham Dumpleton <[email protected]>: >>> 2009/11/23 Graham Dumpleton <[email protected]>: >>>> 2009/11/23 Damjan <[email protected]>: >>>>> >>>>>> Have fun. >>>>>> >>>>>> http://code.google.com/p/modwsgi/wiki/ChangesInVersion0207http://code.google.com/p/modwsgi/wiki/ChangesInVersion0300 >>>>>> >>>>>> Version 3.0 is same as last release candidate exception for version >>>>>> string embedded within it. >>>>> anyone knows of Ubuntu Karmic packages for mod_wsgi 3.0? >>>>> or at least a recipe for building a proper package? >>>> Build from source code yourself as per instructions on mod_wsgi site >>>> or in the source README. >>>> >>>> The issue being discussed here only relates to the build scripts that >>>> Unix distributions wrap around the mod_wsgi configure/make to package >>>> it up for the binary repositories. >>>> >>>> Building it yourself from source code is not affected and should work. >>>> >>>> I'll put out a patch for the CFLAGS stuff later today if get time. >>> For now use the following patches. >>> >>> The issue of embedded spaces probably doesn't cause a problem because >>> both halves will be prefixed and apxs will then remove prefix from >>> both and pass in as originally supplied. >>> >>> Also no need to worry about arguments already using -Wc, as apxs will >>> again strip off duplicate and original -Wc, will still get through >>> compiler as originally intended. >>> >>> I can see now how my -Wl, problems were different as in that case apxs >>> wasn't just using it as magic prefix that got stripped off again >>> anyway. >>> >>> Index: configure >>> =================================================================== >>> --- configure (revision 1487) >>> +++ configure (working copy) >>> @@ -1851,16 +1851,22 @@ >>> fi >>> >>> CFLAGS1="" >>> +for arg in ${CFLAGS} >>> +do >>> + CFLAGS1="${CFLAGS1} -Wc,$arg" >>> +done >>> + >>> +CFLAGS2="" >>> if test -x /usr/bin/lipo; then >>> LDFLAGS3="" >>> ARCHITECTURES=`/usr/bin/lipo -info $HTTPD | sed -e 's/.*://'` >>> for ARCH in $ARCHITECTURES; do >>> - CFLAGS1="${CFLAGS1} -Wc,'-arch ${ARCH}'" >>> + CFLAGS2="${CFLAGS2} -Wc,'-arch ${ARCH}'" >>> LDFLAGS3="${LDFLAGS3} -arch ${ARCH}" >>> done >>> fi >>> >>> -CFLAGS="${CFLAGS} ${CFLAGS1}" >>> +CFLAGS="${CFLAGS1} ${CFLAGS2}" >>> LDFLAGS="${LDFLAGS} ${LDFLAGS1} ${LDFLAGS2} ${LDFLAGS3}" >>> LDLIBS="${LDLIBS} ${LDLIBS1} ${LDLIBS2} ${LDLIBS3}" >>> >>> Index: configure.ac >>> =================================================================== >>> --- configure.ac (revision 1487) >>> +++ configure.ac (working copy) >>> @@ -141,16 +141,22 @@ >>> fi >>> >>> CFLAGS1="" >>> +for arg in ${CFLAGS} >>> +do >>> + CFLAGS1="${CFLAGS1} -Wc,$arg" >>> +done >>> + >>> +CFLAGS2="" >>> if test -x /usr/bin/lipo; then >>> LDFLAGS3="" >>> ARCHITECTURES=`/usr/bin/lipo -info $HTTPD | sed -e 's/.*://'` >>> for ARCH in $ARCHITECTURES; do >>> - CFLAGS1="${CFLAGS1} -Wc,'-arch ${ARCH}'" >>> + CFLAGS2="${CFLAGS2} -Wc,'-arch ${ARCH}'" >>> LDFLAGS3="${LDFLAGS3} -arch ${ARCH}" >>> done >>> fi >>> >>> -CFLAGS="${CFLAGS} ${CFLAGS1}" >>> +CFLAGS="${CFLAGS1} ${CFLAGS2}" >>> LDFLAGS="${LDFLAGS} ${LDFLAGS1} ${LDFLAGS2} ${LDFLAGS3}" >>> LDLIBS="${LDLIBS} ${LDLIBS1} ${LDLIBS2} ${LDLIBS3}" >>> >>> >>> >>> Committed in subversion trunk at revision 1488. The trunk commit also >>> updates version string in mod_wsgi.c as well to 3.1-TRUNK. >>> >>> Graham >>> >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "modwsgi" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/modwsgi?hl=. >> >> > > -- > > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=. > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
