[OpenAFS-devel] Build system help
Ben Huntsman
ben@huntsmans.net
Wed, 29 Mar 2023 17:38:39 +0000
--_000_MWHPR0701MB36743F10343869B23E87F0C1A7899MWHPR0701MB3674_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi everyone-
I had a thought that it would be interesting to see if the AIX build cou=
ld be set up to work with either GCC or XLC, whereas currently it's pretty =
hard-coded around XLC. Furthermore, builds with GCC don't work as extra th=
ings have to be done when building the kernel extension.
However, not being intimately familiar with the build system, would anyo=
ne have a suggestion as to where to start? I'm looking at src/cf/sysname.m=
4 and see that based on the sysname value selected there, certain compiler =
selections and options get defined in src/cf/osconf.m4. However, we probab=
ly don't want to define sysnames like rs_aix72_gcc and rs_aix72_xlc. Would=
it be best to add more complex logic to osconf.m4 to detect xlc or gcc and=
set the variables there accordingly, or would there be a more appropriate =
place?
Thank you!
-Ben
--_000_MWHPR0701MB36743F10343869B23E87F0C1A7899MWHPR0701MB3674_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
Hi everyone-</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
I had a thought that it would be interesting to see if the AIX=
build could be set up to work with either GCC or XLC, whereas currently it=
's pretty hard-coded around XLC. Furthermore, builds with GCC don't w=
ork as extra things have to be done when building
the kernel extension.</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
However, not being intimately familiar with the build sys=
tem, would anyone have a suggestion as to where to start? I'm looking=
at src/cf/sysname.m4 and see that based on the sysname value selected ther=
e, certain compiler selections and options get defined
in src/cf/osconf.m4. However, we probably don't want to define sysna=
mes like rs_aix72_gcc and rs_aix72_xlc. Would it be best to add more =
complex logic to osconf.m4 to detect xlc or gcc and set the variables there=
accordingly, or would there be a more appropriate
place?</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
Thank you!<br>
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
-Ben</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class=
=3D"elementToProof">
<br>
</div>
</body>
</html>
--_000_MWHPR0701MB36743F10343869B23E87F0C1A7899MWHPR0701MB3674_--