Re: [MiNT] Linking with multilib feature

[Patrice Mandin <mandin.patrice@orange.fr>]

Le Fri, 12 Dec 2008 08:06:13 +0100
Patrice Mandin <mandin.patrice@orange.fr> a _crit:

> 
> Le Thu, 11 Dec 2008 23:26:31 -0500
> Mark Duckworth <mduckworth@atari-source.org> a _crit:
> 
> > I think most probably multilib was never designed to be used for static 
> > compiling...  :-/  I've often wondered if it would behave this way.. 
> > it's nice to know for sure.
> 
> Well, I just tried with gcc 4.3, and it behaves the same.
> 
> However I see a difference against gcc 3.3:
> m68k-atari-mint-gcc -m68020-60 -print-search-dirs adds m68020-60
> directories to the libraries: value (4.3) whereas gcc 3.3 does not list
> m68020-60 directories. So I suppose gcc 3.3 manage multilib directories
> differently, whereas gcc 4.3 explicitly adds them.
> I wonder how gcc 2.95 behaves in this regard.

OK, I just tested 2.95 (native), and retested 4.3.2 newly rebuilt, and
they behave correctly, i.e. when -L list one of default directories, it
still has multilib enabled on it. Something is wrong in my 3.3
cross-compiler setup, and my previous 4.3 cross-compiler build.

I need to check 2.95 patch, but the t-mint file for gcc I use for 4.3.2
contains:

MULTILIB_OPTIONS = m68000/m68020/m68020-60 mshort
MULTILIB_DIRNAMES = m68020 m68020-60 mshort

(My idea is to setup multilib to say that m68000 is incompatible with
m68020 and m68020-60).

Before, I only had:

MULTILIB_OPTIONS = m68020/m68020-60 mshort
MULTILIB_DIRNAMES =

So I wonder if it was the cause of my problems. gcc documentation is
not very clear in this regard. Sorry to have bother you all :).

-- 
Patrice Mandin
WWW: http://pmandin.atari.org/
Programmeur Linux, Atari
Spécialité: Développement, jeux