Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Auerbach <karl@cavebear.com>
To: buildroot@busybox.net
Subject: [Buildroot] Several issues by a buildroot newbie...
Date: Sun, 07 Oct 2007 12:19:41 -0700	[thread overview]
Message-ID: <4709314D.1080000@cavebear.com> (raw)
In-Reply-To: <20071007163500.GK20951@aon.at>

Bernhard Fischer wrote:
> On Wed, Oct 03, 2007 at 03:32:13PM -0700, Karl Auerbach wrote:
>> I'm fairly new to buildroot so please excuse me if I inadvertently touch 
>> something that has been raised previously:
>>
>> 1. Undefined reference in uClibc:
>>    In function `__libc_pthread_init':
>>    libc_pthread_init.c:(.text+0xf): undefined reference to
>>    `__libc_multiple_threads'
> 
> Which version of pthreads do you use?

I've used uClibc-0.9.29.tar.bz2 and also the uClibc snapshot (from Oct 
2.)  Is that what you are asking for?

Both versions gave the same problem with Python, but the snapshot 
version fixed similar problems with sudo and the ssh family of executables.

>> 3. The sudo sources aren't available via the URL given in the 
>> package/sudo/sudo.mk.  The site, http://www.courtesan.com/sudo/dist, has 
>> upgraded to a newer version and the older one to be downloaded appears 
>> no longer on that site.
> 
> It should be updated, yes. Please submit a tested patch. TIA.

Hmmm, I just scrounged around and manually downloaded the old version 
from somewhere.

I'm not at all sure that I'm ready, much less sufficiently experienced 
in the buildroot world, to advance the patches and stuff for sudo to the 
current version from the www.courtesan.com site.

>> 4. The lockfile-progs.c (in package lockfile-progs) uses rindex() but 
>> does not include the correct header file that defines it.  This can be 
>> repaired by a patch that either changes rindex() to strrchr() or 
>> including the correct header.  (I did the former.)
> 
> Please submit a patch to use strrchr.

Here's what I've been using, assuming that email doesn't word wrap it 
into oblivion:

karl at klack(24): cat lockfile-progs-iwl-alix.patch
--- lockfile-progs-0.1.10/lockfile-progs.c      2001-07-17 
10:40:06.000000000 -0700
+++ lfp/lockfile-progs.c     2007-09-25 14:41:22.000000000 -0700
@@ -70,7 +70,7 @@
      { NULL, 0, NULL, 0 }
    };

-  char *cmd_name = rindex(argv[0], '/');
+  char *cmd_name = strrchr(argv[0], '/');
    int mail_cmd_p = 0;

    if(cmd_name != NULL) {

      reply	other threads:[~2007-10-07 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-03 22:32 [Buildroot] Several issues by a buildroot newbie Karl Auerbach
2007-10-03 23:55 ` [Buildroot] GDB for threads Leonid
2007-10-09 17:51   ` Rex Ashbaugh
2007-10-04  4:14 ` [Buildroot] Several issues by a buildroot newbie Ulf Samuelsson
2007-10-07 16:30   ` Bernhard Fischer
2007-10-07 18:04     ` Ulf Samuelsson
2007-10-07 16:35 ` Bernhard Fischer
2007-10-07 19:19   ` Karl Auerbach [this message]

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=4709314D.1080000@cavebear.com \
    --to=karl@cavebear.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox