From: "Frank Ch. Eigler" <fche@redhat.com>
To: suleman <sulemankm@gmail.com>
Cc: sid@sourceware.org
Subject: Re: could not build tksm in sid snapshot 20070801
Date: Tue, 14 Aug 2007 11:05:00 -0000 [thread overview]
Message-ID: <20070814110520.GA31682@redhat.com> (raw)
In-Reply-To: <1187088754.15332.4.camel@skmhome>
Hi -
> [...] the tksm component did not build during the configure
> process. In fact the configure script didn't create a makefile in
> the sid/src/sid/component/tcl folder at all.
It should have at least created a Makefile, even if tcl development
headers/libraries are absent. You can try running the tcl-component
configure script again (a sibling of cgen-cpu/configure*) to see
what happened.
- FChE
next prev parent reply other threads:[~2007-08-14 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 10:57 suleman
2007-08-14 11:05 ` Frank Ch. Eigler [this message]
2007-08-16 1:51 ` suleman
2007-08-16 2:04 ` Frank Ch. Eigler
2007-08-16 13:47 ` suleman
2007-08-15 13:06 suleman
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=20070814110520.GA31682@redhat.com \
--to=fche@redhat.com \
--cc=sid@sourceware.org \
--cc=sulemankm@gmail.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).