2008/4/28 Mathieu Malaterre <[EMAIL PROTECTED]>:
> On Mon, Apr 28, 2008 at 5:24 PM, Eduardo M KALINOWSKI <[EMAIL PROTECTED]>
> wrote:
> > Mathieu Malaterre wrote:
> > > Should I simply assumed that gettid should not be used and instead
> > > replaced it with pthread_self as this should be the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/28/08 10:30, Mathieu Malaterre wrote:
> On Mon, Apr 28, 2008 at 5:24 PM, Eduardo M KALINOWSKI <[EMAIL PROTECTED]>
> wrote:
>> Mathieu Malaterre wrote:
>> > Should I simply assumed that gettid should not be used and instead
>> > replaced it wit
Mathieu Malaterre wrote:
> On Mon, Apr 28, 2008 at 5:24 PM, Eduardo M KALINOWSKI <[EMAIL PROTECTED]>
> wrote:
>
>> Mathieu Malaterre wrote:
>> > Should I simply assumed that gettid should not be used and instead
>> > replaced it with pthread_self as this should be the default on all
>> > lin
On Mon, Apr 28, 2008 at 5:24 PM, Eduardo M KALINOWSKI <[EMAIL PROTECTED]> wrote:
> Mathieu Malaterre wrote:
> > Should I simply assumed that gettid should not be used and instead
> > replaced it with pthread_self as this should be the default on all
> > linux/debian system ?
> >
>
> >From man
Mathieu Malaterre wrote:
> Should I simply assumed that gettid should not be used and instead
> replaced it with pthread_self as this should be the default on all
> linux/debian system ?
>
>From man gettid(2):
NOTES
Glibc does not provide a wrapper for this system call; call it
using
Yinghong Zhou wrote:
> Thank you very much for your reply!
>
> Your are absolute right. The wsmp was written by Fortran.
> After I added the underscore, I have new "undefined reference" coming up.
> Here is a few examples of them:
> : undefined reference to `ftn_i_jishft'
> ./lib/libwsmp64.a(tor
Hi Kevin:
Thank you very much for your reply!
Your are absolute right. The wsmp was written by Fortran.
After I added the underscore, I have new "undefined reference" coming up.
Here is a few examples of them:
: undefined reference to `ftn_i_jishft'
../lib/libwsmp64.a(torder.o)(.text+0x11f9): In
Yinghong Zhou wrote:
> I also used rtc() in my program. The linker doesn't report error on this
> one. Following is how I declare the functions in my program:
>
> extern "C" {
> void wssmp( int* N, int* IA, int* JA, double* AVALS, double* DIAG,
> int* PERM, int* INVP, doub
On Sat, 19 Jan 2002 17:09:27 -0300 Mike G <[EMAIL PROTECTED]> wrote:
> Hi all!
> I'm trying to compile a program and I get undefined reference to
> __ctype
> on the isdigit() function, it on woody machine. Any one got this ever? any
> idea?
>
> thanks in advance
Are you including all hea
On Sat, Jan 19, 2002 at 05:09:27PM -0300, Mike G wrote:
| Hi all!
| I'm trying to compile a program and I get undefined reference to
| __ctype on the isdigit() function, it on woody machine. Any one got
| this ever? any idea?
What's the code and what are the compiler options?
$ cat foo.c
#inclu
On Mon, Apr 16, 2001 at 09:17:13PM +0100, Oliver Elphick wrote:
> Can anyone offer a solution for this:
>
> gcc -pipe -L /home/olly/mypackages/eiflibs/eifpgsql/C -L
> /home/olly/mypackages/eiflibs/datetime/C edbgen1.o edbgen2.o edbgen3.o
> edbgen4.o -lgdk -lgtk -leifutils -leifpq -lpq
> /usr/lib
On Mon, Apr 16, 2001 at 09:17:13PM +0100, Oliver Elphick wrote:
| Can anyone offer a solution for this:
|
| gcc -pipe -L /home/olly/mypackages/eiflibs/eifpgsql/C -L
| /home/olly/mypackages/eiflibs/datetime/C edbgen1.o edbgen2.o edbgen3.o
| edbgen4.o -lgdk -lgtk -leifutils -leifpq -lpq
| /usr/lib
On Thu, 4 Sep 1997, Gonzalo A. Diethelm wrote:
> On Sep 3, 1997, at 13:47, Jason Gunthorpe wrote:
> > The trouble is that it doesn't recursively instantiate, ie if you use STL
> > and put the line
> >
> > template class vector;
> >
> > In some .cc file to force instantiation then you w
On Sep 3, 1997, at 13:47, Jason Gunthorpe wrote:
> I would like to point out that GCC doesn't explicitly instantiate too well
> when running with -fno-implicit-templates, which is what I would like to
> use in my sources..
That's a shame... Hopefully, egcs will do a better job.
> The trouble
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> I hope egcs fixes alot of problems like this :<
I believe it does, and again, you can solve all these problems with
the existing gcc and the repo patch. One thing I didn't mention
before was that you do need to compile your code with -frepo.
--
Rob
> On 03-Sep-97 Gonzalo A. Diethelm wrote:
> >
> >The only official way sanctioned by the upcoming C++ ANSI/ISO standard
> >to instantiate templates is to explicitly mention the types you want
> >to use for instantiation. All of the repository techniques that exist,
> >some better, some worse, are
On 03-Sep-97 Gonzalo A. Diethelm wrote:
>
>The only official way sanctioned by the upcoming C++ ANSI/ISO standard
>to instantiate templates is to explicitly mention the types you want
>to use for instantiation. All of the repository techniques that exist,
>some better, some worse, are not standard
> "Gonzalo" == Gonzalo A Diethelm <[EMAIL PROTECTED]> writes:
[Good advice on The Right Way to use templates]
Gonzalo> If your compiler supports explicit template instantiation
Gonzalo> with the standard 'template class MyClass;' mechanism
Gonzalo> (as g++ appears to), then this is what I woul
On Sep 2, 1997, at 20:11, Orn E. Hansen wrote:
> I tried using the 'template class ...' and that did the trick,
> but I agree that it is of limited use though. Kinda limits the
> generality of your code, if you have to know the type ofevery
> template class before hand. So, I'm going to lo
On 8859 xxx 2001, Orn E. Hansen wrote:
^^
Orn, your mailer is formatting dates in a way that pine doesn't understand
:<
> On 02-Sep-97 David B. Teague wrote:
> >
> >you will find a big section that explains how to do the template
> >instantantiation with the template class and implementa
On 02-Sep-97 David B. Teague wrote:
>
>you will find a big section that explains how to do the template
>instantantiation with the template class and implementation in separate
>files.
>
>There are pragmas for this, and the technique taht Borland C++ uses for
>this works (according to the info file
I found the pointer to the template repository patch for gcc 2.7.*.
It's ftp.cygnus.com/pub/g++/gcc-2.7.*-repo.gz.
--
Rob
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
I tried using the 'template class ...' and that did the trick,
but I agree that it is of limited use though. Kinda limits the
generality of your code, if you have to know the type ofevery
template class before hand. So, I'm going to look up the site
you suggested and try their snapshot.
Tru
I took your program example and compiled it, and it works... but here comes the
groovy part. If you take the same program and split it...
|---begin temp.C|
#include "temp.h"
template
ancestor::ancestor(T x)
{
cout << "ancestor()" << endl;
myvar = x;
}
template
ancestor::~ancestor()
{
Gilbert Laycock <[EMAIL PROTECTED]> writes:
> I believe that this (and many other) problems have been fixed for
> gcc/g++ 2.8 which is apparently nearly-but-not-quite-ready for release
> (and has been for some time now).
You can also solve this problem in 2.7.2* by using the repo patch
(available
Hi Gilbert and Orn:
Read info gcc:
use the command
control s template instantiation
you will find a big section that explains how to do the template
instantantiation with the template class and implementation in separate
files.
There are pragmas for this, and the technique taht Borland C++
> Orn E Hansen <[EMAIL PROTECTED]> writes:
> The program compiles without errors, but when the linker is to link the
> object files, it is persistent that the reference to 'something' within
> the main program is undefined to 'ancestor<...>'. Every reference to
> the object 'ancestor' is
Are you linking with gcc or g++? Try g++ for the link phase.
Here is the output I get for a simple test program:
-- Begin temp.C
#include
template
class ancestor {
private:
T myvar;
public:
ancestor(T x) { cout << "ancestor()" << endl; myvar = x; }
~ancestor() { cout << "~
28 matches
Mail list logo