contrib/test_summary mail error

[Cynthia Rempel]

Hi,

I tried to run the following command:

../gcc/contrib/test_summary -p my_commentary.txt -m gcc-testresu...@gcc.gnu.org 
| sh

and got the following error:

sh: 22297: Mail: not found

After digging through emails, ran accross

http://lists.debian.org/debian-user/2002/04/msg00065.html

Mint complained it was a 'virtual package' and told me to pick one of three 
options:
mailutils 1:2.2+dfsg1-5
  heirloom-mailx 12.5-1build1
  bsd-mailx 8.1.2-0.2006cvs-1

The first one didn't fix the error, but the second one did.  Could you fix the 
contrib/test_summary script to suggest mail packages that would work for 
gcc/contrib/test_summary on Ubuntu?
Thanks!
Cindy

Re: contrib/test_summary mail error

[Toon Moene]

On 01/04/2013 04:14 PM, Cynthia Rempel wrote:


Hi,

I tried to run the following command:

../gcc/contrib/test_summary -p my_commentary.txt -m gcc-testresu...@gcc.gnu.org 
| sh


I added "| sed -e 's/Mail/mailx/'" before the "| sh" and it worked for 
Debian Tesing (several months ago).  Apparently I had picked the wrong 
mail package too.


Perhaps test_summary needs some sort of configure-type approach to 
figure out what the mail sender is on the host system ...


--
Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news

Re: contrib/test_summary mail error

[Joel Sherrill]

I would love to add that as a command line option
and another to let us say which BSP we used on the
subject line. But I can't figure out the relationship
between the shell code and the awk code which
does the dirty work.

Can anyone explain how the arguments/variablles
get passed from the shell code to the embedded awk
script?

Thanks.

--joel

On 01/04/2013 09:14 AM, Cynthia Rempel wrote:

Hi,

I tried to run the following command:

../gcc/contrib/test_summary -p my_commentary.txt -m gcc-testresu...@gcc.gnu.org 
| sh

and got the following error:

sh: 22297: Mail: not found

After digging through emails, ran accross

http://lists.debian.org/debian-user/2002/04/msg00065.html

Mint complained it was a 'virtual package' and told me to pick one of three 
options:
mailutils 1:2.2+dfsg1-5
   heirloom-mailx 12.5-1build1
   bsd-mailx 8.1.2-0.2006cvs-1

The first one didn't fix the error, but the second one did.  Could you fix the 
contrib/test_summary script to suggest mail packages that would work for 
gcc/contrib/test_summary on Ubuntu?
Thanks!
Cindy



--
Joel Sherrill, Ph.D. Director of Research&  Development
joel.sherr...@oarcorp.comOn-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35806
Support Available   (256) 722-9985

Re: contrib/test_summary mail error

[Andreas Schwab]

Joel Sherrill  writes:

> Can anyone explain how the arguments/variablles
> get passed from the shell code to the embedded awk
> script?

Via parameter substitution.  The awk script does not need to look at
them.  The mailto variable is passed in the environment, since it is
only used by the produced shell code.

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: stabs support in binutils, gcc, and gdb

[David Edelsohn]

On Thu, Jan 3, 2013 at 11:12 PM, Joel Brobecker  wrote:
>> AIX still uses STABS.  GCC produces it and GDB consumes it.
>>
>> Recent releases of AIX now support DWARF as well, but GCC and GDB have
>> not been converted to use it on AIX.
>
> Note that GNU ld is now completely usable; and one of the side
> effects of using GNU ld is the ability to switch over to DWARF,
> even on older versions such as AIX 5.1.

Can you please clarify what "GNU ld is not completely usable" means?
Is that referring to DWARF support? to compatibility with specific AIX
releases? to compatibility with AIX DWARF feature?

Thanks, David

gcc-4.6-20130104 is now available

[gccadmin]

Snapshot gcc-4.6-20130104 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20130104/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 4.6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_6-branch 
revision 194920

You'll find:

 gcc-4.6-20130104.tar.bz2 Complete GCC

  MD5=6a8da5064ec72f90f8e66e37421dea94
  SHA1=3b76e6273d630108b2025e213df14cd1170ef099

Diffs from 4.6-20121228 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-4.6
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.

Re: stabs support in binutils, gcc, and gdb

[David Edelsohn]

On Fri, Jan 4, 2013 at 3:20 PM, David Edelsohn  wrote:
> On Thu, Jan 3, 2013 at 11:12 PM, Joel Brobecker  wrote:
>>> AIX still uses STABS.  GCC produces it and GDB consumes it.
>>>
>>> Recent releases of AIX now support DWARF as well, but GCC and GDB have
>>> not been converted to use it on AIX.
>>
>> Note that GNU ld is now completely usable; and one of the side
>> effects of using GNU ld is the ability to switch over to DWARF,
>> even on older versions such as AIX 5.1.
>
> Can you please clarify what "GNU ld is not completely usable" means?
> Is that referring to DWARF support? to compatibility with specific AIX
> releases? to compatibility with AIX DWARF feature?

Sorry, I meant what "GNU ld is now completely usable" means because I
believe that it actually is NOT completely usable on AIX.

Thanks, David

error: invalid use of void expression

[Bruce Korb]

