linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl@munich.netsurf.de>
To: Maurice DIAMANTINI <diam@pmdiam.ensta.fr>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: bug glibc strlen() or tcl8.2
Date: Fri, 10 Sep 1999 20:19:56 +0200	[thread overview]
Message-ID: <4.2.0.58.19990910201708.00c47c30@mail.lauterbach.com> (raw)
In-Reply-To: <19990910163126.A19797@pmdiam.ensta.fr>


At 16:31 10.09.99 , Maurice DIAMANTINI wrote:

>     Vous disiez:
>     >
>     > >I'm unable to execute tcl8.2 on linuxppc R5. Although it compile and
>     > >and run very simply on intel box, solaris, ... but not on linuxppc
>     > > ...
>     > >The programm compils OK, but get a core dump at the first execution
>     > >of a tcl command (in fact at the "make test")
>     > ...
>     > >     memcpy ((VOID *) &tmpArgList, (VOID *) &argList, sizeof \
>     >                                                (tmpArgList));
>     >       ^^^^^^^^
>     > This is unportable in combination with va_list. Try:
>     >        __va_copy (tmpArgList, argList);
>
>     Danke Franz,
>
>     But when I modify the code (from the true tcl distrib):
>     (I do'nt thes function which aren't part of the tcl distrib.
>
>             // string = va_arg(tmpArgList, char *);
>             string = __va_arg(tmpArgList, argList);

??? I didn't tell you to do that. I meant: Replace the "memcpy" line in the 
source with the "__va_copy" line I sent you.

Franz.


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

      reply	other threads:[~1999-09-10 18:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-09 14:42 bug glibc strlen() or tcl8.2 Maurice DIAMANTINI
1999-09-09 17:35 ` Franz Sirl
1999-09-10 14:31   ` Maurice DIAMANTINI
1999-09-10 18:19     ` Franz Sirl [this message]

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=4.2.0.58.19990910201708.00c47c30@mail.lauterbach.com \
    --to=franz.sirl@munich.netsurf.de \
    --cc=diam@pmdiam.ensta.fr \
    --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).