translate.o udptl.o ulaw.o utils.o version.o xml.o xmldoc.o
editline/libedit.a db1-ast/libdb1.a - asterisk
astobj2.o: In function `ast_atomic_fetchadd_int':
/usr/src/asterisk-1.8.3/include/asterisk/lock.h:589: undefined reference to
`__sync_fetch_and_add_4'
/usr/src/asterisk-1.8.3/include/asterisk
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 default on
':
gettid.c:(.text+0xe): undefined reference to `gettid'
collect2: ld returned 1 exit status
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 ?
Thanks,
--
Mathieu
--
To UNSUBSCRIBE, email
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
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 gettid(2):
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
linux/debian
-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 with
txTask.o: In function `TxMgrTask::TxMgrTask(RWCString, int,
int)':txTask.C:(.text+0x6b37): undefined reference to
`DDMSDBAgentManagerDDMSUsn, unsigned
long::DDMSDBAgentManager(TxMgrTask*, int, int)'txTask.o: In function
`TxMgrTask::TxMgrTask(RWCString, int, int)':txTask.C:(.text+0x7e47
Roberto Sanchez wrote:
Artur Makówka wrote:
does anyone know why i have a lot of such messages
:/root/source/apache2-2.0.55/build-tree/apache2/support/ab.c:521:
undefined reference to `BIO_printf'
:/root/source/apache2-2.0.55/build-tree/apache2/support/ab.c:605:
undefined reference
Artur Makówka wrote:
compiling 2.0.54 gives the same results (well, at least it also stops on
some errors)
i just want to recompile apache to match my processor architecture
optimization and such, besides i want to change few configure options.
Of course i havent changed them yet, now i
does anyone know why i have a lot of such messages
:/root/source/apache2-2.0.55/build-tree/apache2/support/ab.c:521:
undefined reference to `BIO_printf'
:/root/source/apache2-2.0.55/build-tree/apache2/support/ab.c:605:
undefined reference to `SSL_do_handshake'
:/root/source/apache2-2.0.55/build
Artur Makówka wrote:
does anyone know why i have a lot of such messages
:/root/source/apache2-2.0.55/build-tree/apache2/support/ab.c:521:
undefined reference to `BIO_printf'
:/root/source/apache2-2.0.55/build-tree/apache2/support/ab.c:605:
undefined reference to `SSL_do_handshake'
:/root
Hi all:
I am trying to compile sparse matrix solver, wsmp, in my program. But I
always get following error message:
/home/YZhou/Cprogram/sparse_test/lss.cpp:108: undefined reference to
`wsetnobigmal'
/tmp/ccYLWe54.o(.text+0x1f5):/home/YZhou/Cprogram/sparse_test/lss.cpp:110:
undefined
reference
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, double* B,
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
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(torder.o
español
que hable de como usar el USB con un microcontrolador (PIC16C745) y
GNU/Linux. Tuve un contratiempo y traté de solucionarlo, no me
funcionó, fui a internet (por que hasta eso no me caso con google) y
busqué, te invito a que le pongas en google undefined reference y
verás cuantos resultados
busqué, te invito a que le pongas en google undefined reference y
verás cuantos resultados te salen y en los 20 primeros te apuesto a
que no encuentras una solución real a mi problema, ni siquiera un FAQ
de los que tanto alarde haces. Según yo, lo que pregunté no es algo
trivial y no dejará de
17 y bajando.
Realmente es un error de nivel básico, no viene mal leer algún
libro antes de ponerse a programar, o en su caso ir a alguna clase.
Aunque parezca sorprendente google no proporciona todo el conocimiento
necesario y menos en el primer enlace.
No os ofendais pero es que me
Nombre para nada, no me cambiaria a windocs ni por un santiaguito. Se
necesita mucho más que eso. Además en ningun momento los amenace. Lo
que sigo sin entender, es que suponiendo que sea algo de primaria, que
insisito para mi no lo es, si simplemente lo catalogan como algo
simple y no merece ni
On Sat, 30 Apr 2005, coin wrote:
¿para que viene santiaguito [...]
Pues por si no te diste cuenta, para recomendarte un buen libro sobre C.
Si eso te fastidia tanto, pues lo siento, pero te aseguro que no voy
por ahí recomendando libros sólo para fastidiar a la gente (no soy tan
malo).
El
Ya lo resolví. No se si es la mejor forma de hacerlo pero funcionó.
Agradezco a este pequeño manual que me encontré
http://www.macprogramadores.org/beos/tutoriales/THD/herramientasgnu/gcc/gcc.html
Lo que hice fue solo agregarle -l y el nombre de la libreria.
gcc -o prueba1 prueba1.c -lusb
Pero
On Fri, 29 Apr 2005, coin wrote:
Ya lo resolví. No se si es la mejor forma de hacerlo pero funcionó.
Agradezco a este pequeño manual que me encontré
http://www.macprogramadores.org/beos/tutoriales/THD/herramientasgnu/gcc/gcc.html
Lo que hice fue solo agregarle -l y el nombre de la libreria.
Santiago Vila wrote:
On Fri, 29 Apr 2005, coin wrote:
Ya lo resolví. No se si es la mejor forma de hacerlo pero funcionó.
Agradezco a este pequeño manual que me encontré
http://www.macprogramadores.org/beos/tutoriales/THD/herramientasgnu/gcc/gcc.html
Lo que hice fue solo agregarle -l y el nombre
El include pone las funciones disponibles para el programa en si pero el
linkaje con la libreria es otra cosa, Por cierto... alguien no conoce
una *buena* lista en donde se hablen de estos tópicos.
Las listas no deberían dedicarse a los tópicos, que para eso ya están
las FAQs. Si te refieres a
Tengo un cuate que hace ingeniería lingüista y me habló de proyectos
tan interesantes como el de hacer un diccionario al revés, es decir,
le metes el concepto y te entrega la palabra. Esto en cualquier
momento se va a convertir en el bum de no solo cuestiones didácticas
como el proyecto de
On Fri, 29 Apr 2005, coin wrote:
Tengo un cuate que hace ingeniería lingüista y me habló de proyectos
tan interesantes como el de hacer un diccionario al revés, es decir,
le metes el concepto y te entrega la palabra. Esto en cualquier
momento se va a convertir en el bum de no solo cuestiones
. Tuve un contratiempo y traté de solucionarlo, no me
funcionó, fui a internet (por que hasta eso no me caso con google) y
busqué, te invito a que le pongas en google undefined reference y
verás cuantos resultados te salen y en los 20 primeros te apuesto a
que no encuentras una solución real a mi
On Fri, 29 Apr 2005, coin wrote:
Según yo, lo que pregunté no es algo
trivial y no dejará de serlo. La página que encontré y que poste
respondiendome a mi pregunta, la encontré buscado otras cosas. Es más
me atrevo a lanzar el reto de que si más de 20 personas aseguran que
lo que pregunté es
On Thu, Apr 03, 2003 at 01:01:10AM +0200, Andreas Pakulat wrote:
...
Das Problem ist seit Version 3.8.3 gelöst und hat irgendwas mit usigned
char's zu tun. Fragt mich da nicht weiter, sucht das mal im Netz. Ich
hab mich dafür nicht weiter interessiert. Bugreport gegen 3.8.2 hab ich
;
| }
| }
| return 0;
| }
und so ruf ich den gcc-2.95 auf:
gcc -o a a.cpp -lid3
Sollte ja ausreichen oder?!
Raus kommt sowas:
gcc -o a -lid3 a.cpp
| /tmp/ccVslXkL.o(.text+0x1c): In function `main':
| : undefined reference to `ID3_Tag::ID3_Tag(char const *)'
| /tmp/ccVslXkL.o(.text+0x30
--JYK4vJDZwFMowpUq
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On 02.Apr 2003 - 23:38:53, Andreas Pakulat wrote:
Hi,
=20
das Problem ist zwar eventuell nicht Debian spezifisch (vielleicht ist
auch die Lib in dem Paket
\
-o vmlinux
drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols in discarded
section .text.exit'
make[1]: ** [vmlinux] Erro 1
make[1]: Leaving directory `/usr/src/kernel-source-2.4.16'
make: ** [stamp-build] Erro 2
funes:/usr/src
\
-o vmlinux
drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols in
discarded section .text.exit'
make[1]: ** [vmlinux] Erro 1
make[1]: Leaving directory `/usr/src/kernel-source-2.4.16'
make: ** [stamp-build] Erro 2
funes:/usr/src/kernel-source-2.4.16
test.c
/tmp/cccjQUKt.o: In function `main':
/tmp/cccjQUKt.o(.text+0x60): undefined reference to `singal'
/tmp/cccjQUKt.o(.text+0x72): undefined reference to `singal'
collect2: ld returned 1 exit status
Das Listing:
schnipp---
#include stdio.h
#include sys
Hallo,
Am Donnerstag, 13. Juni 2002 16:27 schrieb Christoph H.:
singal(SIGINT, catcher);
singal(SIGQUIT, catcher);
ersetz das mal mit:
signal(SIGINT, catcher);
signal(SIGQUIT, catcher);
ich verkneif mir jetzt die Frage, ob du auch C programmieren kannst
,wenn du solche Programme
Sers,
Christoph H. [EMAIL PROTECTED] writes:
[...]
Der Kompilierversuch:
$ gcc -o test test.c
/tmp/cccjQUKt.o: In function `main':
/tmp/cccjQUKt.o(.text+0x60): undefined reference to `singal'
/tmp/cccjQUKt.o(.text+0x72): undefined reference to `singal
ich verkneif mir jetzt die Frage, ob du auch C programmieren kannst
,wenn du solche Programme schon kriegst und versucht sie zu verstehen
irgendwie is heut nicht mein tag, sorry :-/
--
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an
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
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
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 headers
Hello!
Could anybody posibly tell me why some source codes using crypt() with
shadowed passwords crush linker?
I get an error:
--
xxx.o: In function 'yyy'
ccc.o(.text+0xMMM): undefined reference to 'crypt
On Thu, 24 May 2001, IronHand wrote:
I Hello!
I
I Could anybody posibly tell me why some source codes using crypt() with
I shadowed passwords crush linker?
I I get an error:
I --
I xxx.o: In function 'yyy'
I ccc.o(.text+0xMMM): undefined reference
IronHand [EMAIL PROTECTED] writes:
IH Could anybody posibly tell me why some source codes using crypt() with
IH shadowed passwords crush linker?
Make sure you're linking against the crypt library (-lcrypt shows up
on the link command line).
--
David Maze [EMAIL PROTECTED]
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/libcrypto.so.0.9.6: undefined reference to `atexit'
collect2: ld returned
/lib/libcrypto.so.0.9.6: undefined reference to `atexit'
| collect2: ld returned 1 exit status
|
| But if I compile a very small program that calls atexit() directly, it has
| no problem finding it, even though I specify no library at all.
| As far as I can see, atexit() is part of libc6
/libcrypto.so.0.9.6: undefined reference to `atexit'
collect2: ld returned 1 exit status
The libssl (libcrypto) was compiled with a buggy version of gcc. It
needs to be recompiled. The version in unstable and (afaik) woody, are
ok (2.95.3-9 or later
`mi_milteropen':
listener.o(.text+0x246): undefined reference to `__inet_addr'
/usr/lib/libmilter/libmilter.a(engine.o): In function `st_connectinfo':
engine.o(.text+0x714): undefined reference to `__inet_aton'
collect2: ld returned 1 exit status
make: *** [sample] Error 1
Before this I changed
I'm getting these errors when compiling stuff:
/usr/X11R6/lib/libX11.so.6: undefined reference to `getpwnam_r@@GLIBC_2.0'
/usr/X11R6/lib/libX11.so.6: undefined reference to `getpwuid_r@@GLIBC_2.0'
I upgraded my libc from stable to unstable last night, so I'm
guessing that's the problem. How
Cuando a mí me ha pasado eso lo he solucionado poniendo en el Makefile
LIBS= -lcrypt
Saludos
el
siguiente
mensaje:
bash-2.01$ make
cc -g -Wall -lpq socket.o text.o db.o main.o -o prueba
/usr/lib/libpq.so: undefined reference to `crypt'
make: *** [done_mud] Error 1
Está muy clarito. Te falta poner -lcrypt para que enlace con la librería.
/usr/lib/libcrypt.a
/usr/lib/libcrypt.so
--- Jordi Roman Mejias [EMAIL PROTECTED] wrote:
EO! Ni puñetera idea de que era
Shaval, hazme un favo's, no te compres un circo con enanos
que resultado obtienes de ?
hardtech= select count(*) from vglobal2 where id557;
hardtech= select count(*) from vglobal2 where
-lpq socket.o text.o db.o main.o -o prueba
/usr/lib/libpq.so: undefined reference to `crypt'
make: *** [done_mud] Error 1
Supongo que me falta alguna libreria de encriptacion. La cuestion es que al
instalar el paquete no me advirtio/recomendo/pidio otras dependencias ... no
deberia haberme pedido
-Mensaje original-
De: Ricard P.G. [SMTP:[EMAIL PROTECTED]
Enviado el: jueves 14 de octubre de 1999 12:34
Para: Lista de Debian
Asunto: undefined reference to `crypt'
Buenas,
bash-2.01$ make
cc -g -Wall -lpq socket.o text.o db.o main.o -o prueba
/usr/lib/libpq.so
Ricard P.G. dijo:
Me he puesto a provar de programar algo en C mediante la libreria libpq que
proporciona postgres. La cuestion es que cuando compilo me aparece el
siguiente
mensaje:
bash-2.01$ make
cc -g -Wall -lpq socket.o text.o db.o main.o -o prueba
/usr/lib/libpq.so: undefined
--- Jaime E. Villate [EMAIL PROTECTED] wrote:
ya intentaste con:
cc -g -Wall -lpq -lcrypt sockett.o text.o db.o main.o -o prueba
Funciona !!! I love youuu!!! ahora en serio, muchas gracias, ya me
veia actualizandome a potato
libcrypt.a viene con libc6-dev.
Si si, ya la
it. This is
the error:
/home/bob/lib/linux/libkernel.a(swsplsur.o): In function
`sweep_spl_sur::deep_copy(pointer_map *) const':
swsplsur.o(.text+0x537): undefined reference to `__eh_pc'
swsplsur.o(.text+0x56a): undefined reference to `__eh_pc'
What is __eh_pc? and why can I not find it in any of the standard
reference to `cout'
t.o(.text+0x12): undefined reference to `ostream::operator(char const
*)'
make: *** [t] Error 1
This is a linker unresolved reference, right? I need to pass a command
line switch to the linker to tell it the library, right?
Okay, how can I relate a given header
++-c t.cc -o t.o
cc t.o -o t
t.o: In function `main':
t.o(.text+0xd): undefined reference to `cout'
t.o(.text+0x12): undefined reference to `ostream::operator(char
const
*)'
make: *** [t] Error 1
This is a linker unresolved reference
On Tue, Apr 06, 1999 at 11:41:30PM -0500, Matt Miller wrote:
Several things:
1. You don't need to compile the object files and then link them in two
seperate steps.
2. You need to #include iostream.h
3. You need to link with the stdc++ library to get all of the C++ I/O classes
The command line
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 vectorint;
In some .cc file to force instantiation then you will not
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 is
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 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 look
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 MyClassint;' mechanism
Gonzalo (as g++ appears to), then this is what I would do:
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 and
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
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 'ancestorint' is reported
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
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 at
Temp
tempMain.o: In function `main':
tempMain.o(.text+0xe): undefined reference to `ancestorint::ancestor(int)'
tempMain.o(.text+0x1a): undefined reference to `ancestorint::dump(void)'
tempMain.o(.text+0x2a): undefined reference to `ancestorint::~ancestor(void)'
...and that's weird
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.
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] .
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 files). I
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 implementation in
I've encountered a condition in GNU C++, where I define the following
template function...
templateclass T
class ancestor {
private:
...
public:
ancestor()
~ancestor()
};
templateclass T
ancestorT::ancestor()
{
...
}
...
and use it in a main program...
main()
{
ancestorint something;
temp.C -o temp
/tmp/cca021531.o: In function `ancestorint::~ancestor(void)':
/tmp/cca021531.o(.text+0x6d): undefined reference to `endl(ostream )'
/tmp/cca021531.o(.text+0x77): undefined reference to `cout'
/tmp/cca021531.o(.text+0x7c): undefined reference to
`ostream::operator(char const *)'
/tmp
/jhankins/Temp/tcl-7.6p2/unix/libtcl7.6.a(tclUnixChan.o): In function
`TcpGetOptionProc':
tclUnixChan.o(.text+0xfdc): undefined reference to `__inet_ntoa'
tclUnixChan.o(.text+0x1015): undefined reference to `__inet_ntoa'
tclUnixChan.o(.text+0x10cb): undefined reference to `__inet_ntoa'
tclUnixChan.o
Hello,
I am still Debian1.1 - compiling a C++ program, which used to
compile cleanly only a few weeks ago, gives me the following
error message:
/lib/libm.so.5: undefined reference to '__getfpucw'
Well, if you are pure Debian-1.1, and didn't upgrade anything between
a few weeks
Hello,
I am still Debian1.1 - compiling a C++ program, which used to
compile cleanly only a few weeks ago, gives me the following
error message:
/lib/libm.so.5: undefined reference to '__getfpucw'
Do I need to upgrade any libraries ?
Can anybody help me sort this out please
80 matches
Mail list logo
