Search:

My latest thoughts are to use Objective-C code to write a class that could open the testfile as well as pass the other arguments to the program at run time rather than compile time. Does anyone have...

The problem I run in to is that the test file (which is now an executable) needs to be an argument to the main program. For instance, the Main program takes arguments of a testfile, input file, etc....

Yes I could read the files, but like you said the code is machine specific. Since the i686 creates .o files when it compiles a program, I figured that was the way to go.

The files were originally...

Would the dlopen() command work if the file was converted to a lib file?

I have an exe program that requires several arguments to be passed to it, including a test file, input/output file, errorfile, print level, etc. They are passed to the executable by using an .rc...

Thanks, I'll look into it some more

Doing objdump on working files shows that the files are of the same form.

I do have __attribute__ syntax, of the following form:


__attribute__ ((section ("GPARMS"))) struct ConfigTableType...

Hmm...I seem to be able to compile other programs though. I suppose I will try to find and install the latest version of binutils?

Is there a better form for the makefile? I just used a template sort of thing.

What info (flags) do you want to see from the objdump? Here's the output from objdump -s Esx.o:



$ objdump -s...

Here is the Makefile I am using:



bin_PROGRAMS = Ddx


SOURCE_DIR = $(top_srcdir)
SOURCE_INCLUDE_DIR = $(SOURCE_DIR)/../../include
SOURCE_COMMON_DIR =...

I can, but it is 650+ lines. For now I am just trying to narrow down the source of the error, looking for possible causes

Trying to compile a program with 2 source files and several headers, get the following error when I try to make:


/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../i686-pc-cygwin/bin/ld: BFD (GNU Bi...

This was it, had to move the comment. Thanks!

Hmmm...doesn't seem to make a difference. I still keep getting the error about the line with "})"

Also, I have several other commands like this in the file that do not cause errors. For instance,...

Like this?:


#define REG_AP(mr,reg_flag) \
({ \
reg_flag \
__asm__ ("pushl %0\n" :"=m"(*mr)); \ /*pushes null onto stack */
__asm__ ("call 0x8000\n"); \
})

a)It is called using the REG_AP() function in the main c file
b) gcc

I have the following snippet of inline assembly code in my ConstHeader.h file:



#define REG_AP(mr,reg_flag) \
({ \
reg_flag \
__asm__ ("pushl %0\n" :"=m"(*mr));
__asm__ ("call ...

It compiles the way it is, with the "%".


I can't seem to locate the function, but I know it is from a separate input file. It seems as though I need direct access to the stack and to the...

That is the m68k version with all the other crap deleted. It seems to cross-compile correctly. What I am trying to get around is rewriting it for the x86 by writing it in C.

Really, all this XPrc...

Sorry, I didn't explain that well. MULTI uses some different instructions for its assembly files that aren't used in regular m68k assembly.

Converting to C sounds like it would relieve a lot of...

The assembly file was written with Green Hills MULTI, and isn't compatible with either the m68k or the x86 through GNU. That is to say it was written for the m68k but has program-specific functions...

I have a C file and an assembly file for a program that I need to compile for both the x86 and m68k processors. Instead of making 2 versions of the assembly file, will it work if I write it inline in...

Here is the output now when I try to make:


../ProgramMain.c: In function `main':
../ProgramMain.c:224: warning: passing arg 2 of `LoadTestProgram' makes pointer from
integer without a cast...

When I removed it I got some errors while compiling, which seems like progress. Thanks for the suggestion

I realize that the m68k makefile would not work on the i686, and I made all changes that I thought were necessary. Earlier you mentioned something about the path to the linker script and I was just...