Date: Tue, 22 Apr 2014 22:36:57 +0200 From: Riccardo Veraldi <riccardo.veraldi@gmail.com> To: sparc64@freebsd.org Subject: Re: libsoup Message-ID: <5356D2E9.4010009@gmail.com> In-Reply-To: <20140422180040.GD43976@funkthat.com> References: <5350D21A.5050800@gmail.com> <25617748.123.1397978390159.JavaMail.craig@w520> <53569D98.1040507@gmail.com> <20140422172251.GC43976@funkthat.com> <5356A743.9010300@gmail.com> <20140422180040.GD43976@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I did it an there are no complains... there is only a warning which was there before. test.c:4: warning: 'g_type_init' is deprecated (declared at /usr/local/include/glib-2.0/gobject/gtype.h:669) Craig compiling on his UltraSparc IIe does not have my problem... On 4/22/14 8:00 PM, John-Mark Gurney wrote: > Riccardo Veraldi wrote this message on Tue, Apr 22, 2014 at 19:30 +0200: >> On 4/22/14 7:22 PM, John-Mark Gurney wrote: >>> Riccardo Veraldi wrote this message on Tue, Apr 22, 2014 at 18:49 +0200: >>>> seems there is a problem with strcmp somewhere... >>> It's probably being passed a bogus pointer... >>> >>>> this happens on my Sun Blade 1000 UltraSPARC IIIcu >>>> >>>> here I reproduced the problem. >>> are you sure it isn't a problem where the prototype isn't in scope, >>> and so strcmp or other function is getting/returning an int (32bits) >>> instead of a pointer (64bits)? The C standard states that if there >>> isn't a prototype in scope it's assumed to always be an int... >> maybe... but how can I fix it then ? >> to succesfully compile libsoup I had to disable the configure script so >> that it won't compile the test program... >> bad idea but at least it goes on... > Try adding -Wimplicit-function-declaration to the gcc command and see > if it complains about something... If it does complain, like: > trc.c: In function 'main': > strc.c:5: warning: implicit declaration of function 'strcmp' > strc.c:5: warning: implicit declaration of function 'f' > > you should report it to the maintainers that it's not including the > correct headers... >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5356D2E9.4010009>