mearvk <[EMAIL PROTECTED]> writes:
> "g++ -c lip.C" gives me lip.o.
> "g++ -c test.C" gives me test.o
> "g++ -o out test.o lip.o -lm" should give me 'out' as an executable
> but it doesn't, instead giving me:
>
> lip.o(.text+0xf88d): In function `zfread(_IO_FILE*, long**)':
> : undefined reference
emp1953 <[EMAIL PROTECTED]> writes:
> When I received the linux machine I find that it is little endian.
Was that a surprise to you?
I mean, it is the first and most obvious question when defining wire
protocol: is the target environment homogeneous (no conversions
necessary) or heterogeneous (m
I developed a ton of code on a Solaris machine in c++ hoping to save
time by not waiting for my linux machine to arrive.
It has several hundred structured messages of varying length from 28
bytes to 2048 bytes, with varying data types.
unsigned char
unsigned short
unsigned int
unsigned long
These m
On Feb 5, 7:44 pm, Paul Pluzhnikov <[EMAIL PROTECTED]> wrote:
> Larry Smith <[EMAIL PROTECTED]> writes:
> > Perhaps the confusion comes from the GCC docs:
>
> > PowerPC Options:
> > `-mlittle'
> > `-mbig'
> > Similar options are mentioned for SPARC, ARM, MCore, IA-64, etc
>
> Interesting. I didn'
Paul Pluzhnikov wrote:
> Pep <[EMAIL PROTECTED]> writes:
>
> > g++ -I. -L. -ltest -o test-main main.cc
>
> Above command line is incorrect. Try this:
>
> g++ -I. -L. -o test-main main.cc -ltest
>
> > I've been looking at this for some time now and am frankly stumped by
> > what I know must be
Larry Smith wrote:
> Here is the "makefile" I used to build your example:
>
> --
>
> # GNU Make makefile
>
> # how to make a '.o' from a '.cc'.
> # make will use this rule to build main.o, file1.o, and file2.o
> %.o: %.cc
> g++ -c -o $@ -I. $<
>
> # how to make 'test-main'
> # th
