From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 633 invoked by alias); 1 May 2002 16:26:28 -0000 Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org Received: (qmail 613 invoked from network); 1 May 2002 16:26:25 -0000 Received: from unknown (HELO quaffle.ee.byu.edu) (128.187.114.165) by sources.redhat.com with SMTP; 1 May 2002 16:26:25 -0000 Received: (from eblake@localhost) by quaffle.ee.byu.edu (8.11.6/8.11.6) id g41GQ8p27317; Wed, 1 May 2002 10:26:08 -0600 X-Authentication-Warning: quaffle.ee.byu.edu: eblake set sender to eblake@ee.byu.edu using -f MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15568.5917.163844.977687@quaffle.ee.byu.edu> Date: Wed, 01 May 2002 09:26:00 -0000 To: Nic Ferrier Cc: java@gcc.gnu.org Cc: gcc@gcc.gnu.org From: Eric Blake Subject: Re: CVS error on ppc X-SW-Source: 2002-05/txt/msg00002.txt.bz2 You're not the only one. Something is wrong in the Makefile script, because I got the same error on a RedHat box: cvs [update aborted]: reading libjava/sysdep/i386/locks.h: Too many levels of symbolic links Basically, something in the Makefile is linking libjava/sysdep//locks.h to itself, causing an infinite link recursion. It is also affecting compilation: ... linking ../../../gcc/libjava/sysdep/i386/locks.h to sysdep/locks.h configure: error: ../../../gcc/libjava/sysdep/i386/locks.h: File not found make[2]: *** [Makefile] Error 1 I'm not sure who is responsible, but would you like to file a high-priority PR since you found it first? I'm cc'ing the gcc list, in case anyone knows what went wrong. > From: Nic Ferrier > To: > Date: 01 May 2002 15:09:39 +0100 > > Something strange just happened on my PPClinux box... I was just > trying a cvs update on the gcc tree (the branch) and I got this: > > cvs [update aborted]: reading libjava/sysdep/powerpc/locks.h: Too many levels of symbolic links > nferrier@imac:~/projects/gnu/gcc/gcc-cvs$ Write failed flushing stdout buffer. > write stdout: Broken pipe > > Bizzare! It worked fine last night (though the build didn't run, > which is why I was updating today - so I could report the fault). > > > Nic ---- Eric Blake ebb9@email.byu.edu