All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] lame linking issue
Date: Fri, 01 Jul 2011 16:49:59 +0200	[thread overview]
Message-ID: <4E0DDE97.2070905@visionsystems.de> (raw)
In-Reply-To: <BANLkTikpCNTTL8aMbkejweQsLN_B9oxB+g@mail.gmail.com>

Hi Hariharan,

see .config for details: http://pastebin.com/xtR3jnHm

Yegor

Am 01.07.2011 16:44, schrieb hariharan veerappan:
> Hi Yegor,
>
> Whether you are using build root toolchain or external?
> Provide your Host Platform ( compilation ) and target platform.
>
> Hariharan.V.
>
> On Fri, Jul 1, 2011 at 7:26 PM, Yegor Yefremov <yegor_sub1 at visionsystems.de <mailto:yegor_sub1@visionsystems.de>> wrote:
>
>     I'm using the latest git version of BR and wanted to build lame-3.98.4. During linking phase I got following errors:
>
>     parse.o: In function `local_strcasecmp':
>     parse.c:(.text+0x134): undefined reference to `__ctype_tolower_loc'
>     get_audio.o: In function `fskip.constprop.1':
>     get_audio.c:(.text+0x224): undefined reference to `__fxstat64'
>     lametime.o: In function `lame_get_file_size':
>     lametime.c:(.text+0x9c): undefined reference to `__xstat64'
>     portableio.o: In function `ReadByte':
>     portableio.c:(.text+0x4): undefined reference to `_IO_getc'
>     portableio.o: In function `Read16BitsLowHigh':
>     portableio.c:(.text+0x28): undefined reference to `_IO_getc'
>     portableio.c:(.text+0x34): undefined reference to `_IO_getc'
>     portableio.o: In function `Read16BitsHighLow':
>     portableio.c:(.text+0x60): undefined reference to `_IO_getc'
>     portableio.c:(.text+0x6c): undefined reference to `_IO_getc'
>     portableio.o: In function `Write8Bits':
>     portableio.c:(.text+0x9c): undefined reference to `_IO_putc'
>     portableio.o: In function `Write16BitsLowHigh':
>     portableio.c:(.text+0xbc): undefined reference to `_IO_putc'
>     portableio.c:(.text+0xcc): undefined reference to `_IO_putc'
>     portableio.o: In function `Write16BitsHighLow':
>     portableio.c:(.text+0xf0): undefined reference to `_IO_putc'
>     portableio.c:(.text+0xfc): undefined reference to `_IO_putc'
>     portableio.o: In function `Read24BitsHighLow':
>     portableio.c:(.text+0x110): undefined reference to `_IO_getc'
>     portableio.c:(.text+0x11c): undefined reference to `_IO_getc'
>     portableio.c:(.text+0x128): undefined reference to `_IO_getc'
>     portableio.o: In function `ReadBytes':
>     portableio.c:(.text+0x23c): undefined reference to `_IO_getc'
>     portableio.o: In function `ReadBytesSwapped':
>     portableio.c:(.text+0x290): undefined reference to `_IO_getc'
>     portableio.o: In function `WriteBytes':
>     portableio.c:(.text+0x30c): undefined reference to `_IO_putc'
>     portableio.o: In function `WriteBytesSwapped':
>     portableio.c:(.text+0x344): undefined reference to `_IO_putc'
>     collect2: ld returned 1 exit status
>
>     Any idea?
>
>     Some toolchain details:
>
>     uClibc: 0.9.32
>     GCC: 4.6.1
>
>     I could also post the whole config file.
>
>     Yegor
>     _______________________________________________
>     buildroot mailing list
>     buildroot at busybox.net <mailto:buildroot@busybox.net>
>     http://lists.busybox.net/mailman/listinfo/buildroot
>
>

  reply	other threads:[~2011-07-01 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 13:56 [Buildroot] lame linking issue Yegor Yefremov
2011-07-01 14:44 ` hariharan veerappan
2011-07-01 14:49   ` Yegor Yefremov [this message]
2011-07-05  8:39 ` Peter Korsgaard
2011-07-05  9:06   ` Yegor Yefremov
2011-07-05  9:24     ` Peter Korsgaard
2011-07-05 10:01       ` Yegor Yefremov
2011-07-05 10:09         ` Peter Korsgaard
2011-07-05 10:12           ` Yegor Yefremov
2011-07-05 11:28             ` Peter Korsgaard
2011-07-05 12:06               ` Yegor Yefremov
2011-07-05 13:01                 ` Peter Korsgaard

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=4E0DDE97.2070905@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --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.