public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/3827] New: Code uses Buid.SRCDIR
Date: Thu, 04 Jan 2007 13:43:00 -0000	[thread overview]
Message-ID: <20070104134324.3827.cagney@redhat.com> (raw)

Installed code is using Build.SRCDIR, and shouldn't.  Instead, assuming it is
test code checking for a src path, it can use Config.getRootSrcDir.

frysk/util/TestFCatch.java:67:                      + Build.SRCDIR
frysk/util/TestFCatch.java:70:                      + Build.SRCDIR
frysk/util/TestFStack.java:83:                        + Build.SRCDIR
frysk/util/TestFStack.java:86:                        + Build.SRCDIR
frysk/util/TestFStack.java:93:                    + Build.SRCDIR +
"/frysk/pkglibdir/funit-child.c#[\\d]+\n"
frysk/gui/DummySourceWindow.java:206:                        Build.SRCDIR + "/"
+ BASE_PATH + GLADE_PKG_PATH,
frysk/gui/DummySourceWindow.java:214:                        "./common",
Build.SRCDIR + "/" + BASE_PATH + "common/",
frysk/gui/DummySourceWindow.java:218:                       
"./srcwin/testfiles", Build.SRCDIR + "/" + BASE_PATH + "srcwin/testfiles",
frysk/gui/DummyDebugResults.java:135:                        Build.SRCDIR + "/"
+ BASE_PATH + GLADE_PKG_PATH,
frysk/gui/DummyDebugResults.java:143:                        "./common",
Build.SRCDIR + "/" + BASE_PATH + "common/",
frysk/gui/DummyDebugResults.java:147:                       
"./srcwin/testfiles", Build.SRCDIR + "/" + BASE_PATH + "srcwin/testfiles",
frysk/gui/test/TestGlade.java:87:                       Build.SRCDIR + "/" +
BASE_PATH + GLADE_PKG_PATH,
frysk/gui/test/TestParser.java:100:                                    
Build.SRCDIR + "/frysk/gui/srcwin/testfiles/test_looper.xml",
frysk/gui/test/TestParser.java:108:    if (DOMFactory.pathFound(Build.SRCDIR))
frysk/gui/FryskGui.java:56:                  Build.SRCDIR + "/" + BASE_PATH +
GLADE_PKG_PATH,
frysk/gui/FryskGui.java:64:                  "./common", Build.SRCDIR + "/" +
BASE_PATH + "common/",
frysk/gui/FryskGui.java:68:                  "./srcwin/testfiles", Build.SRCDIR
+ "/" + BASE_PATH + "srcwin/testfiles",

-- 
           Summary: Code uses Buid.SRCDIR
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: cagney at redhat dot com
OtherBugsDependingO 3694
             nThis:


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

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


             reply	other threads:[~2007-01-04 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 13:43 cagney at redhat dot com [this message]
2007-01-06 12:54 ` [Bug general/3827] Code uses Build.SRCDIR cagney 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=20070104134324.3827.cagney@redhat.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@sourceware.org \
    /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).