From: "Rupert Wood" <me@rupey.net>
To: "'Long Li'" <long21st@yahoo.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: g++ -lmalloc error
Date: Fri, 28 Jun 2002 02:05:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D5EC4B5@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D6BF9FC@whale.softwire.co.uk>
Long Li wrote:
> g++ -Wall -g -lpthread -lrt -lmalloc -I{$my_file_path}
:
> /usr/bin/ld: can not find -lmalloc
> collect2: ld returned 1 exit status
The problem is that you're asking ld to link against libmalloc.a or
libmalloc.so but it can't find either of these.
Do you have a libmalloc.a or .so? If so, make sure that ld is searching
the path it's in (you can add paths using '-L').
Do you really need libmalloc? The function is probably available in the
C library unless you've got special requirements. Check your OS C
library documentation.
Rup.
next parent reply other threads:[~2002-06-28 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D6BF9FC@whale.softwire.co.uk>
2002-06-28 2:05 ` Rupert Wood [this message]
2002-06-28 1:52 Long Li
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=616BE6A276E3714788D2AC35C40CD18D5EC4B5@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=gcc-help@gcc.gnu.org \
--cc=long21st@yahoo.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).