Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0006364]: lockfile-progs do not find rindex in string.h
Date: Mon, 17 Nov 2008 02:26:49 -0800	[thread overview]
Message-ID: <f6e74403fc993a32a18a0f5e194cc16f@busybox.net> (raw)


The following issue has been SUBMITTED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=6364 
====================================================================== 
Reported By:                robang74
Assigned To:                buildroot
====================================================================== 
Project:                    buildroot
Issue ID:                   6364
Category:                   Architecture Specific
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             11-17-2008 02:26 PST
Last Modified:              11-17-2008 02:26 PST
====================================================================== 
Summary:                    lockfile-progs do not find rindex in string.h
Description: 
make[1]: Entering directory
`/home/roberto/gles/buildroot/build_i586/lockfile-progs-0.1.11'
/home/roberto/gles/buildroot/build_i586/staging_dir/usr/bin/i586-linux-uclibc-gcc
-Os  -I/home/roberto/gles/buildroot/build_i586/staging_dir/usr/include
-I/home/roberto/gles/buildroot/build_i586/staging_dir/include
--sysroot=/home/roberto/gles/buildroot/build_i586/staging_dir/ -isysroot
/home/roberto/gles/buildroot/build_i586/staging_dir -mtune=i586
-march=i586 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -g -Wall -Werror -O2   -c -o lockfile-progs.o
lockfile-progs.c
cc1: warnings being treated as errors
lockfile-progs.c: In function ?parse_arguments?:
lockfile-progs.c:96: warning: implicit declaration of function ?rindex?
lockfile-progs.c:96: warning: incompatible implicit declaration of
built-in function ?rindex?
make[1]: *** [lockfile-progs.o] Error 1
make[1]: Leaving directory
`/home/roberto/gles/buildroot/build_i586/lockfile-progs-0.1.11'
make: ***
[/home/roberto/gles/buildroot/project_build_i586/ugles/root/usr/bin/lockfile-create]
Error 2





====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-17-08 02:26  robang74       New Issue                                    
11-17-08 02:26  robang74       Status                   new => assigned     
11-17-08 02:26  robang74       Assigned To               => buildroot       
======================================================================

             reply	other threads:[~2008-11-17 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17 10:26 bugs at busybox.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-17 10:29 [Buildroot] [buildroot 0006364]: lockfile-progs do not find rindex in string.h bugs at busybox.net
2008-11-19 10:17 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=f6e74403fc993a32a18a0f5e194cc16f@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