Re: [PATCH] Correct function prototype for REAL_EXIT and REAL__EXIT

On Sat, Jan 25, 2025 at 07:51:44PM -0600, Jacob Bachmeyer wrote: > This also looks like you might actually know what testglue.c actually does > and how it is used.  Could you enlighten me on that or at least point me to > an example of something that uses it?  I am currently reluctant to touch it

Re: [PATCH] Catch errors properly, if whoami or who don't exist

On 9/8/24 6:15 PM, Jacob Bachmeyer wrote: So the logs were not sitting on a shared server, then.  Perhaps a notion of credit-where-credit-is-due to the testers? In those days we were still using UUCP over Telebit Trailblazer modems. :-) The shared server came by years later when we built th

Re: [PATCH] Catch errors properly, if whoami or who don't exist

On 9/6/24 9:54 PM, Jacob Bachmeyer wrote: In the first place I was wondering why at all logname is needed. I can guess the reason for putting the user's login name into the log based on DejaGnu's history:  DejaGnu originated at Cygnus, where the ability to easily look at a log and see who ha

Re: testsuite under wine

For a totally off-topic response, as the primary author of DejaGnu, and currently retired maintainer (thanks Jacob!), it has been so fun to see such great community support from multiple people and the Wine project. For a 31 year old project, it's very encouraging. I am loving the deep techni

Re: Broken links in online HTML manual

On 3/29/22 16:40, Jacob Bachmeyer wrote: Apparently I somehow missed adding the new nodes to the website CVS repository when updating the manual for 1.6.3.  Is there a different command for adding files vs. updating existing files in CVS? Yeah, I had to remember too, it's been awhile since

Re: Broken links in online HTML manual

On 3/29/22 04:13, Jonathan Wakely wrote: All the links for configuration files at https://www.gnu.org/software/dejagnu/manual/index.html give a 404 error: https://www.gnu.org/software/dejagnu/manual/Local-configuration-file.html https://www.gnu.org/software/dejagnu/manual/Global-configuration-fil

Re: WARNING: Couldn't find the global config file.

On 12/3/20 10:05 PM, Jacob Bachmeyer wrote: > My guess is that this was somehow related to the testing labs at Cygnus > long ago, but I will consider this change for 1.7 and will probably do > it if I do not find a reason to keep the warning. Yep. In the beginning, there were tons of problems w

Re: Driving DejaGNU from Linux for testing arm-none-eabi toolchain executed on Windows

On 10/2/20 9:29 AM, Torbjorn SVENSSON wrote: > Is it possible to run DejaGNU on a Linux system for the Windows tests too, > but use scp/ssh, or something similar, to connect to the Windows system to > run the toolchain binaries? Yes, DejaGnu has been able to do this since it was created. The

Re: [PATCH] build_wrapper: Call customization hook

On 9/14/20 6:02 AM, Christophe Lyon wrote: > It can be useful to customize the build wrapper for local needs: for > instance, one may need to compile additional objects to add > initialization code depending on the target board or multilibs in use. That shouldn't be necessary if you're using a s

Re: [PATCH] Add riscv-sim.exp

On 7/20/20 9:11 PM, Kito Cheng wrote: > Oh, thanks for telling me this, it seems like a pretty new file in the > DejaGNU , I'll take a look at this. It's very new, I've been using it due to a lack of target hardware. I even got GDB testing to work for both bare metal and cross linux. On a si

Re: DejaGnu unit testing protocol

On 7/22/20 5:06 PM, David Malcolm wrote: > (I also ran into the issue that dejagnu.h's pass/fail C functions > aren't thread-safe, which I hack around in my testsuite, replacing them > in multi-threaded tests with ones guarded by a mutex). I'll be honest, when I wrote dejagnu.h, I never thought

Re: [PATCH] Add riscv-sim.exp

On 7/21/20 11:02 PM, Kito Cheng wrote: > Remote protocols need a port which means it's harder to parallel > testing in a single machine, > but I guess it could add some mechanism to randomly pick a port to prevent > that. Actually that's supported for the remote protocol, it increments the por

Re: [PATCH] Add riscv-sim.exp

On 7/20/20 9:11 PM, Kito Cheng wrote: >> Do I correctly infer that this patch works with the sim tool shipped with >> GDB? > Tested with GDB simulator and qemu, but we use a tricky way to test > with qemu, add a wrapper to qemu to made the interface same as gdb > simulator[1]. QEMU supports th

