dejagnu

dejagnu

[Alex Buell]

dejagnu-20010126 fails the tcl tests on sparc32-linux. Is there a newer
version out there?

-- 
Alex.
Signature carefully reformulated to suit demon.loco.
http://www.tahallah.demon.co.uk

RE: dejagnu

[bobbymcn2002]

Should be. Check a sourceware mirror.

-----Original Message-----
From: gcc-owner@gcc.gnu.org [ mailto:gcc-owner@gcc.gnu.org]On Behalf Of
Alex Buell
Sent: Thursday, June 14, 2001 3:44 PM
To: Mailing List - GCC
Subject: dejagnu


dejagnu-20010126 fails the tcl tests on sparc32-linux. Is there a newer
version out there?

-- 
Alex.
Signature carefully reformulated to suit demon.loco.
http://www.tahallah.demon.co.uk


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: dejagnu

[Alexandre Oliva]

On Jun 14, 2001, Alex Buell <alex.buell@tahallah.demon.co.uk> wrote:

> dejagnu-20010126 fails the tcl tests on sparc32-linux. Is there a newer
> version out there?

Shouldn't this be asked in a dejagnu or tcl mailing list? :-)

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

Re: dejagnu

[Alex Buell]

On 14 Jun 2001, Alexandre Oliva wrote:

> Shouldn't this be asked in a dejagnu or tcl mailing list? :-)

Sorry, guys. Anyway I've found dejagnu-1.4.0 and it seems to pass all its
tests so am using it, now to get GCC 3.0 build underway on sparc32.

-- 
Alex.
Signature carefully reformulated to suit demon.loco.
http://www.tahallah.demon.co.uk

Dejagnu

[kwall]

Hello, list,

Is there any reason I should prefer Dejagnu a la
ftp://sources.redhat.com:/pub/gcc/infrastructure/dejagnu-20010126.tar.gz
to ftp://sources.redhat.com/pub/dejagnu/dejagnu-20000518.tar.bz2 or 
ftp://ftp.gnu.org/gnu/dejagnu-1.4.3.tar.gz on the GNU mothership?
I'd like to start tracking down XFAILs...  

Thanks,

Kurt
-- 
Senate, n.:
	A body of elderly gentlemen charged with high duties and
misdemeanors.
		-- Ambrose Bierce

Re: Dejagnu

[Mike Stump]

On Thursday, December 5, 2002, at 06:13 PM, kwall@kurtwerks.com wrote:
> Is there any reason I should prefer Dejagnu a la
> ftp://sources.redhat.com:/pub/gcc/infrastructure/dejagnu- 
> 20010126.tar.gz
> to ftp://sources.redhat.com/pub/dejagnu/dejagnu-20000518.tar.bz2 or
> ftp://ftp.gnu.org/gnu/dejagnu-1.4.3.tar.gz on the GNU mothership?
> I'd like to start tracking down XFAILs...

1.4.0 should be ok, 1.4.1 I'd avoid.  I'd expect 1.4.3 to be fine.  The  
others, I'd just avoid at this point in general, though, they did work  
best before there was a 1.4.

Re: Dejagnu

[kwall]

On Fri, Dec 06, 2002 at 10:39:53AM -0800, Mike Stump wrote:
> On Thursday, December 5, 2002, at 06:13 PM, kwall@kurtwerks.com wrote:

[Dejagnu conundrum elided]

> 1.4.0 should be ok, 1.4.1 I'd avoid.  I'd expect 1.4.3 to be fine.  The  
> others, I'd just avoid at this point in general, though, they did work  
> best before there was a 1.4.

Thanks, Mike. I ended up using 1.4.3 for no other reason than that
it was the latest 'n' greatest.

Kurt
-- 
Reisner's Rule of Conceptual Inertia:
	If you think big enough, you'll never have to do it.

DejaGnu

[Gerald Pfeifer]

I am currently revamping the documentation of the GCC testsuites a bit and
realized that dejagnu-1.3.tar.gz has been released on February 15th, 1996,
which is close to five (sic!) years ago.

Because of that we have to recommend (and provide) snapshots of DejaGnu.

This is hardly acceptable, especially long term.

So, what can we do? A simple first step would be making the latest
snapshot a release and putting it on the GNU FTP servers. (In fact
it seems that Debian, for example, is already using that snapshot.)

Also, the GNU project should try to find an active maintainer for DejaGnu.

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

Re: DejaGnu

[Richard Stallman]

I will talk with the maintainer and take steps one way or another
to get things moving.

dejagnu

