public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
To: Eric Blake <ebb9@email.byu.edu>
Cc: java@gcc.gnu.org,  gcc@gcc.gnu.org
Subject: Re: CVS error on ppc
Date: Wed, 01 May 2002 09:42:00 -0000	[thread overview]
Message-ID: <87wuunizto.fsf@pooh-sticks-bridge.tapsellferrier.co.uk> (raw)
In-Reply-To: <15568.5917.163844.977687@quaffle.ee.byu.edu>

Eric Blake <ebb9@email.byu.edu> writes:

> 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/<arch>/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. 

I don't seem to be able to do that. Submitting with high priority
gives me an error.

Can someone else submit it please?


Nic

  reply	other threads:[~2002-05-01 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-01  9:26 Eric Blake
2002-05-01  9:42 ` Nic Ferrier [this message]
2002-05-01  9:56 ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2002-05-01  7:09 Nic Ferrier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wuunizto.fsf@pooh-sticks-bridge.tapsellferrier.co.uk \
    --to=nferrier@tapsellferrier.co.uk \
    --cc=ebb9@email.byu.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=java@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).