public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* g++ (egcs)
@ 2001-02-07  3:32 Corbisiero, Raffaele (Factiva)
  2001-02-07  4:01 ` Alexandre Oliva
  0 siblings, 1 reply; 4+ messages in thread
From: Corbisiero, Raffaele (Factiva) @ 2001-02-07  3:32 UTC (permalink / raw)
  To: gcc-help

Hi,

I have just built egcs 1.2 for tru64. I am trying to use/declare
an STL of;

	basic_string<unsigned char> data;

I keep getting a link error of;
Unresolved
basic_string<unsigned char, string_char_traits<unsigned char>,
__default_alloc_template<0,0> >::nilRep

Please help!....what have I done wrong

Raffaele

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: g++ (egcs)
  2001-02-07  3:32 g++ (egcs) Corbisiero, Raffaele (Factiva)
@ 2001-02-07  4:01 ` Alexandre Oliva
  0 siblings, 0 replies; 4+ messages in thread
From: Alexandre Oliva @ 2001-02-07  4:01 UTC (permalink / raw)
  To: Corbisiero, Raffaele (Factiva); +Cc: gcc-help

On Feb  7, 2001, "Corbisiero, Raffaele (Factiva)" <Raffaele.Corbisiero@factiva.com> wrote:

> I have just built egcs 1.2 for tru64.

Huh?  There's no such thing as egcs 1.2.  Maybe you meant 1.1.2?  In
this case, it's a very old release.  How about giving GCC 2.95.2 a
try?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: g++ (egcs)
  2001-02-07  8:36 Corbisiero, Raffaele (Factiva)
@ 2001-02-07  8:42 ` Alexandre Oliva
  0 siblings, 0 replies; 4+ messages in thread
From: Alexandre Oliva @ 2001-02-07  8:42 UTC (permalink / raw)
  To: Corbisiero, Raffaele (Factiva); +Cc: gcc-help

On Feb  7, 2001, "Corbisiero, Raffaele (Factiva)" <Raffaele.Corbisiero@factiva.com> wrote:

> I have now tried gcc 2.95.2 and it too gives me the same error...

Then you'll probably have to do some explicit instantiation.  Since
Tru64 doesn't support weak symbols, GCC won't implicitly instantiate
data symbols such as nilRep.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: g++ (egcs)
@ 2001-02-07  8:36 Corbisiero, Raffaele (Factiva)
  2001-02-07  8:42 ` Alexandre Oliva
  0 siblings, 1 reply; 4+ messages in thread
From: Corbisiero, Raffaele (Factiva) @ 2001-02-07  8:36 UTC (permalink / raw)
  To: 'Alexandre Oliva'; +Cc: gcc-help

I have now tried gcc 2.95.2 and it too gives me the same error... (yes I did
mean egcs 1.1.2)

-----Original Message-----
From: Alexandre Oliva [ mailto:aoliva@redhat.com ]
Sent: 07 February 2001 12:02
To: Corbisiero, Raffaele
Cc: gcc-help@gcc.gnu.org
Subject: Re: g++ (egcs)


On Feb  7, 2001, "Corbisiero, Raffaele (Factiva)"
<Raffaele.Corbisiero@factiva.com> wrote:

> I have just built egcs 1.2 for tru64.

Huh?  There's no such thing as egcs 1.2.  Maybe you meant 1.1.2?  In
this case, it's a very old release.  How about giving GCC 2.95.2 a
try?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2001-02-07  8:42 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-02-07  3:32 g++ (egcs) Corbisiero, Raffaele (Factiva)
2001-02-07  4:01 ` Alexandre Oliva
2001-02-07  8:36 Corbisiero, Raffaele (Factiva)
2001-02-07  8:42 ` Alexandre Oliva

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).