You may have been thinking you were using "memcpy", but you were
using "bcopy" instead.  Please apply the patch to md5.c.  Thanks!

$ gcc -c shar-i.c
shar-i.c: In function 'md5_process_bytes':
shar-i.c:3087:13: error: invalid use of void expression


   1034 extern void bcopy (__const void *__src, void *__dest, size_t __n)
   1035  __attribute__ ((__nothrow__ , __leaf__)) __attribute__ 
((__nonnull__ (1, 2)));


   3082   if (len >= 64)
   3083 {
   3084   if (((uintptr_t) (buffer) % _Alignof (uint32_t) != 0))
   3085 while (len > 64)
   3086   {
   3087 md5_process_block (bcopy (buffer, ctx->buffer, 64), 64, 
ctx);
   3088 buffer = (const char *) buffer + 64;
   3089 len -= 64;
   3090   }


In file included from shar.c:55:0:
../lib/md5.c: In function 'md5_process_bytes':
../lib/md5.c:261:13: error: invalid use of void expression
254   if (len >= 64)
255 {
256 #if !_STRING_ARCH_unaligned
257 # define UNALIGNED_P(p) ((uintptr_t) (p) % alignof (uint32_t) != 0)
258   if (UNALIGNED_P (buffer))
259 while (len > 64)
260   {
261 md5_process_block (memcpy (ctx->buffer, buffer, 64), 64, 
ctx);
262 buffer = (const char *) buffer + 64;
263 len -= 64;
264   }
265   else

Re: error: invalid use of void expression

[Eric Blake]

On 01/04/2013 05:47 PM, Bruce Korb wrote:
> You may have been thinking you were using "memcpy", but you were
> using "bcopy" instead.  Please apply the patch to md5.c.  Thanks!
> 

Rather than fixing the call site of memcpy, we should instead fix the
real bug, the fact that you are even doing *ifndef HAVE_MEMCPY and
defining memcpy to bcopy() in the first place.  For some reason, your
./configure run is not properly setting HAVE_MEMCPY in your config.h
file.  Not that it needs to be set: these days, we can assume C89, and
therefore can assume memcpy; code that uses bcopy() is obsolete, and
actually less portable.

The version of md5.c in gnulib does not suffer from the same bug as the
version in sharutils.git.  Therefore, I don't see why we need to patch
gnulib at this time.  Are you sure you updated sharutils properly?  For
starters:

$ diff -ub ../sharutils/lib/md5.c lib/md5.c |head -55 |xclip
--- ../sharutils/lib/md5.c  2013-01-04 19:12:38.105067385 -0700
+++ lib/md5.c   2012-12-31 17:50:53.232969921 -0700
@@ -1,12 +1,12 @@
-/* md5.c - Functions to compute MD5 message digest of files or memory
blocks
+/* Functions to compute MD5 message digest of files or memory blocks.
according to the definition of MD5 in RFC 1321 from April 1992.
-   Copyright (C) 1995, 1996, 2001, 2007 Free Software Foundation, Inc.
-   NOTE: The canonical source of this file is maintained with the GNU C
-   Library.  Bugs can be reported to bug-gl...@prep.ai.mit.edu.
+   Copyright (C) 1995-1997, 1999-2001, 2005-2006, 2008-2013 Free Software
+   Foundation, Inc.
+   This file is part of the GNU C Library.

This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
-   Free Software Foundation; either version 3, or (at your option) any
+   Free Software Foundation; either version 2, or (at your option) any
later version.

This program is distributed in the hope that it will be useful,
@@ -15,56 +15,51 @@
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
-   along with this program; if not, write to the Free Software Foundation,
-   Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.  */
+   along with this program; if not, see .  */

 /* Written by Ulrich Drepper , 1995.  */

-#ifdef HAVE_CONFIG_H
-# include 
-#endif
+#include 
+
+#include "md5.h"

+#include 
+#include 
+#include 
+#include 
 #include 

-#if STDC_HEADERS || defined _LIBC
-# include 
-# include 
-#else
-# ifndef HAVE_MEMCPY
-#  define memcpy(d, s, n) bcopy ((s), (d), (n))
-# endif
+#if USE_UNLOCKED_IO
+# include "unlocked-io.h"
 #endif

-#include "md5.h"

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature

Re: stabs support in binutils, gcc, and gdb

[Joel Brobecker]

> > Can you please clarify what "GNU ld is not completely usable" means?
> > Is that referring to DWARF support? to compatibility with specific AIX
> > releases? to compatibility with AIX DWARF feature?
> 
> Sorry, I meant what "GNU ld is now completely usable" means because I
> believe that it actually is NOT completely usable on AIX.

AdaCore has successfully switched to GNU ld on AIX, tested on AIX
version 5.x and 7.x. We use a version derived from an old HEAD,
I believe, but the latest release might have all the necessary
changes. I cannot tell you that it's perfect, and some options
provided by the native linker might not be implemented (particularly
the options relating to TOCs). But we released GNAT Pro 7.0.1/7.0.2
using GNU ld early last year, and I don't remember seeing any real
problem being reported.

We had to do some changes, and make some fixes, mostly done by
Tristan, and normally they should have been contributed to the
FSF tree. Overall, I think we're pretty happy with GNU ld as
of now.

-- 
Joel