I don't think we need to patch anything -- I implemented a script to post-process the results of the configure step, and add the variables I need to Makefile.config. That was easy enough, since I have a build system that makes this kind of customization really easy.
I managed to coerce OpenAFS into linking against my special paths to ncurses, with no problem. I think in this specific case, what I'm doing is probably not generic enough to justify changing OpenAFS, so I'll continue working with a local solution. On Fri, Oct 1, 2010 at 10:47 AM, Andrew Deason <[email protected]>wrote: > On Fri, 1 Oct 2010 09:10:34 -0400 > Phillip Moore <[email protected]> wrote: > > > Well, I didn't go nearly far enough into the caves on that spelunking > > trip... > > > > XCFLAGS and XLDFLAGS appear to be reset, and not inherited from the > > environment either. > > > > Short of post-processing the auto-generated Makefiles, and adding the > > necessary paths to each place they are needed, is there a generic > > mechanism for seeding these variables with arbitrary values? > > I'm not aware of any, though I haven't really tried. XCFLAGS and > XLDFLAGS (on some platforms anyway) are set in src/cf/osconf.m4; see the > big switch statement for AFS_SYSNAME. You can hard code them there in > your sysname-specific section, or perhaps you/we could add code after > that section that grabs a var from the environment and appends to > XCFLAGS/XLDFLAGS. > > -- > Andrew Deason > [email protected] > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info >
