Hi, Jan

This probably is expected for AIX 4.3.  I am surprised that this
occurs for AIX 5.3 because I thought that weak support was available
after AIX 5.1 or AIX 5.2.

I think that the weak support and MAKE_DECL_ONE_ONLY are required for
proper operation now.

Maybe I should formally deprecate AIX 4.3.

Thanks, David


On Thu, Sep 4, 2014 at 4:39 AM, Jan-Benedict Glaw <jbg...@lug-owl.de> wrote:
> Hi!
>
> I should have sent this earlier, but maybe you're still interested:
>
> [...]
> g++ -c   -g -O2 -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE  -fno-exceptions 
> -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing 
> -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual 
> -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Werror 
> -fno-common  -DHAVE_CONFIG_H -I. -I. -I../../../gcc/gcc -I../../../gcc/gcc/. 
> -I../../../gcc/gcc/../include -I../../../gcc/gcc/../libcpp/include 
> -I/opt/cfarm/mpc/include  -I../../../gcc/gcc/../libdecnumber 
> -I../../../gcc/gcc/../libdecnumber/dpd -I../libdecnumber 
> -I../../../gcc/gcc/../libbacktrace    -o rs6000.o -MT rs6000.o -MMD -MP -MF 
> ./.deps/rs6000.TPo ../../../gcc/gcc/config/rs6000/rs6000.c
> ../../../gcc/gcc/config/rs6000/rs6000.c: In function 'bool 
> rs6000_declare_alias(symtab_node*, void*)':
> ../../../gcc/gcc/config/rs6000/rs6000.c:29707:50: error: 'ASM_WEAKEN_DECL' 
> was not declared in this scope
>   ASM_WEAKEN_DECL (data->file, n->decl, name, NULL);
>                                                   ^
> make[2]: *** [rs6000.o] Error 1
>
>
> I see this at least for rs6000-ibm-aix5.3.0 (eg.
> http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=350500)
> and rs6000-ibm-aix4.3
> (http://toolchain.lug-owl.de/buildbot/show_build_details.php?id=350449).
>
> MfG, JBG
>
> --
>       Jan-Benedict Glaw      jbg...@lug-owl.de              +49-172-7608481
> Signature of:               The real problem with C++ for kernel modules is:
> the second  :                                 the language just sucks.
>                                                    -- Linus Torvalds

Reply via email to