From: schinder@pobox•com
To: Kevin Hendricks <khendricks@ivey•uwo.ca>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: What's up with gcc 2.95.1 and "__va_arg_type_violation"
Date: Fri, 8 Oct 1999 09:30:25 -0400 [thread overview]
Message-ID: <19991008093025.A3784@pobox.com> (raw)
In-Reply-To: <99100721144003.26148@localhost.localdomain>
On Thu, Oct 07, 1999 at 09:08:16PM -0400, Kevin Hendricks wrote:
}
} Hi,
}
} When attempting to run the latest build of the jdk, I get the following error
} message (but only on non-debug builds).
}
} Unsatisfied Link error: __va_arg_type_violation
If you turn off the optimizer, it will stop complaining. I ran into this
building xemacs.
}
} Figuring, I simply forgot some new piece of glibc 2.1.2, I used
}
} nm -o `find /lib -name "*"` | grep va_arg_type
}
} (for /lib, /usr/lib, /usr/local/lib, /opt/lib, etc)
}
} and this damn routine simply does not exist on my machine.
}
} Any ideas of where one might look to fulfill this thing. This is new with
} gcc-2.95.1 and/or glibc 2.1.2
}
}
} By the way, native threads still do not work with the very latest glibc 2.1.2
} because of the new semaphore functions. If I force linking to the old
} semaphore functions, everything starts working again.
}
} I am building a debug glibc 2.1.2 and I will try to find the source of the
} problem.
Take a look at /usr/lib/ppc-redhat-linux/2.95.1/include/va-ppc.h.
It's in there. I don't know why; I suspect it's part of an upcoming
fix of varargs. The egcs that comes with Yellow Dog (and I assume
LinuxPPC) doesn't have this problem.
}
} Any ideas here would be greatly appreciated.
}
} Thanks,
}
} Kevin
}
--
Paul Schinder
schinder@pobox•com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-08 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-08 1:08 What's up with gcc 2.95.1 and "__va_arg_type_violation" Kevin Hendricks
1999-10-08 13:30 ` schinder [this message]
1999-10-12 3:54 ` Troy Benjegerdes
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=19991008093025.A3784@pobox.com \
--to=schinder@pobox$(echo .)com \
--cc=khendricks@ivey$(echo .)uwo.ca \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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