Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Robert Woerle <robert@linuxdevelopment.de>
To: linux-mips@linux-mips.org
Subject: diet-X11 fails /include/bits/types.h
Date: Thu, 05 Jan 2006 23:28:35 +0100	[thread overview]
Message-ID: <43BD9D93.40005@linuxdevelopment.de> (raw)

Hi

i am new to mips and i am compiling a familiar gpe image for mips based
systems .
Now diet-X11 and X11 are breaking to compile on the below error.
I googled  and found various occasions of this /include/bits/types.h
causing problems

i guess that has something todo with combination on compiler and glibc
seems also glibc-2.3.5 fails on that

i am using for that build
glibc-2.3.3
gcc-cross-3.3.4

make[2]: Entering directory
`/home/bob/Handhelds/oe/stuff/mips-build/tmp/work/diet-x11-6.2.1cvs20050226-r5/X11/src/util'
| if gcc -DHAVE_CONFIG_H -I.
-I/home/bob/Handhelds/oe/stuff/mips-build/tmp/work/diet-x11-6.2.1cvs20050226-r5/X11/src/util
-I../../src  
-I/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include
-Wall -Wpointer-arith -Wstrict-prototypes        -Wmissing-prototypes
-Wmissing-declarations     -Wnested-externs -fno-strict-aliasing
-I/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include
-I/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/X11/Xtrans  
-D_XOPEN_SOURCE=500
-I/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include  
-I/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2
-MT makekeys-makekeys.o -MD -MP -MF ".deps/makekeys-makekeys.Tpo" -c -o
makekeys-makekeys.o `test -f 'makekeys.c' || echo
'/home/bob/Handhelds/oe/stuff/mips-build/tmp/work/diet-x11-6.2.1cvs20050226-r5/X11/src/util/'`makekeys.c;
\
| then mv -f ".deps/makekeys-makekeys.Tpo" ".deps/makekeys-makekeys.Po";
else rm -f ".deps/makekeys-makekeys.Tpo"; exit 1; fi
| In file included from
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/sys/types.h:31,
|                  from
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/X11/Xos.h:59,
|                  from makekeys.c:34:
|
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/bits/types.h:127:3:
#error
| In file included from
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/sys/types.h:31,
|                  from
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/X11/Xos.h:59,
|                  from makekeys.c:34:
|
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/bits/types.h:136:
error: syntax error before "__dev_t"
|
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/bits/types.h:136:
warning: type defaults to `int' in declaration of `__dev_t'
|
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/bits/types.h:136:
warning: data definition has no type or storage class
|
/home/bob/Handhelds/oe/stuff/mips-build/tmp/staging/mipsel-linux/include/bits/types.h:140:
error: syntax error before "__ino64_t"

any hint is greatly appriciated
regards

rob_w

             reply	other threads:[~2006-01-05 22:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05 22:28 Robert Woerle [this message]
2006-01-06 15:06 ` diet-X11 fails /include/bits/types.h Robert Woerle

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=43BD9D93.40005@linuxdevelopment.de \
    --to=robert@linuxdevelopment.de \
    --cc=linux-mips@linux-mips.org \
    /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