[OpenAFS-devel] Re: OpenAFS-1.5.24/NetBSD-3.1/amd64 compile problem
Derrick Brashear
shadow@gmail.com
Mon, 17 Sep 2007 23:14:54 -0400
------=_Part_1041_9861627.1190085294099
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 9/4/07, Suzanna <sue@real.wilbury.sk> wrote:
>
> > Why the 1.5 branch? It doesn't look like amd64 support was merged.
>
> Trying to be up to date. I wasn't aware of the missing amd64 code.
1.5 isn't the recommended unix release, anyway, so "up to date" if you want
bleeding is the CVS head and not 1.5 anyway.
> Are you using process.amd64.s? What happens when you add -fPIC to
> > the compile options?
>
> I am. Adding -fPIC doesn't change anything as it is not passed to
> as(1). Apparently, as(1) has no options to force the creation of
> PIC compatible code. Adding it to cc -E before doesn't change
> anything, either.
>
> The error occurs when pam_afs.so.1 is linked... I was wondering about
> linking a lib.a into a lib.so, anyway.
It's doable if your dynamic linker supports it, but most amd64 linkers
don't.
_______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>
------=_Part_1041_9861627.1190085294099
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div><span class="gmail_quote">On 9/4/07, <b class="gmail_sendername">Suzanna</b> <<a href="mailto:sue@real.wilbury.sk">sue@real.wilbury.sk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Why the 1.5 branch? It doesn't look like amd64 support was merged.<br><br>Trying to be up to date. I wasn't aware of the missing amd64 code.</blockquote><div><br>1.5 isn't the recommended unix release, anyway, so "up to date" if you want bleeding is the CVS head and not
1.5 anyway.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Are you using process.amd64.s? What happens when you add -fPIC to
<br>> the compile options?<br><br>I am. Adding -fPIC doesn't change anything as it is not passed to<br>as(1). Apparently, as(1) has no options to force the creation of<br>PIC compatible code. Adding it to cc -E before doesn't change
<br>anything, either.<br><br>The error occurs when pam_afs.so.1 is linked... I was wondering about<br>linking a lib.a into a lib.so, anyway.</blockquote><div><br>It's doable if your dynamic linker supports it, but most amd64 linkers don't.
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">_______________________________________________<br>OpenAFS-devel mailing list
<br><a href="mailto:OpenAFS-devel@openafs.org">OpenAFS-devel@openafs.org</a><br><a href="https://lists.openafs.org/mailman/listinfo/openafs-devel">https://lists.openafs.org/mailman/listinfo/openafs-devel</a><br></blockquote>
</div><br>
------=_Part_1041_9861627.1190085294099--