-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nikita V. Youshchenko writes:
Hello
3. I'm having bad time with gcc-3.4 sparc multilib target. Current
debian/rules.conf contains code that changes TARGET_ALIAS from
sparc-linux to sparc64-linux. But this causes unwanted
Hello
3. I'm having bad time with gcc-3.4 sparc multilib target. Current
debian/rules.conf contains code that changes TARGET_ALIAS from
sparc-linux to sparc64-linux. But this causes unwanted side-effects
(such as attempts to use 'sparc64-linux-as' instead of
'sparc-linux-as' as
Nikita V. Youshchenko writes:
Hello
3. I'm having bad time with gcc-3.4 sparc multilib target. Current
debian/rules.conf contains code that changes TARGET_ALIAS from
sparc-linux to sparc64-linux. But this causes unwanted side-effects
(such as attempts to use 'sparc64-linux-as'
Nikita V. Youshchenko writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
After a delay that was longer that I hoped, I continued my work on
cross-gcc patches.
I'm attaching the results.
Gcc-3.3 and gcc-3.4 are now almost in sync.
3.3 builds for all debian linux targets
3.4
After a delay that was longer that I hoped, I continued my work on
cross-gcc patches.
I'm attaching the results.
Gcc-3.3 and gcc-3.4 are now almost in sync.
3.3 builds for all debian linux targets
3.4 still fails for sparc target, but builds for all other debian
linux targets.
Most
Nikita V. Youshchenko writes:
After a delay that was longer that I hoped, I continued my work on
cross-gcc patches.
I'm attaching the results.
Gcc-3.3 and gcc-3.4 are now almost in sync.
3.3 builds for all debian linux targets
3.4 still fails for sparc target, but builds for all
Btw, what's the current situation with sarge packages? I see binutils
2.15-4 migrated to sarge recently - does that mean that a new upload
of gcc-3.3 and gcc-3.4 will happen? If so, please let me know, and
give me a chance to backport last cross-targets fixes to sarge
versions before the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
After a delay that was longer that I hoped, I continued my work on
cross-gcc patches.
I'm attaching the results.
Gcc-3.3 and gcc-3.4 are now almost in sync.
3.3 builds for all debian linux targets
3.4 still fails for sparc target, but builds
8 matches
Mail list logo