From: Pete Popov <ppopov@redcreek.com>
To: crossgcc@cygnus.com
Subject: Re:
Date: Fri, 22 May 1998 09:56:00 -0000 [thread overview]
Message-ID: <3565ADA2.3C61295A@redcreek.com> (raw)
In-Reply-To: <3561BA5A.B421C781@redcreek.com>
Thanks to everyone who responded to my
mail. I now understand the "problem" and
know how to fix it.
Thanks again,
Pete
Pete Popov wrote:
> Hi,
>
> I'm using a mips64 dos-hosted cross
> compiler which I built on my Linux box.
> The compiler has been working fine and
> we haven't ran into any problems, but
> there's something I don't understand and
> it really frustrates me.
>
> I'm compiling all files with "-nostdinc"
> switch; the files are later linked with
> "-nostdlib". I've got my own version
> of "memcpy" and a few other routines;
> however, for some reason, the compiler
> chooses to insert the standard libc
> memcpy in some of the files. Thus, some
> files get my version of memcpy, and
> other get the libc version. There's is
> no apparent difference in those files;
> they include the same .h files, they are
> compiled with the same switches, etc.
> Any suggestions?
>
> Thanks,
>
> Pete
next prev parent reply other threads:[~1998-05-22 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-19 9:59 No Subject Pete Popov
1998-05-20 6:06 ` your mail Rolf Fiedler
1998-05-20 6:06 ` memcpy Jonathan Larmour
1998-05-22 9:56 ` Pete Popov [this message]
2000-07-18 3:42 Fw: alexperi
2000-07-18 6:54 ` Matthew Majka
2001-01-11 21:46 FW: Mahadev K Cholachagudda
2001-01-11 23:09 ` mike
2001-04-01 0:00 ` Re: mike
2003-03-01 6:38 Windows.net
2003-03-01 6:38 RE: Windows.net
2003-03-01 6:38 RE: Windows.net
2003-03-01 6:38 RE: Windows.net
[not found] <362839576.2566860.1706922246488.ref@mail.yahoo.com>
2024-02-03 1:04 ` Re, Ellen Hester
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=3565ADA2.3C61295A@redcreek.com \
--to=ppopov@redcreek.com \
--cc=crossgcc@cygnus.com \
/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).