Re: [PATCH] Add riscv-sim.exp

On 7/20/20 5:23 PM, Jacob Bachmeyer wrote: >    Do I correctly infer that this patch works with the sim tool shipped > with GDB? That's the default instruction set level simulator, often used when working hardware is unavailable. QEMU does have riscv support, so the new baseboard for generic QE

Re: GDB testsuite overrides default_target_compile and breaks

On 6/19/20 6:57 AM, Tom Tromey wrote: > FWIW this makes sense to me. I think it's never been a great idea to > have this override in gdb. Dejagnu wasn't very actively maintained for > a long time, and had low engagement from gdb developers, so it was more > like a convenient way to move forward.

Re: Ensuring that site.exp no longer overrides command line options

On 6/1/20 9:12 PM, Jacob Bachmeyer wrote: > Obviously, this means that site.exp overriding command line options > needs to be fixed and that window needs to be closed.  I am unsure if > there are any uses for this "misfeature" and therefore how aggressively > the command line parameters should be

patches done

I finished all the patches Jacob added to our savannah patch tracker. I did validate the ones that effected target configuration with my minimal cross testing setup, but would appreciate somebody with a more complex environment could give current 'master' a sanity check. I don't think any of t

cross testing

I got cross testing to my PI working. The GCC execute tests look good, there's problems with the GDB tests I'll need to dig into. Way too many failures, which I'm assuming is unrelated to the GDB tests themselves. :-) Cross GDB tests working after some patches is kindof important, as that's what

Raspberry PI toolchain

I managed to build a cross toolchain from git for the Raspberry PI B3 models, complete with an up-to-data sysroot (Debian Buster). I'll use this to test cross testing changes to real hardware. I'll build this for a few other versions later. It's a big file cause of the large sysroot, but if anyon

toolchain testing

If you use my my fork of ABE from here: https://gitlab.com/rsavoye/abe, here's how I'm running tests with a branch of DejaGnu: ./abe.sh gcc=gcc.git~master --set languages=c,c++,lto,go,fortran --build all --set runtestflags='--xml' --excludecheck glibc --check all --disable update |& tee x E

Re: I volunteer

