On 19.12.2007, at 05:22, [EMAIL PROTECTED] wrote:


Heh, heh, another difficult problem!

The problem is that many applications that compile inside T2 will not
compile outside. That is, I have a full development environemt setup
in Puppy Linux, with all the required tools that were compiled in T2.

Most packages compile, but there are major exceptions, for example I
cannot compile any XFCE or gtkmm-based applications.

What I get are error messages about '__sync_fetch_and_add_4' being an
unresolved symbol.

I have done a lot of googling, and this bug is in the 'gcc' package.
It seems that gcc/libstdc++ is treating the compile as for the
386 CPU, even though I have specified a 'i486' with the '--build'
configure option (also T2 was compiled for a 486).

One fix I cam across on the Internet is to export CFLAGS="-march=i486"
and I tried this before running configure in the Gparted package
(Gparted requires gtkmm libs). But, compiling still stops with that
same error.

At this stage I don't know what to do. The thing is though, you don't
have the problem inside the T2 build system. Does anyone know why not?
Is anything special done to avoid this problem?

I never encountered this problem, although I did 486 builds
even this year.

Gfor the sandbox builds and the generic mechanisms such
as program argument transformations used by T2 every
compiler invocation gets the specified optimizations, such as
-mcpu=i486 et al. injected automatically. No matter what might
be encoded in some Makefile, scons or shell script. This might
be why it just builds with T2 and something is missing or wrong
in manual builds.

All the best and happy christmas,

--
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  Geschäftsführer: Susanne Klaus, René Rebe
  Sitz: Berlin, Amtsgericht Charlottenburg HRB 105 123 B
  USt-IdNr.: DE251602478
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name


----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of: unsubscribe t2

Reply via email to