public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60191] test case gfortran.dg/dynamic_dispatch_1/3.f03 fail on ARMv7
Date: Sun, 16 Feb 2014 12:28:00 -0000	[thread overview]
Message-ID: <bug-60191-4-hMByQKyTO7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60191-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60191

--- Comment #6 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to Dominique d'Humieres from comment #4)
> (In reply to Bernd from comment #3)
> IIRC the tests gfortran.dg/stat_(1|2).f90 fail if the user's uid or gid are
> different from those of the directory in which the tests are run (see
> pr42900). If for some reason you cannot run the tests with user's IDs
> matching those of the working directory, these tests will always fail.
> 

Ok, thanks. That would explain this one:

My target does not have a hard disk, so I mounted everything
with nfs and the user/group gets squashed by the server.
I log in with root at the target, but everything on the nfs share
is owned by nobody, nogroup I think. But I can fix that somehow.

> For the other failures, are they regressions or is it the first time they
> are tested on armv7l-unknown-linux-gnueabihf?

Given how hard it was to boot strap everything on that target,
(I started in december!), I don't think anybody did that before.
The target itself was built from scratch with cross-compilers.


  parent reply	other threads:[~2014-02-16 12:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  8:39 [Bug fortran/60191] New: " bernd.edlinger at hotmail dot de
2014-02-14  8:42 ` [Bug fortran/60191] " pinskia at gcc dot gnu.org
2014-02-15 17:00 ` janus at gcc dot gnu.org
2014-02-16 10:03 ` bernd.edlinger at hotmail dot de
2014-02-16 10:47 ` dominiq at lps dot ens.fr
2014-02-16 11:53 ` janus at gcc dot gnu.org
2014-02-16 12:28 ` bernd.edlinger at hotmail dot de [this message]
2014-02-17  7:55 ` bernd.edlinger at hotmail dot de
2014-02-17  8:17 ` bernd.edlinger at hotmail dot de
2014-03-25 12:17 ` burnus at gcc dot gnu.org
2014-03-25 14:48 ` bernd.edlinger at hotmail dot de
2014-03-31  9:14 ` mikael at gcc dot gnu.org
2014-04-04 13:55 ` edlinger at gcc dot gnu.org
2014-04-05  6:13 ` bernd.edlinger at hotmail dot de
2014-04-10 20:14 ` edlinger at gcc dot gnu.org

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=bug-60191-4-hMByQKyTO7@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).