On 5/18/20 4:36 PM, Jacob Bachmeyer wrote: > What is the minimal set needed for sufficient testing?  (Which > packages?  GCC, GDB, ...?  How many versions?  Latest release/Past three > releases/All supported releases/Something else?  I have/have access to > AMD64 (with 32-bit compatibility availab

Re: I volunteer

On 5/19/20 3:11 AM, Christophe Lyon wrote: > IIRC, that's what ABE does too. Abe lets you specify a branch of all tools to build, including DejaGnu. I do this a few different ways. If the DejaGnu branch is upstream, then just tell ABE to use that. If the branch isn't upstream, you can do what Ch

Re: I volunteer (was: Re: dejagnu version update?)

On 5/18/20 2:16 PM, Jacob Bachmeyer wrote: > My work on DejaGnu is one of my hobbies.  However, DejaGnu is a > relatively stable project, so I do not expect it to require much time. To adequately test DejaGnu, you need to be able to build and test the GNU toolchain, both native and cross. That'

Re: dejagnu version update?

On 5/17/20 1:43 PM, Maciej W. Rozycki wrote: > patch service before. It doesn't appear linked to our mailing list either > and instead you need to go through the hoops of a web interface (and open > an account first) to submit a change. From what I remember, it was decided the GNU toolchain

Re: dejagnu version update?

On 5/16/20 5:45 PM, Maciej W. Rozycki wrote: > Overall perhaps a patch management system might be good having to make > chasing patches easier, such as patchwork, and we already use Git, so we As an old GNU project, we're required to use what the FSF prefers, which is on savannah. https://sav

Re: dejagnu version update?

On 5/15/20 6:22 PM, Mike Stump wrote: > Anyway, love to have software that can move code wholesale. Love to move the > testsuite into a new language. All it needs is funding. :-) What GDB needs is expect, not Tcl. Most of the GDB testsuite is just expect pattern matching from the shell. That'

Re: dejagnu version update?

On 5/14/20 5:34 PM, Maciej W. Rozycki wrote: > And then current development appears ongoing, ferociously indeed, with the > last check in literally today (barring my time zone), as indicated here: > . It's obvious I haven't been paying attention, so muc

Re: dejagnu version update?

On 5/14/20 10:08 AM, David Edelsohn wrote: > Have you approached the Linux Foundation Core Infrastructure > Initiative for funding for both DejaGNU maintenance (patch backlog) > and refactoring DejaGNU in Python efforts? Not that team, the folks I talked to thought I was crazy for wanting to re

Re: dejagnu version update?

On 5/14/20 8:08 AM, Rainer Orth wrote: >> stops responding for whatever reason. I have come up with a solution >> (that I'd be happy to upstream, except that DejaGNU maintenance seems to >> have been dead for like a year now), which I have also confirmed to be >> required with current DejaGNU

Re: dejagnu version update?

On 5/13/20 10:51 AM, Mike Stump wrote: > So, now that ubuntu 20.04 is out and RHEL 8 is out, and they both > contain 6, and SLES has 6 and since we've been sitting at 1.4.4 for > so long, anyone want to not update dejagnu to require 1.6? We do still find and fix bugs occasionally. :-) And 1.4.4

Re: connecting a QEMU VM to dejagnu...

On 10/16/19 5:40 PM, Alan Lehotsky via DejaGnu wrote: > The one example I found via a web search seems to want to do > everything in the virtual machine - but I have to believe that’s > going to be insanely slow… Well, qemu is a virtual machine... Here's the ones I used for GNU toolchain cross

Re: PATCH: Update internal unit tests for changes from 22 years ago

On 5/22/19 8:23 PM, Jacob Bachmeyer wrote: > Why?  The simulators still work, or were the Cygnus simulators never > actually released?  (I have never actually seen them.)  Use m68k QEMU?  > Or is m68k basically a dead arch now that is no longer used? Yes, it's a dead architecture. > Well, then

Re: PATCH: Update internal unit tests for changes from 22 years ago

On 5/21/19 8:38 PM, Jacob Bachmeyer wrote: > While developing tests for default_target_compile, I ran into several > strange problems that I eventually tracked down to an empty board_info > array.  Apparently, when the target configuration was moved into the > board_info array 22 years ago, the Dej

Re: "tool-and-target-specific" configuration files

On 1/22/19 4:25 AM, Ben Elliston wrote: > On Mon, Jan 21, 2019 at 09:32:34PM -0600, Jacob Bachmeyer wrote: > >> Or should I shelve documenting the expected structure of a testsuite >> and untangle the board/target description rat's nest first, >> documenting the description of a testing lab under

Re: PATCH: add dejagnu(1) multi-launcher

On 12/18/18 5:58 PM, Ben Elliston wrote: > > Sometimes it is true that things are the way they are for a reason, > but some of those reasons are now 25 years old. I really don't mind > the idea that the next version of DejaGnu might not run on Ultrix. :) The original spec in those days was it ha

Re: testsuite/lib/libsup.exp appears to be an interesting fossil

On 12/11/18 7:59 PM, Jacob Bachmeyer wrote: > Is there a known reason that this approach (an interactive Expect > subprocess) is not used, or was there simply not time to pursue it in > early 1996? In 1996, when that file was written, nobody was using the unit test API at all. Later on, that d

Re: PATCH: clean up whitespace in manual

are procs that are only to be used internally and should probably be avoided in a normal testsuite. > Also, after what threshold of adding/reorganizing/etc. the manual do we > have to change the cover page to list "Rob Savoye, et al" and "Cygnus > Support and the GNU Project&qu

Re: PATCH: simplify regular expressions

On 12/11/18 2:55 AM, Ben Elliston wrote: > On Mon, Dec 10, 2018 at 04:30:49PM -0600, Jacob Bachmeyer wrote: > >> GDB has changed somewhat over the years; are the strings those >> modules seek still valid or do we need to accept both "old" and >> "new" message sets? Should DejaGnu eventually suppo

Re: PATCH: fix syntax error in lib/tip.exp

On 12/7/18 2:22 PM, Ben Elliston wrote: > I have been running the ttclchecker syntax checker over the DejaGnu > sources and slowly fixing problems it identifies. Here's a patch for > the first one: I'm not sure anyone still uses tip for serial communications. :-) - rob - signature.a

Re: PATCH: remove redundant methods in dejagnu.h

On 12/3/18 4:56 PM, Jacob Bachmeyer wrote: > What revision of C++ added those runtime type conversions?  Is it > plausible that any projects out there might be using an older C++ > version?  Could there be a compiler out there that does not do those > conversions on function calls even though it s

Re: isremote and unix board special handling question

On 11/29/18 12:35 AM, Brooks Moses wrote: > Fair enough -- but having done cross-testing on both GCC (with > DejaGnu) and glibc (without it), and having also done some substantial > porting work to get the GCC testing working with our systems, I have I'll note that GCC testing is much easier th

Re: Can we deprecate $subdir?

On 11/25/18 5:15 PM, Ben Elliston wrote: > * The GCC testsuite uses $subdir extensively and I'm sure other > testsuites do, too. Correct. Depreciating subdir would potentially break testsuites even if you made it work with the GNU toolchain tests. - rob - signature.asc Description:

Re: isremote and unix board special handling question

On 11/27/18 3:46 PM, Steve Ellcey wrote: Sorry, catching up from being offline while traveling... > I have a question about the special handling of the 'unix' name in > dejagnu. I am doing some GCC testing which uses dejagnu and I > want to create a new baseboard (unix-sysroot) which is just

Re: isremote and unix board special handling question

On 11/28/18 4:26 PM, Jacob Bachmeyer wrote: > $DEJAGNU and the local init files ($base_dir/site.exp, $objdir/site.exp) > are loaded independently.  It does not help that both local and global > init files are named (or default to) "site.exp".  Documenting this is on > my TODO list. The site.exp

Re: isremote and unix board special handling question

On 11/28/18 2:10 PM, Brooks Moses wrote: > Much like the other big lesson of the last 30 years or so: Shipping > something that works is far more valuable than waiting to try to > achieve perfection. :) It was worse than that. :-) When I started DejaGnu, there were only 7 of us in all of Cygnu

