All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 83] New: liblockfile fails to compile due to eaccess redefinition
Date: Mon,  2 Feb 2009 20:00:56 +0000 (UTC)	[thread overview]
Message-ID: <bug-83-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=83

              Host: pc-linux
            Target: arm-linux-gnueabi (gcc 4.2.2)
             Build: 2009.02-rc3
           Summary: liblockfile fails to compile due to eaccess redefinition
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: hunter.cobbs at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


When compiling buildroot liblockfile fails compiling dotlockfile.c due to
redefinition of eaccess in 4.2 gcc compilers.

-------------------  compiler snip -----------------
/opt/eldk/usr/bin/arm-linux-gcc -Os 
-I/home/hcobbs/dev/src/buildroot-2009.02-rc3/ucm_build_arm/staging_dir/include
-I/home/hcobbs/dev/src/buildroot-2009.02-rc3/ucm_build_arm/staging_dir/usr/include
-I/opt/eldk/usr/arm-linux/include --sysroot
/home/hcobbs/dev/src/buildroot-2009.02-rc3/ucm_build_arm/staging_dir/ -g -O2
-Wall -D_GNU_SOURCE -fPIC -D_REENTRANT -I.   -c -o dotlockfile.o dotlockfile.c
dotlockfile.c:45: error: conflicting types for 'eaccess'
/opt/eldk/usr/../arm/usr/include/unistd.h:268: error: previous declaration of
'eaccess' was here
make[1]: *** [dotlockfile.o] Error 1
make[1]: Leaving directory
`/home/hcobbs/dev/src/buildroot-2009.02-rc3/ucm_build_arm/liblockfile-1.06.1'
make: ***
[/home/hcobbs/dev/src/buildroot-2009.02-rc3/ucm_build_arm/staging_dir/lib/liblockfile.so.1.0]
Error 2

-----------------  end compiler snip  -----------------

==================== compiler version ==================
Reading specs from /opt/eldk/usr/bin/../lib/gcc/arm-linux-gnueabi/4.2.2/specs
Target: arm-linux-gnueabi
Configured with:
/opt/eldk/build/arm-2008-11-24/work/usr/src/denx/BUILD/crosstool-0.43/build/gcc-4.2.2-glibc-20070515T2025-eldk/arm-linux-gnueabi/gcc-4.2.2/configure
--target=arm-linux-gnueabi --host=i686-host_pc-linux-gnu
--prefix=/var/tmp/eldk.ywMqKk/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/arm-linux-gnueabi
--disable-hosted-libstdcxx
--with-headers=/var/tmp/eldk.ywMqKk/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/arm-linux-gnueabi/arm-linux-gnueabi/include
--with-local-prefix=/var/tmp/eldk.ywMqKk/usr/crosstool/gcc-4.2.2-glibc-20070515T2025-eldk/arm-linux-gnueabi/arm-linux-gnueabi
--disable-nls --enable-threads=posix --enable-symvers=gnu --enable-__cxa_atexit
--enable-languages=c,c++,java --enable-shared --enable-c99 --enable-long-long
--without-x
Thread model: posix
gcc version 4.2.2
================== end compiler version =================

Altering the liblockfile configure script the following way eliminates the
problem after a make clean:

-- orig --
if test "$GCC" = "yes"; then
    CFLAGS="$CFLAGS -Wall -D_GNU_SOURCE"
fi

-- patched --
if test "$GCC" = "yes"; then
    CFLAGS="$CFLAGS -Wall"
fi


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-02-02 20:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 20:00 bugzilla at busybox.net [this message]
2009-02-02 21:36 ` [Buildroot] [Bug 83] liblockfile fails to compile due to eaccess redefinition bugzilla at busybox.net
2009-02-02 22:21 ` bugzilla at busybox.net
2009-07-06 23:26 ` bugzilla at busybox.net
2009-07-07 21:26 ` bugzilla 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=bug-83-163@https.bugs.busybox.net/ \
    --to=bugzilla@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 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.