public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: gcc-gnats@gcc.gnu.org Cc: Bryce McKinlay <bryce@waitaki.otago.ac.nz> Subject: libgcj/5064: java/lang/natClassLoader.cc doesn't compile on systems without snprintf Date: Mon, 10 Dec 2001 15:46:00 -0000 [thread overview] Message-ID: <200112102334.AAA12352@korsakov.TechFak.Uni-Bielefeld.DE> (raw) >Number: 5064 >Category: libgcj >Synopsis: java/lang/natClassLoader.cc doesn't compile on systems without snprintf >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Dec 10 15:46:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Rainer Orth >Release: 3.1 20011210 (experimental) >Organization: >Environment: System: OSF1 korsakov V4.0 1229 alpha Machine: alpha host: alphaev67-dec-osf4.0f build: alphaev67-dec-osf4.0f target: alphaev67-dec-osf4.0f configured with: /vol/gnu/src/gcc/gcc-dist/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls --enable-libgcj alphaev67-dec-osf4.0f >Description: libgcj fails to compile on this target: /vol/gnu/src/gcc/gcc-dist/libjava/java/lang/natClassLoader.cc: In function `void _Jv_RegisterClassHookDefault(java::lang::Class*)': /vol/gnu/src/gcc/gcc-dist/libjava/java/lang/natClassLoader.cc:468: `snprintf' undeclared (first use this function) /vol/gnu/src/gcc/gcc-dist/libjava/java/lang/natClassLoader.cc:468: (Each undeclared identifier is reported only once for each function it appears in.) Tru64 UNIX V4.0 (as well as e.g. IRIX 6.2 and Solaris 2.5.1) lacks snprintf in libc. libgcj should still be usable on such platforms. >How-To-Repeat: Bootstrap gcc with --enable-libgcj. >Fix: Use sprintf with a format (like %.170s or some such) to avoid buffer overflows. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-12-10 23:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-10 15:46 Rainer Orth [this message] 2001-12-10 19:55 tromey 2001-12-10 20:06 tromey
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=200112102334.AAA12352@korsakov.TechFak.Uni-Bielefeld.DE \ --to=ro@techfak.uni-bielefeld.de \ --cc=bryce@waitaki.otago.ac.nz \ --cc=gcc-gnats@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).