Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <734626098.1208517384765.JavaMail.jira@brutus>
Date: Fri, 18 Apr 2008 04:16:24 -0700 (PDT)
From: "Vladimir Beliaev (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Closed: (HARMONY-3325) [classlib][build] linker failure does
 not stop the build
In-Reply-To: <6827069.1173272604595.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HARMONY-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Beliaev closed HARMONY-3325.
-------------------------------------


> [classlib][build] linker failure does not stop the build
> --------------------------------------------------------
>
>                 Key: HARMONY-3325
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3325
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>         Environment: cygwin
>            Reporter: Vladimir Beliaev
>            Priority: Minor
>
> I know the cygwin is not officially supported, still looks like a lot of contributers are using it...
> The problem is that: if one is building classlib from newly installed cygwin then cygwin's 'link' tool is in the PATH before msvc linker - so cygwin linker is used whih causes "do not understand options" error like in trace example below.
> Still, the build does not stop with error reporting the build is SUCESSFULL. It is confusing & it makes diagnistics to be a bit more complex.
> Please get it fixed.
>      [exec]    Creating library <trunk>\working_classlib\deploy\lib\print.lib and object <trunk>\working_classlib\deploy\lib\print.exp
>      [exec] 	link  /debug /opt:icf /opt:ref /INCREMENTAL:NO /NOLOGO  -entry:_DllMainCRTStartup -dll /BASE:0x13300000 -machine:AMD64  /comment:"Print native code. (c) Copyright 2005 - 2006 The Apache Software Foundation or its licensors, as applicable."  -subsystem:windows -out:..\print.dll -map:..\print.map  print.obj  ui.obj print.res  ws2_32.lib Iphlpapi.lib  kernel32.lib  ws2_32.lib advapi32.lib user32.lib gdi32.lib  comdlg32.lib winspool.lib  <trunk>\working_classlib\deploy\lib\print.exp
>      [exec] /usr/bin/link: invalid option -- e
>      [exec] Try `/usr/bin/link --help' for more information.
>      [exec] 	if exist ..\print.dll.manifest  mt -manifest ..\print.dll.manifest -outputresource:..\print.dll;#2
> The known workaround is to remove cygwin linker from PATH.
> Thanks
> Vladimir Beliaev

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.