Re: isremote and unix board special handling question

On 11/27/18 7:27 PM, Ben Elliston wrote: > On Tue, Nov 27, 2018 at 06:53:17PM -0600, Jacob Bachmeyer wrote: > >> As we see, set_board_info only works if the specified /entry/ has not >> already been defined. > > That is consistent with the manual: > > @node set_board_info procedure, [...] >

Re: relative line numbers and dg-line directive

On 06/01/2017 10:23 AM, Tom de Vries wrote: > I have only tested this with the local testsuite. > > I can test this more extensively with the gcc testsuite. I suppose I'll > have to test both: The true validation test would be a full run of cross-testing to an embedded system, before and after

Re: Separating stdout and stderr

On 03/25/2016 08:57 AM, Christophe Lyon wrote: > Well, as Yvan showed with his recent patches, we seem to be using > DejaGnu in an unusual configuration, which uncovers corner case bugs. As I've mentioned before, we need to make our validation less unusual. :-) > I'm seeing "random" results in

Re: patch #8947: Don't try to execute a data file

On 03/22/2016 01:15 AM, Ben Elliston wrote: > +# Don't try to execute a data file, which is used by some tests > +# to compare output. > +if {[regexp "^\.txt$" $prog]} { > + return "" > +} > > Wouldn't it be better to not call unix_load with such an argument? Unix_load is

Re: removing stale config files

On 03/22/2016 04:28 AM, Ben Elliston wrote: > The following files are in the config/ directory. Many of these are > very, very old. Can you please let me know if you suggest (a) > removing a file immediately (and if so, which one) or (b) marking a > file for removal after the next release. > > T

Re: PATCH: rewrite utils.exp:which

On 03/21/2016 01:50 PM, Ben Elliston wrote: > There was a '???' comment in utils.exp:which, so I rewrote it to > properly mimic the behaviour of the which(1) shell utility. A nice > side effect of the new version is that, because the new proc > normalises the filename when it's found, the GCC test

Re: [RFA] fix remote testing I/O conflicts

On 03/03/2016 01:45 AM, Yvan Roux wrote: > To fix this issue, changing the layout to have the testcases > downloaded and executed inside "/tmp/pid/" directory would do the job, > but as this change might have an impact on other project or on other > config which use remote_download, my proposal is

Re: Honor timeout in lib/rsh.exp:rsh_exec

On 09/28/2014 10:36 AM, Maxim Kuvyrkov wrote: > This patch fixes an issue that rsh_exec does bails on tests in just 10sec, > even when board specifies a longer timeout. The problem is that > lib/rsh.exp:rsh_exec (which is called via remote.exp:remote_exec) reads its > timeout from global timeou

