public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dcnltc at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug documentation/4326] New: make all fails if '.' on execution path
Date: Thu, 05 Apr 2007 23:41:00 -0000	[thread overview]
Message-ID: <20070406004131.4326.dcnltc@us.ibm.com> (raw)

I discovered while trying to install systemtap from one of the snapshots on the
web site, that the 'make all' fails if you have '.' on your execution path
because when the build gets into: src/build-elfutils/src, it builds an
executable called 'ld'.  On subsequent attempts to link other tools this ld
get's invoked and it apparently doesn't recognize the same switches as the host ld.

There isn't really a component to report this sort of bug so I just chose
documentation because the installation instructions don't say: "don't have . on
your path.

-- 
           Summary: make all fails if '.' on execution path
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: documentation
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: dcnltc at us dot ibm dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=4326

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2007-04-05 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 23:41 dcnltc at us dot ibm dot com [this message]
2007-04-05 23:52 ` [Bug documentation/4326] " fche at redhat dot com
2007-04-06 19:09 ` dcnltc at us dot ibm dot com
2007-04-06 20:01 ` fche 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=20070406004131.4326.dcnltc@us.ibm.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@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).