On Fri, Jul 30, 2010 at 10:39 AM, patrick keshishian <pkesh...@gmail.com> wrote: > On Thu, Jul 29, 2010 at 10:37 PM, patrick keshishian <pkesh...@gmail.com> > wrote: >> On Wed, Jul 28, 2010 at 10:27 PM, David Coppa <dco...@gmail.com> wrote: >>> On Thu, Jul 29, 2010 at 3:42 AM, patrick keshishian <pkesh...@gmail.com> >>> wrote: >>>> FF 3.6.7 was crashing as reported by Dawe and me[1] same as X (from >>>> snapshots and built from source). Rebuilding xenocara from source with >>>> debug got X working (don't know why). >>>> >>>> I tried building FF 3.6.8 and it too is crashing with signal 11. I >>>> built FF 3.6.8 with DEBUG="-g -O0" hoping to at least get a backtrace >>>> out of the core, but evidently the resulting binary is stripped[2] >>>> (brilliant!). >>>> >>>> Question: I'm about to rebuild this monster again on my slow ibook. >>>> how do I prevent it from being stripped? >>>> >>>> Google finds me "--disable-install-strip", but does our port >>>> infrastructure provide a more uniform way of handling this across all >>>> (or most) ports? >>> >>> DEBUG="-g -O0" INSTALL_STRIP= make clean repackage reinstall >> >> Thanks David! > > > ughh.. it still ended up stripping firefox-bin. i don't know what else > to try besides trying some hack like replacing system strip with true > or something.
I've crawled a little into mozilla-firefox source and its configure stuff... Just add "--disable-install-strip" to CONFIGURE_ARGS and go ahead: apparently there's no sane way to avoid stripping binaries using environment variables as we use to do. ciao, david
