___
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
On Thu, 7 Sep 2000, identity wrote:
>Date: Thu, 7 Sep 2000 12:59:26 +0200
>From: identity <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Content-Type: text/plain;
> charset="iso-8859-1"
>Subject: Re: Hi
>
>You are both right. I was accually doing C.
You are both right. I was accually doing C. I only just remembered one book
about C++. :))) thanks
- Original Message -
From: "Mike A. Harris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 07, 2000 11:56 AM
Subject: Re: Hi
> On Thu,
On Thu, 10 Aug 2000, Jesse Marlin wrote:
>You mentioned using c++. gcc is the C compiler and g++ is the C++ compiler.
>Since you have files with .c extension then I assume you are doing C. So
>you would want to try:
>
>to compile:
>gcc -c -o blabla.o blabla.c
>
>to link:
>gcc -o blabla blabla.o
> identity writes:
> > well nothing, just gcc blabla.c blabla.o, etc
>
> You mentioned using c++. gcc is the C compiler and g++ is the C++ compiler.
> Since you have files with .c extension then I assume you are doing C. So
> you would want to try:
>
> to compile:
> gcc -c -o blabla.o blabla.
identity writes:
> well nothing, just gcc blabla.c blabla.o, etc
You mentioned using c++. gcc is the C compiler and g++ is the C++ compiler.
Since you have files with .c extension then I assume you are doing C. So
you would want to try:
to compile:
gcc -c -o blabla.o blabla.c
to link:
gcc -o
Alexandru Sofronie wrote:
> Yes, C++ DOS programming sucks but that's my client's platforms.
> When they'll have Linux, i'll #include there but MS DOS is
> commercial, right? I get commercial too!!!
>
Then why don't you complete the cycle paying someone to commercially solve your
problem?
B
t: Wednesday, August 09, 2000 12:42 AM
Subject: Re: Hi
> well it was under linux, never programmed under dos
>
> Happy coding?
>
> - Original Message -
> From: "Matt Fahrner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, Augus
well nothing, just gcc blabla.c blabla.o, etc
- Original Message -
From: "Jesse Marlin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 09, 2000 12:16 AM
Subject: Re: Hi
> identity writes:
> > well it was under linux, never program
identity writes:
> well it was under linux, never programmed under dos
Do you have a Makefile or can you supply the arguments you passed
to g++?
> > > Alexandru Sofronie wrote:
> > > >
> > > > Can anyone tell me what can I do when the C++ linker has fatal error:
> > > > Segment _TEXT excee
well it was under linux, never programmed under dos
Happy coding?
- Original Message -
From: "Matt Fahrner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 08, 2000 11:32 PM
Subject: Re: Hi
> Does sound like DOS not Linux. I had similar
True, I had that experience on DOS and on DEC Ultrix (back in the 1980's),
but I've not experienced anything of late on Linux or HP-UX.
On Tue, 8 Aug 2000, Matt Fahrner wrote:
> Does sound like DOS not Linux. I had similar messages when we exceded
> stack sizes within the DOS 64k memory limit.
nowing. Happy coding! :)
- Original Message -
From: "Mark Pruett" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 08, 2000 11:23 PM
Subject: Re: Hi
> What OS and compiler are you using? The last time I saw
> these types of messages was with Borland compile
Does sound like DOS not Linux. I had similar messages when we exceded
stack sizes within the DOS 64k memory limit.
- Matt
Mark Pruett wrote:
>
> What OS and compiler are you using? The last time I saw
> these types of messages was with Borland compilers
> on DOS/Windows
What OS and compiler are you using? The last time I saw
these types of messages was with Borland compilers
on DOS/Windows on x86 machines. Borland let you
select "memory models" for compilation/linking,
and the smaller memory models ("small" and "compact",
IIRC) were limited to 64k _TEXT segments.
Try using type LONG_TEXT
- Original Message -
From: "Alexandru Sofronie" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 08, 2000 10:57 PM
Subject: Hi
> Can anyone tell me what can I do when the C++ linker has fatal error:
> Segment _TEXT
Can anyone tell me what can I do when the C++ linker has fatal error:
Segment _TEXT exceedes 64K?
What can I do?
Thanks,
[EMAIL PROTECTED]
___
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-de
> Hi folks,
>
> Do you know of any Linux Virtual Server Cluster installations on a
> production environment?
>
> I need the hi-availability, but don't have any money. The LVS seems to be a
> good candidate... a cluster with 4/5 machines running proprietary softw
Hi
This is OT for a Redhat development list
RH does have a load balancing software for http called Pirhana, apart from
that I believe Turbolinux has cluster based systems
*** REPLY SEPARATOR ***
On 1/05/00 at 12:54 Edward Hoo wrote:
>Hi folks,
>
>Do you know of
Hi folks,
Do you know of any Linux Virtual Server Cluster installations on a
production environment?
I need the hi-availability, but don't have any money. The LVS seems to be a
good candidate... a cluster with 4/5 machines running proprietary software
and oracle db's. I wou
20 matches
Mail list logo
