Re: [E-devel] Strange warnings & compiling errors

[Nathan A. S. <na...@co...>]

On Sun, 2006-01-01 at 17:34 +0900, David Stevenson wrote:
> 
> 
> On 1/1/06, Nathan A. Smith <na...@co...> wrote:
>         Hi guys,
>         
>         I have recently noticed I am getting a lot of strange (to me)
>         compiling
>         errors and warnings.  I was hoping I could get one of you
>         smart people
>         to point me in the right direction to fix them.
>         
>         the warnings (I started getting them when compiling evas --
>         and 
>         everthing that followed)
>         
>         an example follows:
>         
>         ecore_value.c:31: warning: redeclaration of
>         'ecore_prime_table' with
>         different visibility (old visibility preserved)
>         Ecore_Data.h:41: warning: previous declaration of
>         'ecore_prime_table' 
>         was here
>         
>         
>         These warnings would be repeated for different lines more than
>         a hundred
>         times -- no kidding.
> 
> I was seeing those too when I rebuilt everything earlier today.
> 
> Further, e17 was seg'ing when the moon module's e_modapi_shutdown
> function was called. I think this was a result of the visibility
> changes ,.. not sure though.
> 
> Anyway when I rebuilt the moon module, those visibility warnings were
> appearing there too, so I 
> 1) mimicked raster's EAPI changes from 4 days ago into the moon's
> e_mod_main.h, and additionally 
> 2) found that putting "EAPI" in front of all the module api function
> declarations in e_mod_main.c got rid of the warnings as well. 
> 
> I tried using both these gcc versions:
> gcc (GCC) 3.3.6 (Debian 1:3.3.6-10)
> gcc (GCC) 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)
> ...and there are no more warnings with either after making those
> changes...
> 
> I don't understand all this too well, so hopefully someone who does
> can confirm that these EAPI changes in e_mod_main.c were the right
> thing to do. 
> Anybody?
> (If so I'll make a new version of the moon module with these changes
> shortly, for any moon module fans)
> 
for evas: 

Vincent's suggestion of removing line 17 from 
evas_common.h (in ../evas/src/lib/include/) does allow evas to compile.
I will have to look for similar lines in other libraries -- and talk to
Raster to see if this would be a good fix.

Nasa



> Nothing like a little fun to start the new year :-) 
> 
> 
>         which finally lead to this error:
>         
>         /usr/bin/ld: .libs/ecore.o: relocation R_X86_64_PC32 against 
>         `setlocale@@GLIBC_2.2.5' can not be used when making a shared
>         object;
>         recompile with -fPIC
>         /usr/bin/ld: final link failed: Bad value
> 
> This I did not see.
> 
> Regards!
> David 
> 
>