From: Jon <jgrosshart@gmail.com>
To: xfs@oss.sgi.com
Subject: acl build failure on x86_64
Date: Tue, 19 Jan 2010 04:18:24 -0500 [thread overview]
Message-ID: <4B5578E0.5000201@gmail.com> (raw)
Brandon and anyone else who might be able to shed some light on this
issue... I'm stumped.
> /usr/bin/make -C chacl
> make[2]: Entering directory `/tmp/acl-2.2.49/chacl'
> gcc -g -O2 -DDEBUG -funsigned-char -fno-strict-aliasing -Wall
> -DVERSION=\"2.2.49\" -DLOCALEDIR=\"/usr/share/locale\"
> -DPACKAGE=\"acl\" -I../include -c -o chacl.o chacl.c
> chacl.c: In function 'walk_dir':
> chacl.c:335: warning: implicit declaration of function 'readdir64'
> chacl.c:335: warning: assignment makes pointer from integer without a cast
> chacl.c:337: error: dereferencing pointer to incomplete type
> chacl.c:337: error: TONS MORE OF THESE ERRORS
> make[2]: *** [chacl.o] Error 1
> make[2]: Leaving directory `/tmp/acl-2.2.49/chacl'
> make[1]: *** [chacl] Error 2
> make[1]: Leaving directory `/tmp/acl-2.2.49'
> make: *** [default] Error 2
This is a pure 64 bit bootstrap using gcc-4.4.2/glibc-2.11/binutils-2.20
following Greg Shaffers DIY Linux reference build. I've got almost 300
packages compiled and am at the tail end of my build so know this has to
be isolated with ACL.... besides the occasional -fPIC issue with certain
progs, this is the first stumbling block I've hit.
Thanks for any and all help.
Jon
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-01-19 4:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 9:18 Jon [this message]
2010-01-20 3:54 ` acl build failure on x86_64 Nathan Scott
2010-01-20 14:29 ` Jon Grosshart
2010-01-20 14:50 ` Jon Grosshart
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=4B5578E0.5000201@gmail.com \
--to=jgrosshart@gmail.com \
--cc=xfs@oss.sgi.com \
/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