public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeremyhu at macports dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/54847] --enable-libstdcxx-time=yes non-functional on darwin
Date: Sun, 07 Oct 2012 19:38:00 -0000	[thread overview]
Message-ID: <bug-54847-4-dYvLsJwGRO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54847-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #9 from Jeremy Huddleston Sequoia <jeremyhu at macports dot org> 2012-10-07 19:38:18 UTC ---
(In reply to comment #8)
> (In reply to comment #7)
> > Yeah, Jack... your copying them and pasting them here just makes it easier for
> > me to accidentally read them.  Please don't do that.  The code is GPL3, and it
> > remains GPL3 even if you copy/paste it into this bug report.
> 
> Well you are bound to read code fragments that are GPLv3 in FSF gcc bugzilla so
> I 
> don't know what you expecting here. I would stop reading FSF gcc bugzilla if
> you can't 
> reasonably participate.

I can certainly participate.  I just need to make sure that I don't read any
code snippets that are GPL3 licensed.

> Also, aren't headers considered different in context 
> from source 
> files?

It depends how they are licensed, but this is really a side conversation.


  parent reply	other threads:[~2012-10-07 19:38 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 16:11 [Bug libstdc++/54847] New: " howarth at nitro dot med.uc.edu
2012-10-07 17:31 ` [Bug libstdc++/54847] " paolo.carlini at oracle dot com
2012-10-07 17:40 ` jeremyhu at macports dot org
2012-10-07 18:02 ` paolo.carlini at oracle dot com
2012-10-07 18:35 ` jeremyhu at macports dot org
2012-10-07 18:51 ` howarth at nitro dot med.uc.edu
2012-10-07 18:54 ` howarth at nitro dot med.uc.edu
2012-10-07 19:04 ` jeremyhu at macports dot org
2012-10-07 19:22 ` howarth at nitro dot med.uc.edu
2012-10-07 19:38 ` jeremyhu at macports dot org [this message]
2012-10-07 19:43 ` howarth at nitro dot med.uc.edu
2012-10-07 20:11 ` howarth at nitro dot med.uc.edu
2012-10-07 22:17 ` howarth at nitro dot med.uc.edu
2012-10-07 22:29 ` howarth at nitro dot med.uc.edu
2012-10-07 22:51 ` jeremyhu at macports dot org
2012-10-07 23:03 ` paolo.carlini at oracle dot com
2012-10-07 23:07 ` jeremyhu at macports dot org
2012-10-07 23:14 ` roblu2184 at gmail dot com
2012-10-07 23:15 ` paolo.carlini at oracle dot com
2012-10-07 23:19 ` roblu2184 at gmail dot com
2012-10-07 23:26 ` jeremyhu at macports dot org
2012-10-07 23:33 ` paolo.carlini at oracle dot com
2012-10-08  3:48 ` jeremyhu at macports dot org
2012-10-08  9:26 ` paolo.carlini at oracle dot com
2012-10-08 10:06 ` redi at gcc dot gnu.org
2012-10-08 11:00 ` redi at gcc dot gnu.org
2012-10-08 11:17 ` redi at gcc dot gnu.org
2012-10-08 13:47 ` howarth at nitro dot med.uc.edu
2012-10-08 14:03 ` howarth at nitro dot med.uc.edu
2012-10-08 14:33 ` redi at gcc dot gnu.org
2012-10-08 14:47 ` redi at gcc dot gnu.org
2012-10-08 15:14 ` [Bug libstdc++/54847] --enable-libstdcxx-time=yes doesn't find the functional nanosleep() " howarth at nitro dot med.uc.edu
2012-10-08 15:31 ` howarth at nitro dot med.uc.edu
2012-10-08 15:55 ` redi at gcc dot gnu.org
2012-10-08 16:03 ` redi at gcc dot gnu.org
2012-10-08 16:31 ` howarth at nitro dot med.uc.edu
2012-10-08 16:45 ` howarth at nitro dot med.uc.edu
2012-10-08 16:48 ` [Bug libstdc++/54847] --enable-libstdcxx-time=yes doesn't find the function " redi at gcc dot gnu.org
2012-10-08 17:04 ` howarth at nitro dot med.uc.edu
2012-10-08 17:16 ` redi at gcc dot gnu.org
2012-10-08 18:33 ` jeremyhu at macports dot org
2012-10-08 19:50 ` redi at gcc dot gnu.org
2012-10-08 20:10 ` jeremyhu at macports dot org
2012-10-08 20:31 ` howarth at nitro dot med.uc.edu
2012-10-08 20:42 ` redi at gcc dot gnu.org
2012-10-08 22:27 ` howarth at nitro dot med.uc.edu
2012-10-09  0:46 ` howarth at nitro dot med.uc.edu
2012-10-10 23:20 ` redi at gcc dot gnu.org
2012-11-06 11:35 ` redi 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-54847-4-dYvLsJwGRO@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).