From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001287]: posix_memalign() declared but not implemented
Date: Sat, 24 Mar 2007 12:48:08 -0700 [thread overview]
Message-ID: <93bf8b621253bf2ec48dd4c7f30269ed@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=1287
======================================================================
Reported By: Franck78
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1287
Category: Standards Compliance
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
======================================================================
Date Submitted: 03-24-2007 12:15 PDT
Last Modified: 03-24-2007 12:48 PDT
======================================================================
Summary: posix_memalign() declared but not implemented
Description:
Hello,
For a reason totally ununderstandable for me, 'Vapier' made a correction
19 months ago to uClibc and this correction is not present in latest
uClibc release (0.9.28.3) Why such a delay.....
The facts:
posix_memalign() function is declared in header file (stdlib.h)
posix_memalign() is implemented nowhere
=>compilations run smoothly
=>linking final application sucks (of course)
For example try 'parted version 1.8.2'
Either the function is present or not. But half done job is idiot.
Provided patch to drop in "buildroot/toolchain/uClibc"
to implement the function in next snapshot.
Thank you for read (and fixing).
======================================================================
----------------------------------------------------------------------
bernhardf - 03-24-07 12:31
----------------------------------------------------------------------
So.. why do you file this against buildroot and not properly against
uClibc?
----------------------------------------------------------------------
Franck78 - 03-24-07 12:48
----------------------------------------------------------------------
I did !
http://busybox.net/bugs/view.php?id=1275
If a correction is not released after 19 months, it will never be, no ?
Issue History
Date Modified Username Field Change
======================================================================
03-24-07 12:15 Franck78 New Issue
03-24-07 12:15 Franck78 Status new => assigned
03-24-07 12:15 Franck78 Assigned To => buildroot
03-24-07 12:15 Franck78 File Added: uClibc-0.9.28.3-posix_memalign.patch
03-24-07 12:17 Franck78 Issue Monitored: Franck78
03-24-07 12:31 bernhardf Note Added: 0002276
03-24-07 12:48 Franck78 Note Added: 0002277
======================================================================
next reply other threads:[~2007-03-24 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 19:48 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-31 12:37 [Buildroot] [buildroot 0001287]: posix_memalign() declared but not implemented bugs at busybox.net
2007-03-24 19:57 bugs at busybox.net
2007-03-24 19:32 bugs at busybox.net
2007-03-24 19:15 bugs at busybox.net
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=93bf8b621253bf2ec48dd4c7f30269ed@busybox.net \
--to=bugs@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox