the problem here is that i have a building system here that need to work automatically.
btw no problem I've build a set of patch... for authors for configure of sipXproxy and so on I just miss the point on how the things works here.. to propose patch and be accepted. thanks Domenico Chierico On Tue, Jun 19, 2012 at 4:46 PM, Joegen Baclor <[email protected]> wrote: > Yep. Automagic seems like the way to go but right now, this set of > patches just need to get built as RPMS. As i've said, we already have the > automagic in place in master so if you can simply highlight "-mt" and press > delete, that's the way to go with 4.4. > > > On 06/19/2012 08:39 PM, Domenico Chierico wrote: > > at least let it be automagic :) > > > On Tue, Jun 19, 2012 at 2:34 PM, Joegen Baclor <[email protected]> wrote: > >> Hi domenico, >> >> This has been a known issue. Since we are compilign against Centos 5, we >> are following the format that OS has. In 4.6, we have a >> m4_include([config/ax_boost_base.m4]) that can do this during >> configuration. In 4.4, I am not sure we have that so my suggestion is to >> just manually change the linker flags in Makefile.am for Fedora since there >> is not muh that can change in 4.4 that would require you to frequently >> change this. Douglas is the build guru. Let's see if he chimes in. >> >> Joegen >> >> >> On 06/19/2012 08:04 PM, Domenico Chierico wrote: >> >> well with the last pull from 4.4 branch I'm experiencing some problems >> into builds. >> >> Now proxy can't build 'cose Makefile require linking on libboost_thread >> instead on fedora 14 we have libboost_thread-mt >> >> so >> any suggestion there? >> >> >> >> >> _______________________________________________ >> sipx-dev mailing [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> >> >> > >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
