Closed Bug 276825 Opened 20 years ago Closed 18 years ago

change to cygwin coreutils packaging block building

Categories

(Developer Documentation Graveyard :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: daa, Assigned: endico)

Details

from thread http://cygwin.com/ml/cygwin/2004-12/msg00762.html

cygwin.com released  new packaging of "coreutils" (which contains the GNU
fileutils, sh-utils and textutils) included is a /usr/bin/link.exe that is
likely to show up in  your path before the MS linker (link.exe) and make build
impossable

solution - remove or rename /usr/bin/link.exe
There's nothing we can do about this in the build system (short of taking
ownership of the cygwin coreutils package) but it should be documented.
Assignee: nobody → endico
Component: Build Config → Mozilla Developer
Product: Mozilla Application Suite → Documentation
QA Contact: core.build-config → imajes
Anyone on the hook to update the build page?
instructions should say to stick cygwin *after* your compiler (and everything
else, possibly save windows system paths if you have some need for cygwin find)
That's fine, but the instructions call out common errors and why they happen -
we should put this one on.
Here's the exact error to update the page with:

configure: error: The linker major version, ,  does not match the compiler suite
 version, 7.
*** Fix above errors and then restart with "make -f client.mk build"
I've been using the following as a workaround.  Comments welcome.

  1. Under "Configure the Environment", add a new user variable MOZ_BUILD_PATH
     and set it to include %MOZ_TOOLS%\bin and the system's VC bin paths.

  2. Open a Cygwin window and edit ~/.bash_profile so that the following lines
     are appended:

       MBP_CYGPATH_MOD=`cygpath -u -p "$MOZ_BUILD_PATH"`
       PATH="$MBP_CYGPATH_MOD:$PATH"
       export PATH

Can we clean up that we recommend changing the PATH variable at the OS level?

  * Adding "c:\cygwin\bin" is only useful to have access to Cygwin utils from a
    command prompt or from Start->Run.  Though I only use Cygwin apps through a
    Cygwin shell, maybe others commonly use them outside of that environment.  
    Anyone?

  * According to the above, %MOZ_TOOLS%\bin would be a part of %MOZ_BUILD_PATH%
    and would find their way into $PATH inside a Cygwin shell.

  * "c:\mingw\bin" is only needed in MinGW environments.
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.