Re: Few improvements for androideabi board

On 11/05/2013 04:43 AM, Alexander Ivchenko wrote: > What's the next step for the patch? Given your OK, could you please > submit it? Sorry, I've been traveling to conferences. Yeah, I'll commit it, feel free to nag me if I don't do it this week. - rob -

Re: Few improvements for androideabi board

On 10/15/2013 07:26 AM, Alexander Ivchenko wrote: > The "cross" addition in DejaGNU and the correspoding change in the > test itself ({ target native cross }) would allow us to run them. > Defining cross as '1' in androideabi > board is not a very pretty solution, but I don't see others now.. M

Re: Few improvements for androideabi board

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/14/2013 04:14 AM, Ben Elliston wrote: > Rob, would you mind reviewing this patch? You know this bit of code > better than I do. I'd like to see the 'iscross' proc removed, ! 'isnative' should be sufficient. I'm a touch confused, this looks l

Re: dejagnu-2.0 feature wishlist (from Cauldron 2013)

On 08/30/2013 01:31 PM, Robert Hartmann wrote: > Well, as Windows user I would like to have a DejaGnu executable, > running as a native Win32-Application (Win95->...) inside command.com, > cmd.exe or MSYS. DejaGnu is not an executable, it's a TCL shell script. The executable you need is for exp

Re: dejagnu-2.0 feature wishlist (from Cauldron 2013)

On 08/31/2013 07:35 AM, Jan Kratochvil wrote: > On Sat, 31 Aug 2013 15:02:16 +0200, Rob Savoye wrote: > Not-my-business but when such decision is being made please use Gollum or any > other GIT-contributable Wiki (if there is any other such). Interesting... I've been using med

Re: dejagnu-2.0 feature wishlist (from Cauldron 2013)

On 08/30/2013 07:13 PM, Ben Elliston wrote: > What we really need is a wiki page to put all of this discussion > in. I just checked and, unfortunately, Savannah provides nothing > for this purpose. :-( Yeah, this is why I maintain mu own wiki for Gnash. Since I already have a server for Gnash,

Re: dejagnu-2.0 feature wishlist (from Cauldron 2013)

On 08/29/2013 11:42 AM, Jan Kratochvil wrote: > I haven't found any discussion here about the features in hypothetical > dejagnu-2.0, as presented by Rob Savoye at Cauldron 2013. Sorry, I've been focused on other tasks, this Fall I'll be launching into DejaGnu again heavil

Re: [PATCH] Support of bridge method testing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/12/13 23:37, Ben Elliston wrote: > Rob, Docbook is a dog. Why don't we take the current generated > Texinfo file as the starting point and just use that, like every > other GNU project? Actually other projects don't use texinfo as the prima

Re: autotools clean up

On 06/25/12 23:33, Sami Kerola wrote: > Hello dejagnu maintainers, > > See attachment for rather large patch. I took liberty to remove all > autofiles from git repository. > > $ git diff HEAD~1 --shortstat > 52 files changed, 189 insertions(+), 45448 deletions(-) > > I described commit having t

Re: patch to allow file name argument to --xml

On 06/11/12 11:43, Tom Tromey wrote: > I would have, but --xml already isn't documented, and I don't feel that > I know enough about exactly what it does to document it very well. I added the XML output option solely to make it possible to suck all the testing results into an SQL database. I fo

Re: deja gnu

On 03/09/11 05:47, ras...@copperheadsystems.com wrote: > whether dejagnu supports Linux. Yes, of course it does. - rob - ___ DejaGnu mailing list DejaGnu@gnu.org http://lists.gnu.org/mailman/listinfo/dejagnu

Re: %s, %t and friends ?

On 06/14/09 16:47, Aaron Gray wrote: \ I could not find any references in the documentation to %s, and %t ? %s gives me the source file containing the %s reference. %t gives me a .tmp file. Are there any other % symbols that could be of interest. Look in the manual for make, as these are Ma

Re: stopping CVS service

Ben Elliston wrote: > After a long period of running with the GIT tree, I am shutting down > CVS service today. Fine with me. I'm so glad to be away from CVS... - rob - ___ DejaGnu mailing list DejaGnu@gnu.org http://lists.gnu.org/mailman/li

Re: upcoming enhancement requests for GCC testing

Janis Johnson wrote: > The GCC testsuite support does some really ugly things to support > functionality that is not available in DejaGnu. For example, it uses I think that could be called an understatement. :-) In the begging, all testsuites actually lived in DejaGnu, so there was tighter int

