public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "georg@schorsch-tech.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/66359] Regex Fails to match
Date: Mon, 01 Jun 2015 15:19:00 -0000	[thread overview]
Message-ID: <bug-66359-4-4rquPttsjb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66359-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66359

--- Comment #3 from georg@schorsch-tech.de ---
I tried to apply that revision to gcc-4.9.2. Now i get the following error.

g++ -DUSE_STD -std=c++11 main.cpp 
In file included from
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.2/include/g++-v4/regex:58:0,
                 from main.cpp:2:
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.2/include/g++-v4/bits/regex.h:65:5:
warning: inline function 'std::shared_ptr<std::__detail::_NFA<_TraitsT> >
std::__detail::__compile_nfa(const typename _TraitsT::char_type*, const
typename _TraitsT::char_type*, const _TraitsT&,
std::regex_constants::syntax_option_type) [with _TraitsT =
std::regex_traits<char>; typename _TraitsT::char_type = char]' used but never
defined
     __compile_nfa(const typename _TraitsT::char_type* __first,
     ^
/tmp/ccMywN21.o: In function `std::basic_regex<char, std::regex_traits<char>
>::basic_regex<char const*>(char const*, char const*,
std::regex_constants::syntax_option_type)':
main.cpp:(.text._ZNSt11basic_regexIcSt12regex_traitsIcEEC2IPKcEET_S6_NSt15regex_constants18syntax_option_typeE[_ZNSt11basic_regexIcSt12regex_traitsIcEEC5IPKcEET_S6_NSt15regex_constants18syntax_option_typeE]+0xd5):
undefined reference to
`std::shared_ptr<std::__detail::_NFA<std::regex_traits<char> > >
std::__detail::__compile_nfa<std::regex_traits<char>
>(std::regex_traits<char>::char_type const*, std::regex_traits<char>::char_type
const*, std::regex_traits<char> const&,
std::regex_constants::syntax_option_type)'
collect2: error: ld returned 1 exit status


I added my applied patch too. I copied the files from your revision to my tree
and used git to create that patch.


  parent reply	other threads:[~2015-06-01 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01  9:53 [Bug libstdc++/66359] New: " georg@schorsch-tech.de
2015-06-01  9:54 ` [Bug libstdc++/66359] " georg@schorsch-tech.de
2015-06-01 11:46 ` timshen at gcc dot gnu.org
2015-06-01 15:19 ` georg@schorsch-tech.de [this message]
2015-06-01 15:25 ` georg@schorsch-tech.de
2015-06-05  4:59 ` timshen at gcc dot gnu.org
2015-06-05  5:06 ` timshen at gcc dot gnu.org
2023-07-20 11:47 ` 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-66359-4-4rquPttsjb@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).