public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/16550] New: bfd/cache.c doesn't compile with gcc -m64 on Solaris
Date: Mon, 10 Feb 2014 14:11:00 -0000	[thread overview]
Message-ID: <bug-16550-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=16550

            Bug ID: 16550
           Summary: bfd/cache.c doesn't compile with gcc -m64 on Solaris
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: ro at CeBiTec dot Uni-Bielefeld.DE
          Reporter: ro at CeBiTec dot Uni-Bielefeld.DE
              Host: *-*-solaris2.*
            Target: *-*-solaris2.*
             Build: *-*-solaris2.*

On current mainline, gdb 7.7 and binutils 2.24 branches, bfd/cache.c doesn't
compile with gcc -m64 on Solaris 8 to 11:

cc1: warnings being treated as errors
/vol/src/gnu/gdb/gdb-7.7/bfd/cache.c: In function 'bfd_cache_max_open':
/vol/src/gnu/gdb/gdb-7.7/bfd/cache.c:85: error: comparison between signed and
unsigned integer expressions

This is a regression from previous releases.

The error is about

      && rlim.rlim_cur != RLIM_INFINITY)

where <sys/resource.h> has

typedef unsigned long   rlim_t;
#define RLIM_INFINITY   (-3l)

  Rainer

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2014-02-10 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 14:11 ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2014-02-10 15:28 ` [Bug build/16550] " cvs-commit at gcc dot gnu.org
2014-02-10 15:44 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-05-05 21:54 ` cvs-commit at gcc dot gnu.org

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=bug-16550-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).