From: Aaron G. <an...@be...> - 2007-05-19 04:07:12
|
/usr seems to be redirected to root on my version/instillation of msys, = hence it has vannished to all intensive purposes. Is this normal, and if = so why ? Also what is going on with MSYS and MinGW directory tree wise, can they = just be merged into one tree. I need Unix/Linux compatibility in the tree structure otherwise GIT does = not seem to work correctly. Many thanks in advance, Aaron |
From: Tim S. <sta...@ne...> - 2007-05-19 04:44:14
|
Aaron Gray wrote: > /usr seems to be redirected to root on my version/instillation of msys, hence it has vannished to all intensive purposes. Is this normal, and if so why ? > > Also what is going on with MSYS and MinGW directory tree wise, can they just be merged into one tree. > > I need Unix/Linux compatibility in the tree structure otherwise GIT does not seem to work correctly. > > Many thanks in advance, > > Aaron See the folder etc/ under MSys look at fstab.sample in order to edit or create fstab file. Tim S |
From: Emmett G. <emm...@fr...> - 2007-05-19 05:54:57
|
the mount command doesn't work in vista. Tim Stahlhut wrote: > Aaron Gray wrote: > > >> /usr seems to be redirected to root on my version/instillation of msys, hence it has vannished to all intensive purposes. Is this normal, and if so why ? >> >> Also what is going on with MSYS and MinGW directory tree wise, can they just be merged into one tree. >> >> I need Unix/Linux compatibility in the tree structure otherwise GIT does not seem to work correctly. >> >> Many thanks in advance, >> >> Aaron >> > > See the folder etc/ under MSys look at fstab.sample in order to edit or > create fstab file. > > Tim S > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys > > > |
From: Aaron G. <an...@be...> - 2007-05-19 16:56:22
|
> the mount command doesn't work in vista. I have both XP and Vista both have the same problem. Can you redirect or create a normal directory for /usr using fstab ? > Tim Stahlhut wrote: >> Aaron Gray wrote: >> >> >>> /usr seems to be redirected to root on my version/instillation of msys, >>> hence it has vannished to all intensive purposes. Is this normal, and if >>> so why ? >>> >>> Also what is going on with MSYS and MinGW directory tree wise, can they >>> just be merged into one tree. >>> >>> I need Unix/Linux compatibility in the tree structure otherwise GIT does >>> not seem to work correctly. >>> >>> Many thanks in advance, >>> >>> Aaron >>> >> >> See the folder etc/ under MSys look at fstab.sample in order to edit or >> create fstab file. >> >> Tim S >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Mingw-msys mailing list >> Min...@li... >> https://lists.sourceforge.net/lists/listinfo/mingw-msys >> >> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.467 / Virus Database: 269.7.4/811 - Release Date: 18/05/2007 > 15:50 > > |
From: Keith M. <kei...@us...> - 2007-05-19 18:00:15
|
On Saturday 19 May 2007 17:56, Aaron Gray wrote: > the mount command doesn't work in vista. It does, to the extent that, IIRC, is documented in the README.rtf file which came along with MSYS; you *did* read it, didn't you? In case not, then FTR it works only without arguments, to report the mount table state, as defined via /etc/fstab. If you wish to manipulate this, then you edit /etc/fstab, as explained in the fine manual, i.e. this self same README.rtf file, which you apparently didn't read. FWIW, I have developed my own variation on MSYS' mount command, which does accept arguments, and so behaves more as might be expected. We may consider putting something like that into MSYS-1.0.12; maybe even into the upcoming MSYS-1.0.11 -- I'll need to discuss that with Cesar. > I have both XP and Vista both have the same problem. > Can you redirect or create a normal directory for /usr using fstab ? No; nor should you try. The philosophy is to provide an emulation of the build environment which will be found on UNIX, with the common tools as required by the GCS. Various flavours of UNIX are unable to agree on where certain tools should be installed; some will put them in /bin, others in /usr/bin. Some build scripts assume tools will be in /bin, where in reality they are in /usr/bin, and vice versa. Such scripts are technically broken, but in an attempt to accommodate them, most modern UNIXes symlink the tools, so that they appear to co-exist in both directories. MSYS can't do this, because Woe32 doesn't support symlinks; (even Vista's claimed support for them is apparently completely broken). Instead, MSYS makes /usr a virtual loopback mount to its own virtual file system root; thus /bin and /usr/bin will *always* show the same content, (and indeed, so will / and /usr). If this interferes with you build system, then sorry, but it's your build system that is broken. You should *not* be trying to install to *either* /bin or /usr/bin; you should use /usr/local/bin, (which will also appear as /local/bin), or /mingw instead. Regards, Keith. |
From: Aaron G. <an...@be...> - 2007-05-20 00:29:11
|
> On Saturday 19 May 2007 17:56, Aaron Gray wrote: >> the mount command doesn't work in vista. > > It does, to the extent that, IIRC, is documented in the README.rtf file > which came along with MSYS; you *did* read it, didn't you? In case > not, then FTR it works only without arguments, to report the mount > table state, as defined via /etc/fstab. If you wish to manipulate > this, then you edit /etc/fstab, as explained in the fine manual, i.e. > this self same README.rtf file, which you apparently didn't read. > > FWIW, I have developed my own variation on MSYS' mount command, which > does accept arguments, and so behaves more as might be expected. We > may consider putting something like that into MSYS-1.0.12; maybe even > into the upcoming MSYS-1.0.11 -- I'll need to discuss that with Cesar. > >> I have both XP and Vista both have the same problem. >> Can you redirect or create a normal directory for /usr using fstab ? > > No; nor should you try. > > The philosophy is to provide an emulation of the build environment which > will be found on UNIX, with the common tools as required by the GCS. > Various flavours of UNIX are unable to agree on where certain tools > should be installed; some will put them in /bin, others in /usr/bin. > Some build scripts assume tools will be in /bin, where in reality they > are in /usr/bin, and vice versa. Such scripts are technically broken, > but in an attempt to accommodate them, most modern UNIXes symlink the > tools, so that they appear to co-exist in both directories. MSYS can't > do this, because Woe32 doesn't support symlinks; (even Vista's claimed > support for them is apparently completely broken). Instead, MSYS > makes /usr a virtual loopback mount to its own virtual file system > root; thus /bin and /usr/bin will *always* show the same content, (and > indeed, so will / and /usr). > > If this interferes with you build system, then sorry, but it's your > build system that is broken. You should *not* be trying to install to > *either* /bin or /usr/bin; you should use /usr/local/bin, (which will > also appear as /local/bin), or /mingw instead. AFAICT This messes up GIT. GIT is looking for /usr/share/git-core/templates but does not seem to be able to find it. Aaron |
From: Keith M. <kei...@us...> - 2007-05-20 16:13:56
|
On Sunday 20 May 2007 01:28, Aaron Gray wrote: > GIT is looking for /usr/share/git-core/templates but does not seem to > be able to find it. Well, there is no reason at all why you cannot create a directory called `/usr/share/git-core/templates', (which by virtue of MSYS' automatic mounting arrangement would also appear as `/share/git-core/templates'). However, configuring GIT for installation with a prefix of `/usr/local' or `/mingw' rather than '/usr' would be more sensible. This is particularly true if you are still using MSYS-1.0.10, or earlier, rather than the MSYS-1.0.11 development snapshots; if you install any GIT executables into `/usr/bin', that really *will* break your installation, unless you are building with the MSYS developers' compiler suite, and hence making them depend on MSYS-1.0.dll. Regards, Keith. |
From: Aaron G. <an...@be...> - 2007-05-20 16:47:25
|
> On Sunday 20 May 2007 01:28, Aaron Gray wrote: >> GIT is looking for /usr/share/git-core/templates but does not seem to >> be able to find it. > > Well, there is no reason at all why you cannot create a directory called > `/usr/share/git-core/templates', (which by virtue of MSYS' automatic > mounting arrangement would also appear as `/share/git-core/templates'). > However, configuring GIT for installation with a prefix of `/usr/local' > or `/mingw' rather than '/usr' would be more sensible. > > This is particularly true if you are still using MSYS-1.0.10, or > earlier, rather than the MSYS-1.0.11 development snapshots; if you > install any GIT executables into `/usr/bin', that really *will* break > your installation, unless you are building with the MSYS developers' > compiler suite, and hence making them depend on MSYS-1.0.dll. Yes, tried that, maybe its a "bug" in GIT then. I will try getting the source rather than using the binary instillation. Thanks, Aaron |
From: Keith M. <kei...@to...> - 2007-05-21 10:07:13
|
Aaron Gray wrote, quoting me: >>> GIT is looking for /usr/share/git-core/templates but does not seem to >>> be able to find it. >> >> Well, there is no reason at all why you cannot create a directory called >> `/usr/share/git-core/templates', (which by virtue of MSYS' automatic >> mounting arrangement would also appear as `/share/git-core/templates'). >> However, configuring GIT for installation with a prefix of `/usr/local' >> or `/mingw' rather than '/usr' would be more sensible. >> >> This is particularly true if you are still using MSYS-1.0.10, or >> earlier, rather than the MSYS-1.0.11 development snapshots; if you >> install any GIT executables into `/usr/bin', that really *will* break >> your installation, unless you are building with the MSYS developers' >> compiler suite, and hence making them depend on MSYS-1.0.dll. > > Yes, tried that, maybe its a "bug" in GIT then. > > I will try getting the source rather than using the binary instillation. A binary build, precompiled for MSYS? Seems kind of implausible. Where did you find it? To run under MSYS, in the absence of an MSYS component build, which we don't provide, you should be looking for a *native* Woe32 build; that definitely should not have any precompiled dependency on a UNIX path such as `/usr/share/git-core/templates' -- it should be in native Woe32 format. This alone would make me suspect an invalid build, unless of course it's really a Cygwin build, in which case that's the environment in which you should be deploying it. Your best bet, to get it running under MSYS, would be to build from source, which may involve a (possibly substantial) porting effort. Regards, Keith. |
From: Aaron G. <an...@be...> - 2007-05-21 14:03:10
|
>> I will try getting the source rather than using the binary instillation. > > A binary build, precompiled for MSYS? Seems kind of implausible. Where > did you find it? For MinGW... Source :- http://repo.or.cz/w/git/mingw.git Binary :- http://lilypond.org/git/binaries/mingw/ > To run under MSYS, in the absence of an MSYS component build, which we > don't provide, you should be looking for a *native* Woe32 build; that > definitely should not have any precompiled dependency on a UNIX path > such as `/usr/share/git-core/templates' -- it should be in native Woe32 > format. This alone would make me suspect an invalid build, unless of > course it's really a Cygwin build, in which case that's the environment > in which you should be deploying it. > > Your best bet, to get it running under MSYS, would be to build from > source, which may involve a (possibly substantial) porting effort. Aaron |
From: Keith M. <kei...@to...> - 2007-05-21 14:41:04
|
>> A binary build, precompiled for MSYS? Seems kind of implausible. >> Where did you find it? > > For MinGW... > > Source :- > http://repo.or.cz/w/git/mingw.git > > Binary :- > http://lilypond.org/git/binaries/mingw/ Ok, so they look like they should be for native Woe32, and built using MinGW. However, neither is an officially supported MinGW package; you may get more informed support from the respective package maintainers. Regards, Keith. |