From: "per jonhanesen" <per@johanesenaps.com>
To: help-gcc@gnu.org
Subject: Re: Installation of GCC 2.72 on ms-dos
Date: Fri, 07 Jan 2000 06:46:00 -0000 [thread overview]
Message-ID: <oXmd4.158$RR1.356@news.get2net.dk> (raw)
In-Reply-To: <38753fa3.46216045@news.nic.utwente.nl>
Thanks for the answer.
We needed to state the libraries to link to to the linker. ld ....
/llibname.
Isn´t djgpp 32-bit for windows developer environment ? We are using a m68k
cross compiler (gcc-m68k for DOS), so I dont think using djgpp is a good
idea !
Does anyone know if it is difficult to make this cross-compiler compile C++
code and link it with ld ?
Morten Boll, Master Student in CS at DIKU Uni. of Copenhagen
Andrei A. Dergatchev <A.Dergatchev@tn.utwente.nl> wrote in message
news: 38753fa3.46216045@news.nic.utwente.nl ...
> I want to ask in
>
> comp.os.msdos.djgpp
>
> (or check deja for that NG)
>
> HTH
>
> Andrei
>
> On Thu, 6 Jan 2000 03:44:39 +0100, "Morten Boll" <boll@boll.com>
> wrote:
>
> >Does ne1 know of a good installation guide for installation of GNU GCC
> >compiler accessible on the net?
> >
> >We have copied all the files to "C:\GCC" - but whenever we try to
compiles
> >it comes with a linker error, like
> > hello.o(.text+0x12):hello.c: undefined reference to `__main'
> > hello.o(.text+0x1c):hello.c: undefined reference to `printf'
> >
> >Any help would be appreciated, thnx
> >
> >/Kasper and Morten
> >
> >
> >
>
WARNING: multiple messages have this Message-ID
From: "per jonhanesen" <per@johanesenaps.com>
To: help-gcc@gnu.org
Subject: Re: Installation of GCC 2.72 on ms-dos
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <oXmd4.158$RR1.356@news.get2net.dk> (raw)
Message-ID: <20000401000000.rRwV8yz-JWs1DWr6n31aiORQbnPB67_H5crgIR6ln4Q@z> (raw)
In-Reply-To: <38753fa3.46216045@news.nic.utwente.nl>
Thanks for the answer.
We needed to state the libraries to link to to the linker. ld ....
/llibname.
Isn´t djgpp 32-bit for windows developer environment ? We are using a m68k
cross compiler (gcc-m68k for DOS), so I dont think using djgpp is a good
idea !
Does anyone know if it is difficult to make this cross-compiler compile C++
code and link it with ld ?
Morten Boll, Master Student in CS at DIKU Uni. of Copenhagen
Andrei A. Dergatchev <A.Dergatchev@tn.utwente.nl> wrote in message
news: 38753fa3.46216045@news.nic.utwente.nl ...
> I want to ask in
>
> comp.os.msdos.djgpp
>
> (or check deja for that NG)
>
> HTH
>
> Andrei
>
> On Thu, 6 Jan 2000 03:44:39 +0100, "Morten Boll" <boll@boll.com>
> wrote:
>
> >Does ne1 know of a good installation guide for installation of GNU GCC
> >compiler accessible on the net?
> >
> >We have copied all the files to "C:\GCC" - but whenever we try to
compiles
> >it comes with a linker error, like
> > hello.o(.text+0x12):hello.c: undefined reference to `__main'
> > hello.o(.text+0x1c):hello.c: undefined reference to `printf'
> >
> >Any help would be appreciated, thnx
> >
> >/Kasper and Morten
> >
> >
> >
>
next prev parent reply other threads:[~2000-01-07 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-06 6:55 Morten Boll
2000-01-06 17:27 ` Andrei A. Dergatchev
2000-01-07 6:46 ` per jonhanesen [this message]
2000-04-01 0:00 ` per jonhanesen
2000-04-01 0:00 ` Andrei A. Dergatchev
2000-04-01 0:00 ` Morten Boll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='oXmd4.158$RR1.356@news.get2net.dk' \
--to=per@johanesenaps.com \
--cc=help-gcc@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).