From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Sherrill To: Ian Lance Taylor Cc: gas2@cygnus.com Subject: Re: binutils 2.9 powerpc-rtems breakage Date: Tue, 14 Apr 1998 11:58:00 -0000 Message-id: References: <199804141821.OAA16222@subrogation.cygnus.com> X-SW-Source: 1998/msg00118.html On Tue, 14 Apr 1998, Ian Lance Taylor wrote: > OK, so why isn't elf32-powerpcle in your target list? I do not know. I have not been tinkering with anything. In fact, bfd/config.bfd has this: powerpc-*-*bsd* | powerpc-*-elf* | powerpc-*-sysv4* | powerpc-*-eabi* | \ powerpc-*-solaris2* | powerpc-*-linux-gnu* | powerpc-*-rtems*) targ_defvec=bfd_elf32_powerpc_vec targ_selvecs="rs6000coff_vec bfd_elf32_powerpcle_vec bfd_powerpcle_pei_vec bfd_powerpc_pei_vec bfd_powerpcle_pe_vec bfd_powerpc_pe_vec ppcboot_vec" So anything on powerpc-eabi and powerpc-rtems should behave the same. > It would normally be there because of a -DSELECT_VECS argument when > targets.c was compiled. OK. > Are you using shared libraries by any chance. Somebody has already > pointed out a shared library problem in the 2.9 release: the name of > the library does not include the target name, so if you build and > install BFD more than once using --enable-shared, then the new library > will overwrite the old one. I have not configured with --enable-shared. So if it happened, it was the default case. I am on a RedHat x86 linux box if that makes any difference. I build a lot of targets but always use different --prefix options. I don't think this problem is mine but it could be. Is there anything else I could look at in gdb to figure out which vectors are available? Would that be a clue? > Personally, I think the right solution is to just build BFD once using > --enable-targets, but building it multiple ones ought to work as well, > so this is a bug. I have managed to build all the RTEMS configuration except the mips64orion and powerpc ones. Both of them are showing problems during multilib builds of libgcc*.a. --joel