This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ebcdic support for binutils...


On Mon, Dec 10, 2001 at 09:26:58PM -0500, DJ Delorie wrote:
> 
> If configure doesn't pick up your linker, you can do this:
> 
> 	LD=whatever ../src/configure

oh yeah... i knew that... *never mind*... 

> Why no patch for libiberty/hex.c also?

I looked at it, at least in 2.11.2, and libiberty/hex.c looked like:

#include "libiberty.h"

char _hex_value[_hex_array_size];

void hex_init ()
{
	int i;
	for (i = 0; i < _hex_array_size; i++)
		_hex_value[i] = _hex_bad;
  	for ( i = 0; i < 10; i++ )
		_hex_value['0' + i] = i;
	for ( i = 0; i < 6; i++ )
		_hex_value['a' + i] = _hex_value['A' + i] = 10 + i;
}

which seems to be portable to me...

Anyways, again, it configures, and I've gotten to the point where it says:

*** ld does not support target i370-ibm-openedition
*** see ld/configure.tgt for supported targets
Configure in /u/mdss/esp5/builds/binutils-2.11.2.new/ld failed, exiting.

Looking inside of configure.txt, I see a bunch of emulation modes. However,
the values for targ_emul that points to a shell script containing emulation
parameters for the given system.

So - how do you find out what these parameters are supposed to be? Or, more 
important, how do you make use of these parameters (ie: what source do you get 
them from?)

Ed


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]