GNU bug report logs - #14711
struct rusage redefinition issues on ppc - gnu time-1.7

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Bob Proulx <bob <at> proulx.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#14711: closed (struct rusage redefinition issues on ppc - gnu
 time-1.7)
Date: Wed, 26 Jun 2013 03:34:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 25 Jun 2013 21:33:19 -0600
with message-id <20130626033319.GA29623 <at> hysteria.proulx.com>
and subject line Re: bug#14711: struct rusage redefinition issues on ppc - gnu time-1.7
has caused the debbugs.gnu.org bug report #14711,
regarding struct rusage redefinition issues on ppc - gnu time-1.7
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
14711: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14711
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Aijaz Baig <aijaz.baig <at> tcs.com>
To: bug-coreutils <at> gnu.org
Subject: struct rusage redefinition issues on ppc - gnu time-1.7
Date: Tue, 25 Jun 2013 15:02:25 +0530

[Message part 3 (text/plain, inline)]

Hi.
I am trying to compile Gnu time 1.7 for a PowerPC system using the 
windriver build system which is based on yocto.
The build fails with an error at resuse.h:44:error: redefinition of 
'struct rusage'.
On searching the internet found  Benoit Sibaud was facing a same problem 
on sparc. He commented out system definition for struct rusage and it 
worked for him. For me however it doesn't work. On doing that it fails to 
link the various object files viz. time.o getopt.o error.o resuse.o and 
version.o.
On another thread here, Jim McMaster was also facing a similar issue while 
building it for Solaris.  Paul Eggert suggested him to define HAVE_WAIT3 
in the Makefile. I've tried that too but it fails as well. And its again 
while linking the aforementioned object files.
Please help me in getting this fixed. Where do I check for the build logs 
in detail. As what exactly is causing the linking to fail? It is failing 
with an errors of the sort 'crt1.o: No such file: No such file or 
directory'. These are link time errors right? At times I've seen people 
saying they signify a corrupted libc. However when I manually search for 
it in my Sysroot, I see it.
I am confused. Please elaborate. Keen to hear.

Aijaz Baig
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Bob Proulx <bob <at> proulx.com>
To: Aijaz Baig <aijaz.baig <at> tcs.com>
Cc: 14711-done <at> debbugs.gnu.org
Subject: Re: bug#14711: struct rusage redefinition issues on ppc - gnu time-1.7
Date: Tue, 25 Jun 2013 21:33:19 -0600

Aijaz Baig wrote:
> Hi.

Hi.

> I am trying to compile Gnu time 1.7 for a PowerPC system using the 
> windriver build system which is based on yocto.

Thanks for the report.  However you are reporting a bug in the time
project to the coreutils project.  Time and coreutils are two separate
projects.  GNU time doesn't use any bug trackers.  Therefore this bug
to the coreutils project will never be seen by the GNU time
maintainer.

The best reporting address for problems with time is the
bug-gnu-utils <at> gnu.org mailing list.  It isn't a good place.  It is
only the best place relative to any other reporting address.

The GNU time project has actually been quite dead for many, many
years.  However the official maintainer keeps saying that a new
release will happen every time he is asked.  Therefore the project
sits in a perpetual limbo betwixt and between.

In my opinion the best way to compile GNU time is to grab the patched
sources from one of the many software distributions.  I am the
maintainer for Debian and so my biased opinion would be to use the
Debian patched sources.  But most of the patches have been shared all
around by now and so any of the distros are likely very similar at
this stage.

I will continue the discussion in your other message to the discussion
list and then redirect it over to the bug-gnu-utils list.  Anyone who
wishes to join in please meet us over there.

Bob

> Notice: The information contained in this e-mail
> message and/or attachments to it may contain 
> confidential or privileged information. If you are 
> not the intended recipient, any dissemination, use, 
> review, distribution, printing or copying of the 
> information contained in this e-mail message 
> and/or attachments to it are strictly prohibited. If 
> you have received this communication in error, 
> please notify us by reply e-mail or telephone and 
> immediately and permanently delete the message 
> and any attachments. Thank you

READ CAREFULLY.  By reading this email, you agree, on behalf of your
employer, to release me from all obligations and waivers arising from
any and all NON-NEGOTIATED agreements, licences, terms-of-service,
shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure,
non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I
have entered into with your employer, its partners, licensors, agents
and assigns, in perpetuity, without prejudice to my ongoing rights and
privileges.  You further represent that you have the authority to
release me from any BOGUS AGREEMENTS on behalf of your employer.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.