public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Edward L. Hepler'" <hepler@vlsi-concepts.com>,
		<insight@sources.redhat.com>
Subject: RE: Adding a target?
Date: Tue, 26 Feb 2008 18:13:00 -0000	[thread overview]
Message-ID: <008601c878a3$3d5c2330$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <Pine.GSO.4.62.0802252126560.18140@manx.misty.com>

On 26 February 2008 03:07, Edward L. Hepler wrote:

> P.S.  I'm using insight-6.6  (I downloaded insight-6.7.1, but "configure"
> failed due to syntax errors (lines 11 and 19)...  Haven't had time to
> look into this...).  I'm also running all of this under Cygwin
> on a PC running Windows XP pro...

  You know, looking at the configure script, I /really/ don't think there
should be a syntax error on line 11 ....

/gnu/insight-6.7.1 $ cat -n configure | head -14 | tail -6
     9  ## M4sh Initialization.  ##
    10  ## --------------------- ##
    11
    12  # Be Bourne compatible
    13  if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then
    14    emulate sh


  Heh.  This is a cygwin-specific thing:  Don't use WinZIP or WinRAR or any
other gui application to unpack tarballs, because they mangle the line endings
into windows-style CRLF, which bash doesn't understand.  Use command-line tar
instead:

    "tar xvjf <tarball name>.tar.bz2"

or

    "tar xvzf <tarball name>.tar.gz2"

according to the type.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2008-02-26 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26  3:07 Edward L. Hepler
2008-02-26 18:13 ` Dave Korn [this message]
2008-03-06  3:31   ` Edward L. Hepler
2008-02-29  5:38 ` Keith Seitz
     [not found]   ` <Pine.GSO.4.62.0803081507200.8750@manx.misty.com>
2008-03-09 17:34     ` Edward L. Hepler
2008-03-09 23:49       ` Keith Seitz

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='008601c878a3$3d5c2330$2e08a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=hepler@vlsi-concepts.com \
    --cc=insight@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).