public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug build/14120] New: build process creates autom4te.cache directory in source dir
Date: Fri, 18 May 2012 18:35:00 -0000 [thread overview]
Message-ID: <bug-14120-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14120
Bug #: 14120
Summary: build process creates autom4te.cache directory in
source dir
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: build
AssignedTo: unassigned@sourceware.org
ReportedBy: aj@suse.de
CC: carlos@systemhalted.org
Classification: Unclassified
Running configure always creates a directory autom4te.cache.
We do not support building in the source dir, so let's not touch it by default.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-05-18 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 18:35 aj at suse dot de [this message]
2012-05-19 10:21 ` [Bug build/14120] " allan at archlinux dot org
2012-05-19 12:19 ` schwab@linux-m68k.org
2012-05-21 20:59 ` carlos_odonell at mentor dot com
2012-12-03 23:58 ` carlos at systemhalted dot org
2013-10-02 19:44 ` eblake at redhat dot com
2013-10-03 1:00 ` allan at archlinux dot org
2013-10-03 1:04 ` carlos at redhat dot com
2013-10-11 23:23 ` eblake at redhat dot com
2013-10-11 23:30 ` joseph at codesourcery dot com
2013-10-12 10:27 ` allan at archlinux dot org
2013-10-15 18:44 ` carlos at redhat dot com
2013-10-16 3:49 ` allan at archlinux dot org
2013-12-16 1:32 ` allan at archlinux dot org
2014-06-25 10:57 ` fweimer at redhat dot com
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-14120-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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: 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).