All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roland Vossen" <rvossen@broadcom.com>
To: sparclinux@vger.kernel.org
Subject: Re: Simple piece of code with unexpected behavior
Date: Thu, 11 Aug 2011 14:18:53 +0000	[thread overview]
Message-ID: <4E43E4CD.6020805@broadcom.com> (raw)
In-Reply-To: <4E43CB0F.7050700@broadcom.com>

> Something is very wrong with your build environment:

Thanks for doing this experiment David. Can you email me some details on 
the build chain you are using: eg, output of 'gcc -v'? Did you cross 
compile gcc yourself or did you download a binary ?

Thanks, Roland.



  parent reply	other threads:[~2011-08-11 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 12:29 Simple piece of code with unexpected behavior Roland Vossen
2011-08-11 12:44 ` David Miller
2011-08-11 14:18 ` Roland Vossen [this message]
2011-08-11 14:34 ` David Miller

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=4E43E4CD.6020805@broadcom.com \
    --to=rvossen@broadcom.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.