Re: DejaGnu suitable for network server testing?

Rainer Gerhards wrote: > the wrong path. So actually a quick yes or no type of answer would be > fine with me. Yes. :-) > I am in the process at building test suites for my rsyslog project. > This is a GPLv3 syslogd replacement. Almost all tests involve running > a server instance of the daemo

Re: Debian patches: dejagnu's testsuite

Daniel Jacobowitz wrote: > Thanks. Yeah, that's what I do too. I'm going to drop the patches I > posted from the Debian package, but the ones for host_exec in > particular might be generally applicable - it seems like the dejagnu > testsuite tests mostly that and the C header, neither of which a

Re: Debian patches: dejagnu's testsuite

Daniel Jacobowitz wrote: > Is DejaGNU's testsuite useful? I admit, a strange question to have to Minimally useful. I think it's fair to say that almost nobody runs the DejaGnu test suite, they run the GCC/GDB one to test DejaGnu instead. - rob - __

Re: time out from degagnu

noam_a wrote: > when i execute the test on my version of gdb, it failed with timeout. > but! when i execute the commands for gdv directly threw gdb console' it > seems that every thing work fine and there is no susspend or something like > that. Often these are buffering issues. You can run wit

Re: Quoting problem in standard_send

Daniel Jacobowitz wrote: > This patch fixes a TCL error in standard_send. You can't quote > a string by saying eval "{$string}" - if the string has an unmatched Thanks, I just checked this in. - rob - ___ DejaGnu mailing list DejaGnu@gnu.o

Re: Integration of the TAT tool into dejagnu proposal

Franco Carbognani wrote: > I have made available a snapshot of our changes (as tar/gzip file) > under this web link: > https://workarea.ego-gw.it/ego2/ego/itf/software/tat-deja-gnu/resolveuid/711499f1ae3bc6acd699f86aa28e560f > > Let me know if you have any problem in dowloading it. > > The TAT code

Re: Integration of the TAT tool into dejagnu proposal

Franco Carbognani wrote: > The version of dejagnu we put together and that we are keep testing > seems very well fitting our needs and should potentially feet the > needs of all the project currently using TAT. > I want to remark we simply made an interface extension, existing > dejagnu features a

Re: hello world

deckrider wrote: > I'm having difficulty getting the simplest hello world example to > pass, using the following, copied straight from the manual (I added > the 'default' so I can get an idea as to when it fails): Try using one of the examples in the source tree, I'm not sure if the manual is 10

Re: Testing on a simulator

On Mon, Sep 18, 2006 at 02:07:05AM -0700, Mohamed Shafi wrote: > Can i see this information if i use the debug options > while testing? Several -v options should print out which simulator is being use. Is this a standalone simulator, or part of GDB ? - rob - ___

Re: remote serial connection

David Byron wrote: > On 25 July 2006, Dave Korn wrote: > Searching a bit further to the back of the shelf turned up the missing file. > Turns out your suggestion is on the money...basically just called > telnet_open and then invoke cu and wait for a couple of prompts. What also happened was ex

Re: [HOWTO] RE: dejagnu remote testing without rsh/rcp facilities on target.

Dave Korn wrote: > Ok, so you have a command line listening over a serial port? You could > perhaps write a quick'n'dirty downloader using some ascii format (e.g. srec) > couldn't you? Anyway, even if you can't ... Many years ago I added the ability to GDB to convert any executable file i

Re: ssh/scp discrepencies while running a testsuite

Daniel Jacobowitz wrote: I will try CVS next week--it's a beautiful Friday evening now and I just can't work any longer. Must be nice! Argh wet, cloudy, and still Friday morning... Here it's cold, windy, and snowing for two days. - rob - ___

Re: CVS commit messages

Ben Elliston wrote: shows that nothing has arrived to this list since December 2003. Does the GNU Savannah system even produce CVS commit messages? If so, can we control where they go? Yes to both. I probably need to just email the savannah sysadmins and have them fix the broken connection

Re: PATCH: flatten Makefile tree

