From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, Ben Elliston <bje@au.ibm.com>
Subject: [aimingoff@mba.nifty.com: build/2446: Architecture depend file under gdb/libdecnumber]
Date: Thu, 17 Apr 2008 02:45:00 -0000 [thread overview]
Message-ID: <20080416230010.GB3853@caradoc.them.org> (raw)
Ben, any comments? I suspect this is because "make distclean"
doesn't delete it; see the top level src-release file if you're not
familiar with how gdb snapshots and releases get built.
----- Forwarded message from aimingoff@mba.nifty.com -----
Date: 14 Apr 2008 03:31:33 -0000
From: aimingoff@mba.nifty.com
Subject: build/2446: Architecture depend file under gdb/libdecnumber
To: gdb-gnats@sources.redhat.com
Reply-To: aimingoff@mba.nifty.com
>Number: 2446
>Category: build
>Synopsis: Architecture depend file under gdb/libdecnumber
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: mistaken
>Submitter-Id: net
>Arrival-Date: Mon Apr 14 03:38:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: aimingoff@mba.nifty.com
>Release: gdb-6.8
>Organization:
>Environment:
>Description:
There is architecture depend file gdb/libdecnumber/gstdint.h in distributed archive. This file is automatically generated while building, however, the original file is still referred if the make procedure is done under 'build' directory. The building will fail if the machine doesn't have "stdint.h".
>How-To-Repeat:
mkdir build
cd build
../configure
make
>Fix:
Remove "gdb/libdecnumber/gstdint.h" from distributed archive.
>Release-Note:
>Audit-Trail:
>Unformatted:
----- End forwarded message -----
--
Daniel Jacobowitz
CodeSourcery
next reply other threads:[~2008-04-16 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 2:45 Daniel Jacobowitz [this message]
2008-04-18 19:54 ` Ben Elliston
2008-04-21 16:53 ` Daniel Jacobowitz
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=20080416230010.GB3853@caradoc.them.org \
--to=drow@false.org \
--cc=bje@au.ibm.com \
--cc=gdb@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