[OpenAFS] linking afs.ext.64 on AIX fails with missing symbol
vprintf
Ben Huntsman
ben@huntsmans.net
Sat, 13 Aug 2022 20:04:21 +0000
--_000_MWHPR0701MB367479A7FE82383960E639EFA7669MWHPR0701MB3674_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Just to tie off, yes, reverting that change worked. Other problems down th=
e line, but I will continue in the openafs-devel list.
Thank you.
-Ben
________________________________
From: Jeffrey E Altman
Sent: Saturday, August 13, 2022 10:25 AM
To: Ben Huntsman; openafs-info@openafs.org
Subject: Re: [OpenAFS] linking afs.ext.64 on AIX fails with missing symbol =
vprintf
On 8/13/2022 12:20 PM, Ben Huntsman (ben@huntsmans.net<mailto:ben@huntsmans=
.net>) wrote:
Ah, yes, that is what I thought. The problem is that AIX's kernel doesn't =
have vprintf. Only printf. However, the change set you linked indicates t=
hat previously, osi_Msg used fprintf, and indeed that goes all the way back=
to the beginning. That's why I wonder how it worked on AIX in the past. =
With no vprintf in the kernel, what alternative should we use here?
The prior change had osi_Msg as a macro not a function. That means that th=
e fprintf reference would have been substituted for wherever osi_Msg was us=
ed. Assuming that osi_Msg was defined for AIX at all.
The referenced change was intended to fix a problem specific to Linux. You=
might want to revert the change and see whether or not you make further pr=
ogress.
As an aside, development discussions such as this are not of general intere=
st to the end user community and are more appropriate to be held on openafs=
-devel@openafs.org<mailto:openafs-devel@openafs.org> instead.
--_000_MWHPR0701MB367479A7FE82383960E639EFA7669MWHPR0701MB3674_
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);" class=3D"elementToProof">
Just to tie off, yes, reverting that change worked. Other problems do=
wn the line, but I will continue in the openafs-devel list.</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);" class=3D"elementToProof">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);" class=3D"elementToProof">
Thank you.</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);" class=3D"elementToProof">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);" class=3D"elementToProof">
-Ben</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);" class=3D"elementToProof">
<br>
</div>
<div>
<div><br>
</div>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12p=
t; color:rgb(0,0,0);">
<br>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%;">
<b>From:</b> Jeffrey E Altman<br>
<b>Sent:</b> Saturday, August 13, 2022 10:25 AM<br>
<b>To:</b> Ben Huntsman; openafs-info@openafs.org<br>
<b>Subject:</b> Re: [OpenAFS] linking afs.ext.64 on AIX fails with missing =
symbol vprintf
<div><br>
</div>
</div>
<div class=3D"rps_2a2f">
<div>
<div class=3D"x_moz-cite-prefix">On 8/13/2022 12:20 PM, Ben Huntsman (<a hr=
ef=3D"mailto:ben@huntsmans.net" target=3D"_blank" rel=3D"noopener noreferre=
r" data-auth=3D"NotApplicable" class=3D"x_moz-txt-link-abbreviated">ben@hun=
tsmans.net</a>) wrote:<br>
</div>
<blockquote type=3D"cite">
<div class=3D"x_elementToProof" style=3D"font-family:Calibri,Arial,Helvetic=
a,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Ah, yes, that is what I thought. The problem is that AIX's kernel doe=
sn't have vprintf. Only printf. However, the change set you lin=
ked indicates that previously, osi_Msg used fprintf, and indeed that goes a=
ll the way back to the beginning. That's why I
wonder how it worked on AIX in the past. With no vprintf in the kern=
el, what alternative should we use here?</div>
<br>
</blockquote>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">The prior change had osi_=
Msg as a macro not a function. That means that the fprintf reference =
would have been substituted for wherever osi_Msg was used. Assuming t=
hat osi_Msg was defined for AIX at all.</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">The referenced change was=
intended to fix a problem specific to Linux. You might want to rever=
t the change and see whether or not you make further progress.</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;">As an aside, development =
discussions such as this are not of general interest to the end user commun=
ity and are more appropriate to be held on
<a href=3D"mailto:openafs-devel@openafs.org" target=3D"_blank" rel=3D"noope=
ner noreferrer" data-auth=3D"NotApplicable" class=3D"x_moz-txt-link-abbrevi=
ated">
openafs-devel@openafs.org</a> instead.</p>
<p style=3D"margin-top: 0px; margin-bottom: 0px;"><br>
</p>
</div>
</div>
</div>
</body>
</html>
--_000_MWHPR0701MB367479A7FE82383960E639EFA7669MWHPR0701MB3674_--