Ben Elliston wrote: We could do that. Why not just call the target `examples', though? That's ok too. I just thought it would be good to have a target to build them. - rob - ___ DejaGnu mailing list DejaGnu@gnu.org http://lists.gnu.or

Re: PATCH: flatten Makefile tree

Ben Elliston wrote: This patch substantially flattens the tree of Makefile.am's we have. All of the testsuite Makefile.ams have now been collected in the top-level Makefile.am. Well, considering the lower level Makefiles don't really do much, this isn't much of a change anyway. into the

Re: another way to port dejagnu to windows

Yan Jiang wrote: I am new to dejagnu, using it to make a test framework about 2-3 months. Recently, my boss wants me to port the whole framework to windows. Cygwin is a good choice which i have already tried out. Now I came through this idea that whether I can port dejagnu to windows using acti

Re: Using DejaGnu in a regression farm

[EMAIL PROTECTED] wrote: This is interesting. What is SBC and X10 controller? How much does it cost? Sorry. SBC = Single Board Computer. In this case, usually an evaluation boards from a micro-processor manufacturer. The X10s are very cheap. You can get them at most electronics stores. The

Re: Using DejaGnu in a regression farm

Sean Cavanaugh wrote: I'm looking at using DejaGnu to help automate a regression testing farm. We plan to have a number of boards connected to the test computer via serial and network, and will be testing the Board Support Packages we're developing (including testing everything from the Linux

Re: newlib_include_flags/newlib_link_flags [libgloss,etc. too]

Doug Evans wrote: Suppose one has a full source tree layout that is not the usual Cygnus layout (where everybody is a sibling). I'm not entirely sure how useful this would be as most folks I talk to use the version of DejaGnu in their path, not in their source tree. It's really only GCC/GDB

Re: Remove packaging/rpm/dejagnu.spec

Ben Elliston wrote: Similarly, the DejaGnu package maintainer for Fedora has told me that they maintain their own RPM spec file. Accordingly, I'd like to delete the one in the source tree. There are way more distributions than just Fedora. I'd actually like to see the one used for Fedora, a

Re: [RFA:] libffi-dg.exp: Replace \n with \r?\n in dg-output

Hans-Peter Nilsson wrote: Perhaps also a simple means to change \r\n into \n in test output, maybe specified in the baseboard file? That would have solved the specific problem at hand. That's what I get out of his earlier message. A generic way for DejaGnu to support different interpretations o

Re: Add program_transform_name to runtest.exp

Josh Conner wrote: Adding support for the program_transform_name (sed-style expression to convert the names of executables under test) would simplify the testing of gcc cross-compilers, since the runtest.exp procedure "transform" is unable to find binaries created with a transformed name. I'd

Re: [RFA:] libffi-dg.exp: Replace \n with \r?\n in dg-output

Andreas Tobler wrote: Hans-Peter Nilsson wrote: CC to the dejagnu list in the hope that something to help without the assumption needed below will appear in a future version. Something to help with what assumption ? I haven't followed this thread, so if you want me to fix/add something to DejaG

Re: Oops, proper OpenBSD warning pruning

Mark Kettenis wrote: Did you really? Anyway, I discovered a few more cases. I'm pretty sure noew that I've got them all covered with this patch. It'd be great if you could apply this one too ;-). Done. I know what you mean. Finding all the cases to filter is a bit trial and error. Course now

Re: Oops, proper OpenBSD warning pruning

Mark Kettenis wrote: Even though I was sure about that one, I just discovered there is another pattern that should be caught. Here's a patch that adds the missing one. Thanks, I checked in the latest version. - rob - ___ DejaGnu mailing list Deja

Re: Oops, proper OpenBSD warning pruning

Mark Kettenis wrote: Please ignore my previous patch. Thanks to a typo, I didn't notice it wasn't working. This one does, really! Are you sure ? I hope so, cause I just checked this in. :-) - rob - ___ DejaGnu mailing list DejaGnu@gnu.org http

Re: unit tests

Baurzhan Ismagulov wrote: For now, I've added mytest to noinst_PROGRAMS and defined mytest_SOURCES. What should I do in mytest.exp? exec? Look at the unit.cc test case. This uses a simple header file to print FAIL or PASS states from the unit test. Then you use the functions in dejagnu.exp to e

Re: Ping*2: baseboards/cris-sim.exp

Hans-Peter Nilsson wrote: I sent this reminder a week ago, but I don't see the message in the ml archives. Anyway, it still seems true. (Browsing http://savannah.gnu.org/cgi-bin/viewcvs/dejagnu/dejagnu/> I don't see any CVS activity at all in the last three months; perhaps the CVS has moved?)