public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>,
	crossgcc@sourceware.org
Subject: crosstool_ng configure bug
Date: Fri, 11 Nov 2011 22:05:00 -0000	[thread overview]
Message-ID: <CAHrUA34+V3TxnOaaQ-zL+kLDrugY+=7n5AAOOusa-jFZ-Kt-QQ@mail.gmail.com> (raw)

Hi,

Just downloaded crosstool_ng, and hit a trite bug:

tar -jxvf crosstool-ng-1.13.0.tar.bz2
cd crosstool-ng-1.13.0
mkdir build
cd build
../configure --prefix=/my/path

and I get:

... etc
Checking for 'libncursesw.a'... no
Checking for 'libncurses.so'... yes

Computing version string...
Building up Makefile... /bin/sed: can't read Makefile.in: No such file
or directory
done


I habitually use a build dir distinct from the source dir to avoid
polluting the source tree with .o files; handy when disk-space is low,
when preparing patches for people, when using git, when copying files
around, and other reasons too. And disk space is always low ... so I
was slightly disappointed when configure broke by not finding
Makefile.in

Another minor remark: If/when I have to hack on a tool, such as
crosstool_ng, I use quilt, with automaticallly uses a directory called
"patches". So it was a surprise to see that such a directory already
exists in crosstool_ng. Hmmm.

--linas

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2011-11-11 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 22:05 Linas Vepstas [this message]
2011-11-12 11:39 ` Yann E. MORIN

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='CAHrUA34+V3TxnOaaQ-zL+kLDrugY+=7n5AAOOusa-jFZ-Kt-QQ@mail.gmail.com' \
    --to=linasvepstas@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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).