Why are you so adamant on using MSYS make? You already have MSYS
installed, so MSYS make is already there, yet you complain and nag about
mingw32-make not being able to do what MSYS make does.
Neither I am adamant, nor I am complaining or nagging around. I am a
starter in using MinGW and MSYS. The questions I am asking are reasonable
and context related. And, yes, blindly nodding my head has never ever been
in my nature. So, just I am trying to fiddle with. If you yourself do not
understand where something fails, you cannot help someone in future also.
One small example, earlier I have used Eclipse, but the setup was done by
someone else. It took two whole days for me to understand how the IDE
behaves. Even Eclipse Juno, which I am using as the front end , has bugs,
especially Codan, the static code analyzer. Since last two days, I have
built working setup, messed it up intentionally by changing parameters and
readjusted those. But I can provide better support for one who's using
Eclipse since last one year BUT ONLY on working setup.So, getting
MinGW/MSYS configured with a set of friendly people is not my intention,
nut I want to understand it fully, fiddle with it. If someone catches my
approach of learning wrong, I humbly request him/her to stay away from
responding to my messages.
What part of Unix shells and win32 cmd being different escapes you?
mingw32-make uses cmd, cmd can't understand shell constructs used in
Unix style make files. make uses sh, sh can't understand cmd constructs.
If you have trouble understanding, try the following in cmd:
gcc -c somefile -o somefile$(uname -o)
Can you yourself see that you have intentionally/unintentionally delivered
something useful? This is what I gain when I "complain/nag" around.
Please LISTEN to the advice given, if you don't, you're on your own
Please do not top post and please reply the context properly, your
current messages take huge efforts to read and understand
Actually I couldn't get the meaning of the instruction. It appeared in some
earlier mail also. For the ease of reading, I am quoting the context and
coloring it in blue. Still, how is it incomprehensible? What else should I
do? Please be clearer.
and is giving
a bad impression on you.
If only a newcomer's messaging style irritates someone so much, I assume
he/she is not the right person to help someone in a friendly tech group.
Regarding your personal opinion of having a bad impression, I am NOT really
worried about. But, of course, I will listen to any formatting suggestion
if instructed clearly and properly understood by me
On 19 August 2012 08:26, JonY <jon_y@...> wrote:
> On 8/19/2012 03:31, Dipanjan Das wrote:
> > We do not advise or support adding any MinGW path
> > to the Windows PATH at a global level. We suggest you create a file
> > you call to setup your environment after starting a Windows shell
> > No, I haven't touched my system's PATH variable. I added those two /bin
> > directories in the PATH variable used by Eclipse from within the IDE. It
> > no way affecting Windows command shell.
> > And we do not
> > support the use of MSYS in a shell other than the one MSYS provides.
> > I can't relate the context. If mingw32-make uses sh.exe as its shell,
> > how does the question of using MSYS in an alternative shell comes? It is
> > the other way round, i.e. MinGW using MSYS shell (sh.exe) instead of its
> > regular command interpreter (cmd.exe).
> > So if you find something works in MSYS shell but not in the Windows
> > shell then you're on your own to figure out what is wrong.
> > Why so? Such a friendly community and you people are there.
> > for pointing out. Please clarify the doubts above.
> I feel like the good volunteers are responding to a troll, I'll bite too.
> Why are you so adamant on using MSYS make? You already have MSYS
> installed, so MSYS make is already there, yet you complain and nag about
> mingw32-make not being able to do what MSYS make does.
> What part of Unix shells and win32 cmd being different escapes you?
> mingw32-make uses cmd, cmd can't understand shell constructs used in
> Unix style make files. make uses sh, sh can't understand cmd constructs.
> If you have trouble understanding, try the following in cmd:
> gcc -c somefile -o somefile$(uname -o)
> These things can appear in a makefile.
> Please LISTEN to the advice given, if you don't, you're on your own.
> Please do not top post and please reply the context properly, your
> current messages take huge efforts to read and understand and is giving
> a bad impression on you.
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> MinGW-users mailing list
> This list observes the Etiquette found at
> We ask that you be polite and do the same. Disregard for the list
> etiquette may cause your account to be moderated.
> You may change your MinGW Account Options or unsubscribe at:
> Also: mailto:mingw-users-request@...
Thanks & Regards,