public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: dhlii@dlasys..net To: insight-gnats@sources.redhat.com Subject: insight/324: Build problems on OpenBSD Date: Mon, 26 Nov 2007 10:43:00 -0000 [thread overview] Message-ID: <20071126103837.18995.qmail@sourceware.org> (raw) >Number: 324 >Category: insight >Synopsis: Build problems on OpenBSD >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Nov 26 10:43:01 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Dave Lynch >Release: 6.7.1 >Organization: >Environment: OpenBSD 4.2 >Description: would not build as downloaded. >How-To-Repeat: >Fix: 1) add --disable-nls to ./configure 2). delete "const" from bfd/elf32-i386.c:1174 gcc claims is duplicate >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2007-11-26 10:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-26 10:43 dhlii [this message] 2008-02-21 0:48 kseitz
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=20071126103837.18995.qmail@sourceware.org \ --to=dhlii@dlasys..net \ --cc=insight-gnats@sources.redhat.com \ /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).