On Fri, Oct 15, 2010 at 11:42 PM, Dongsheng Song <[email protected]> wrote: > On Thu, Oct 14, 2010 at 22:35, NightStrike <[email protected]> wrote: >> On Wed, Oct 13, 2010 at 5:06 AM, Dongsheng Song >> <[email protected]> wrote: >>> 3. symlinks >>> Even for single target, we must set symlinks. Can we disable the mess >>> multilibs support in this occasion ? >> >> Which symlink, the lib > libXX, or the mingw > $target? And, can you >> rephrase your actual question? I do not understand what exactly you >> are asking. >> > > For i686-w64-mingw32 target, I do not expected lib32 existed: > > ~/gcc-4.5-xp$ du -hs * > 17M bin > 8.3M include > 11M lib > 19M lib32 > 64M libexec > 11M share > 65M i686-w64-mingw32 > > > For x86_64-w64-mingw32 target, I do not expected lib64 existed: > ~/gcc-4.5-x64$ du -hs * > 21M bin > 8.3M include > 13M lib > 24M lib64 > 69M libexec > 11M share > 127M x86_64-w64-mingw32 >
Yes, this does seem backwards. Are the directory names wrong, or the contents wrong? ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
