public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "J. Kean Johnston" <jkj@sco.com>
To: EGCS Mailing List <egcs@cygnus.com>
Subject: DejaGnu nightmares
Date: Fri, 05 Dec 1997 16:52:00 -0000	[thread overview]
Message-ID: <19971205163714.39931@sco.com> (raw)

Ok. I formally give up on DejaGnu. Great idea but I like my hair too much to
tear it all out any more. Ignore Robert Lipe's COFF results for EGCS, and
mine. DejaGnu still lies like a cheap rug. I have tried everything I can
think of to get it to handle multilibs on OSR5 properly, to no avail. It
will pass some options down tot eh compiler, but not to libio or libstdc++.
Sometimes it gets -I and -L flags right, sometimes not. I have found a few
inconsistancies in libgloss.exp (when I am more sure about my hacks I may
post a patch for people to peruse) and I now have DejaGnu passing correct
-I and -L flags for libio and libstdc++. But it will take the devil's own
luck to get the damn thing to pass -mcoff or -melf when I want it to.

I have tried running with "--tool_opts=-mcoff", with CC="gcc -mcoff",
CXX="gcc -mcoff", event --target_board="unix{-mcoff,-melf}", and none
of them pass any flags on down to libio. So all libio and libstdc++
tests have been failing (and succeeding in some cases) with the incorrect
versions of the library.

Doing a make install before running the tests only partially improves the
problem. At least it doesnt get the wrong header files now.

So ... can some DejaGnu expert PLEASE tell me how we can make sure that the
libio, libstdc++ and other non-gcc tests get passed the compiler flags
specified, and how to guarantee that library and include paths are correctly
calculated?

Kean.

             reply	other threads:[~1997-12-05 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-05 16:52 J. Kean Johnston [this message]
1997-12-07  9:55 ` Jeffrey A Law

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=19971205163714.39931@sco.com \
    --to=jkj@sco.com \
    --cc=egcs@cygnus.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).