Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: olegol@aport.ru
To: "Stephen P. Becker" <geoman@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: Re: GTK/GLIB port for mipsel
Date: Thu, 19 Jan 2006 16:05:48 +0300	[thread overview]
Message-ID: <Vy3HKuPmiEfd4pZ@aport2000.ru> (raw)
In-Reply-To: <43CF864F.1020202@gentoo.org>

>> Can anybody here point me to a source where I can 
>> download a glib and gtk ports for mipsel, or at least 
get 
>> more info on this.
>
>Well, it wouldn't surprise me if something is broken, as 
I get the 
>feeling that the GNOME folks are notorious for doing 
unportable crap in 
>their code.  However, GTK/glib builds and works just 
fine for me.  I 
>suspect that either something is broken in your cross-
compile setup, or 
>you might be using ancient versions of these packages.  
I have both 
>glib-2.8.5 and gtk -2.8.10 installed on my (big-endian) 
machines here 
>without any problems.

I'm trying to install glib 2.8.3 (I do not think it is 
too much different from 2.8.5). I have little-endian mips 
architecture (mipsel) and am installing the library on 
the RedHat Linux with core 2.4 (both on a target and on a 
host).
I'm using the following parameters with configure:
./configure --prefix=<path> --build=mipsel-linux --
host=i686-linux --with-libiconv=gnu

Do you have you gtk/glib compiled from the sources on 
your machine or just a binaries installed? Do you have 
a ./glib/gatomic.c file compiled? I do not quite 
understand how that can be (I could not see there a 
section for MIPS/MIPSEL). Also, do you have any of the 
G_ATOMIC_<platform> macros defined in the config.h file?

With respect,
Oleg Kruzhkov

  reply	other threads:[~2006-01-19 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 12:15 GTK/GLIB port for mipsel olegol
2006-01-19 12:30 ` Stephen P. Becker
2006-01-19 13:05   ` olegol [this message]
2006-01-19 14:57     ` Stephen P. Becker
2006-01-19 15:18       ` olegol

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=Vy3HKuPmiEfd4pZ@aport2000.ru \
    --to=olegol@aport.ru \
    --cc=geoman@gentoo.org \
    --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