['David Scott Urban]

Although this is not directly related to gcc, I wasn't sure where to ask questions about this app.

The sourceware archives contain a directory for dejagnu but they have not been 
updated in a long time. 

Is there a newsgroup or mailing list associated with dejagnu? Who is the current 
maintainer, if any? Is there a homepage on the web or a place on the web to get 
the current version?

The reason I am asking is that I would like to update dejagnu to use the latest 
expect and tcl. But, I am running into problems with the testing on a HP running 
HP-UX 10.20. Also, I am having problems compiling on a Solaris box running 2.5.1 
or 2.6 with the call to setpgrp.

Thanks for you time and any help you can give me.

Scott Urban


D. S. Urban   
email : urban@ast.lmco.com
-------------------------------------------------------------------------------
To be the person, you must know the person. To know the person, you must
understand the person. To understand the person, you must listen. To listen,
you must open your mind and put aside all preconceived ideas and notions.
-------------------------------------------------------------------------------
All opinions expressed are my own not that of my employer.

Dejagnu

[Mark Mitchell]

Is there an easy way to teach dejagnu that some warnings are OK?  On
mips-sgi-irix6.4 every test that involves linking fails with something
like this:

  output is:
  ld32: WARNING 84: /pooma/mitchell/egcs/objdir/libraries//libstdc++/libstdc++.a \
  is not used for resolving any symbol.
  ld32: WARNING 84: /usr/lib32/libm.so is not used for resolving any symbol.
  FAIL: g++.brendan/code-gen1.C (test for excess errors)
  ld32: WARNING 84: /pooma/mitchell/egcs/objdir/libraries//libstdc++/libstdc++.a \
  is not used for resolving any symbol.
  ld32: WARNING 84: /usr/lib32/libm.so is not used for resolving any symbol.

The ever-so-helpful SGI linker wants to tell us this all the time, but
this causes many, many test failures.  I'm sure I can figure this out,
but if anyone knows the answer off-hand, I'd appreciate it.
 
Thanks,

-- 
Mark Mitchell <mmitchell@usa.net>
http://home.earthlink.net/~mbmitchell
Consulting Services Available

Re: Dejagnu

[Ian Lance Taylor]

   Date: Thu, 26 Mar 1998 21:56:35 -0800
   From: Mark Mitchell <mmitchell@usa.net>

   Is there an easy way to teach dejagnu that some warnings are OK?

See prune_warnings in dejagnu/lib/target.exp.  I don't actually know
that it is used for the egcs testsuite, but it may be, and it's the
right place to change anyhow.

Ian

Re: Dejagnu

[Lee Iverson]

In message < 199803281941.OAA14915@subrogation.cygnus.com > you write:
>    Date: Thu, 26 Mar 1998 21:56:35 -0800
>    From: Mark Mitchell <mmitchell@usa.net>
> 
>    Is there an easy way to teach dejagnu that some warnings are OK?
> 
> See prune_warnings in dejagnu/lib/target.exp.  I don't actually know
> that it is used for the egcs testsuite, but it may be, and it's the
> right place to change anyhow.

I already sent this patch in to the dejagnu maintainers:

*** dejagnu/lib/target.exp.~1~	Sun Nov 30 18:07:59 1997
--- dejagnu/lib/target.exp	Thu Mar 26 15:57:33 1998
*************** proc prune_warnings { text } {
*** 184,189 ****
  
      # Or the IRIX 6 ones.
!     regsub -all "(^|\n)(ld: WARNING \[^\n\]*\n?)+" $text "\\1" text
!     regsub -all "(^|\n)(ld: Giving up.*Use -wall\[^\n\]*\n?)+" $text "\\1" text
  
      # It might be tempting to get carried away and delete blank lines, etc.
--- 184,189 ----
  
      # Or the IRIX 6 ones.
!     regsub -all "(^|\n)(ld(|32|64): WARNING \[^\n\]*\n?)+" $text "\\1" text
!     regsub -all "(^|\n)(ld(|32|64): Giving up.*Use -wall\[^\n\]*\n?)+" $text "\\1" text
  
      # It might be tempting to get carried away and delete blank lines, etc.

-------------------------------------------------------------------------------
Lee Iverson     		SRI International
leei@ai.sri.com			333 Ravenswood Ave., Menlo Park CA 94025
http://www.ai.sri.com/~leei/	(650) 859-3307

Re: Dejagnu

[Jim Wilson]

	I already sent this patch in to the dejagnu maintainers:

I made sure it got installed.  It was already half there as of two days ago,
and I added in the other half.

Jim

Re: Dejagnu

[Jeffrey A Law]

  In message < 199803270556.VAA00740@mail.earthlink.net >you write:
  > 
  > Is there an easy way to teach dejagnu that some warnings are OK?  On
  > mips-sgi-irix6.4 every test that involves linking fails with something
  > like this:
Somewhere there's a "prune_system_crud" or similarly named funtion;
it's part of dejagnu if I remember correct 9as opposed to something
in the gcc/g++ testsuites).

jeff

Re: Dejagnu

[Jim Wilson]

	 On mips-sgi-irix6.4 every test that involves linking fails with something
	like this:

	  ld32: WARNING 84: /pooma/mitchell/egcs/objdir/libraries//libstdc++/libstdc++.a \
	  is not used for resolving any symbol.

We could also try to fix this by telling the linker to shut up.  This can be
done by putting a -dont_warn_unused option before the -lstdc++ and a 
-warn_unused afterwards.  This requires having the cp/g++spec.c file emit
target dependent options though, and we currently have no support for this.

Jim