Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] building tiny-x or x11R7 with latest snapshot
Date: Thu, 23 Aug 2007 22:55:00 -0700 (PDT)	[thread overview]
Message-ID: <12306984.post@talk.nabble.com> (raw)
In-Reply-To: <0ad801c7e382$8bb6dfe0$dcc4af0a@atmel.com>


Hi Ulf,

  If we cant build either Tinyx or Xorg or X11 then how else can we build
cairo,pango,gtk and other stuff. i am trying to build a decent toolchain
with all library for arm926ejs but i see that most of these are not
supported for am926ejs

  Is there any possibilities that i can build just cairo pango gtk2 without
the need for x softwares. Once i build all this later can we integrate these
with x softwares.

Regards
Gururaja



Ulf Samuelsson-2 wrote:
> 
>>I receive errors if I want to build either tiny-x or the full X11R7.  has
>> anyone else had these?  Is this something in the environment?
>> 
>> 
>> 
>> I have a snapshot from a couple of months ago and I can build tiny-x
>> without
>> a problem on it.
>> 
>> 
>> 
>> X11R7:
> [snip]
> 
>> 
>> 
>> tiny-x: 
>> 
>> making imake with BOOTSTRAPCFLAGS= in config/imake
>> 
>> /home/christopher/sb/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclib
>> c-gcc -Os -pipe
>> -I/home/christopher/sb/buildroot/build_arm/staging_dir/usr/include
>> -I/home/christopher/sb/buildroot/build_arm/staging_dir/include
>> -mtune=arm920t -o ccimake  -O -I../../include
>> -I../../imports/x11/include/X11 ccimake.c
>> 
> 
> As you can see from above, you are compiling ccimage.c using the ARM cross
> compiler.
> 
>> /home/christopher/sb/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclib
>> c-gcc -Os -pipe
>> -I/home/christopher/sb/buildroot/build_arm/staging_dir/usr/include
>> -I/home/christopher/sb/buildroot/build_arm/staging_dir/include
>> -mtune=arm920t -c  -O -I../../include -I../../imports/x11/include/X11
>> `./ccimake` imake.c
>> 
>> /bin/sh: ./ccimake: cannot execute binary file
> 
> And now you try to run the ARM binary on your PC.
> 
>> 
> [snip]
>> ./config/imake/imake -I./config/cf  -s ./config/makedepend/Makefile.proto
>> -f
>> ./config/makedepend/Imakefile -DTOPDIR=../.. -DCURDIR=./config/makedepend
>> 
>> ./config/imake/imake: ./config/imake/imake: cannot execute binary file
>> 
> 
> I have seen the same problem, tinyx simply does not build.
> Xorg does not build either, and x11r7 is still work in progress.
> 
> 
> 
> Best Regards
> Ulf Samuelsson 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
> 
> 

-- 
View this message in context: http://www.nabble.com/building-tiny-x-or-x11R7-with-latest-snapshot-tf4301002.html#a12306984
Sent from the BuildRoot mailing list archive at Nabble.com.

  reply	other threads:[~2007-08-24  5:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 19:23 [Buildroot] building tiny-x or x11R7 with latest snapshot Christopher Reder
2007-08-20 22:30 ` Ulf Samuelsson
2007-08-24  5:55   ` Hebbar [this message]
2007-08-25 12:46     ` Ivan Kuten
2007-08-25 14:46       ` Hebbar
     [not found]       ` <01cc01c7e757$3e1bf8a0$7201820a@atmel.com>
2007-08-27 13:24         ` Ivan Kuten
2007-09-10 21:25           ` Ivan Kuten

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=12306984.post@talk.nabble.com \
    --to=gururajakr@sanyo.co.in \
    --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