From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] GetTime() no longer works after toolchain rebuild
Date: Sat, 24 Jul 2010 19:47:45 +0200 [thread overview]
Message-ID: <20100724194745.12aa8889@surf> (raw)
In-Reply-To: <AANLkTikKay6hseM5TaLwOuBTci4YqXUn+YhQTrg0o9YT@mail.gmail.com>
On Sat, 24 Jul 2010 23:55:58 +1000
Mitch Davis <mjd+buildroot@afork.com> wrote:
> > I've recently rebuilt a toolchain, and now when I recompile some
> > old (c) code, the GetTime() isn't recognised. ?The code compiles,
> > and runs (mostly) on the target architecture. ?The GetTime()
> > function isn't one I recognise (as I inherited the code), and
> > believe I must have missed something when rebuilding the toolchain.
> > ?Any ideas what library this belongs to, and what I have to do to
> > get it working again.
>
> I'm not part of the buildroot crew, so don't take my response as 100%
> but as far as I know, GetTime() is not a standard C function or system
> call. I'm guessing it's part of some user library your old C code is
> linking against. Can you find a reference to GetTime() using Google?
Yes, GetTime() is not a C library function. So, JNY, could you give
some more details about your problem ? Which application/library you're
trying to compile, the exact error message you're having, etc.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-24 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 15:55 [Buildroot] GetTime() no longer works after toolchain rebuild JNY
2010-07-24 13:55 ` Mitch Davis
2010-07-24 17:47 ` Thomas Petazzoni [this message]
2010-07-26 7:49 ` JNY
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=20100724194745.12aa8889@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.