[OpenAFS] Re: Latest docs on building the OpenAFS source code
Phillip Moore
w.phillip.moore@gmail.com
Fri, 1 Oct 2010 11:28:55 -0400
--00c09f905ca34664f004918fdaf0
Content-Type: text/plain; charset=ISO-8859-1
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 <adeason@sinenomine.net>wrote:
> On Fri, 1 Oct 2010 09:10:34 -0400
> Phillip Moore <w.phillip.moore@gmail.com> 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
> adeason@sinenomine.net
>
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
--00c09f905ca34664f004918fdaf0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div><br></div>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 va=
riables I need to Makefile.config. =A0That was easy enough, since I have a =
build system that makes this kind of customization really easy.<div>
<br></div><div>I managed to coerce OpenAFS into linking against my special =
paths to ncurses, with no problem.</div><div><br></div><div>I think in this=
specific case, what I'm doing is probably not generic enough to justif=
y changing OpenAFS, so I'll continue working with a local solution.</di=
v>
<div><br></div><div><div class=3D"gmail_quote">On Fri, Oct 1, 2010 at 10:47=
AM, Andrew Deason <span dir=3D"ltr"><<a href=3D"mailto:adeason@sinenomi=
ne.net">adeason@sinenomine.net</a>></span> wrote:</div><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">On Fri, 1 Oct 2010 09:10:34 -0400<br>
<div class=3D"im">Phillip Moore <<a href=3D"mailto:w.phillip.moore@gmail=
.com">w.phillip.moore@gmail.com</a>> wrote:<br>
<br>
</div><div class=3D"im">> Well, I didn't go nearly far enough into t=
he caves on that spelunking<br>
> trip...<br>
><br>
> XCFLAGS and XLDFLAGS appear to be reset, and not inherited from the<br=
>
> environment either.<br>
><br>
> Short of post-processing the auto-generated Makefiles, and adding the<=
br>
> necessary paths to each place they are needed, is there a generic<br>
> mechanism for seeding these variables with arbitrary values?<br>
<br>
</div>I'm not aware of any, though I haven't really tried. XCFLAGS =
and<br>
XLDFLAGS (on some platforms anyway) are set in src/cf/osconf.m4; see the<br=
>
big switch statement for AFS_SYSNAME. You can hard code them there in<br>
your sysname-specific section, or perhaps you/we could add code after<br>
that section that grabs a var from the environment and appends to<br>
XCFLAGS/XLDFLAGS.<br>
<font color=3D"#888888"><br>
--<br>
Andrew Deason<br>
<a href=3D"mailto:adeason@sinenomine.net">adeason@sinenomine.net</a><br>
<br>
_______________________________________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</a><br=
>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info" target=
=3D"_blank">https://lists.openafs.org/mailman/listinfo/openafs-info</a><br>
</font></blockquote></div><br></div>
--00c09f905ca34664f004918fdaf0--