linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Tobler <toa@pop.agri.ch>
To: ian reinhart geiser <geiseri@msoe.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problems Compileing PVM
Date: Sun, 07 May 2000 11:05:18 +0200	[thread overview]
Message-ID: <391531CD.E9097B47@pop.agri.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10005061706360.6831-100000@sleepchamber.apt5.msoe.edu


ian reinhart geiser wrote:
>
> Greetings,
>         I have a problem with compileing PVMd
>         on my LinuxPPC 1999 dist.
>
>         When i try to build anything liked off of the
>         PVM libs i get the following errors:
>
>         ../../lib/LINUXPPC/libpvm3.a(lpvmpack.o): In function
> `pvm_vpackf': lpvmpack.o(.text+0x53e8): undefined reference to
> `__va_arg_type_violation'
>         lpvmpack.o(.text+0x53e8): relocation truncated
> to fit: R_PPC_REL24 __va_arg_type_violation
>         lpvmpack.o(.text+0x54f4):
> undefined reference to `__va_arg_type_violation'
>         lpvmpack.o(.text+0x54f4): relocation truncated to fit: R_PPC_REL24
> __va_arg_type_violation
>
>         It looks like a linker error...
>         i have never had this error before on any
>         of my other systems(ARM, ALPHA and INTEL).
>
>         has anyone seen this?  or am i looking in the
>         wrong list?

Have a look in the function pvm_vpackf. I suppose there is something
like this:

va_arg(xyz,int) and in your case I suppose the int isn't int, it's
something else?!

e.g. when you have this va_arg(xyz,char), this would give the error
described above. You can only get the function as wanted when you do
(char)va_arg(xyz,int).

For further details search the dev-list.

Andreas

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-07  9:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-06 22:14 Problems Compileing PVM ian reinhart geiser
2000-05-07  9:05 ` Andreas Tobler [this message]
2000-05-07 14:37 ` Michael Schmitz
2000-05-07 18:28   ` Kevin Hendricks
2000-05-08  9:35     ` Michael Schmitz
2000-05-08 12:56       ` Hendricks, Kevin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=391531CD.E9097B47@pop.agri.ch \
    --to=toa@pop.agri.ch \
    --cc=geiseri@msoe.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).