MinGW - Minimalist GNU for Windows

Hi There

Many apologies for the "html-ised post", Im using outlook on a friends
machine at the moment ( poor excuse I know )

> What is the output of
>    type -a perl
> from with the MSYS shell?

perl is /mingw/bin/perl
perl is /mingw/bin/perl

( no typo here,  it really does report it twice )



Regards

Dave Rowbotham

http://slashwilts.org

Dave Rowbotham wrote:
> Hi There
>  
>  > What is the output of
>  >    type -a perl
>  > from with the MSYS shell?
>  
> perl is /mingw/bin/perl
> perl is /mingw/bin/perl
>  

So I don't have to go find the stored mail, what is our environment again?

CPU MODEL:
OS VERSION:

Earnie.

Hi There

> So I don't have to go find the stored mail, what is our environment again?
>
> CPU MODEL:
> OS VERSION:
>
> Earnie.


CPU is AMD K6-2 450
OS is Win98 ME ( 4.90.3000 )

FWIW heres the other bits n peices I have on the system that may be relevant

Ram = 192Mb
Video Card = ATI Rage128VR 32Mb AGP
Sound = ESS Solo-1 1938S
Motherboard = ALI 1542 based ( I cant remember if its QDI or SuperMicro )
Network card = Unbranded RTL8029 PCI


Thanks for your time :-)

Cheers

Dave

http://slashwilts.org

Dave Rowbotham wrote:
> Hi There
> 
> 
>>So I don't have to go find the stored mail, what is our environment again?
>>
>>CPU MODEL:
>>OS VERSION:
>>
>>Earnie.
> 
> 
> 
> CPU is AMD K6-2 450
> OS is Win98 ME ( 4.90.3000 )
> 

By Win98 ME, do you mean an original Win98 upgraded to ME?

Have you installed various OS patches?

> FWIW heres the other bits n peices I have on the system that may be relevant
> 
> Ram = 192Mb
> Video Card = ATI Rage128VR 32Mb AGP
> Sound = ESS Solo-1 1938S
> Motherboard = ALI 1542 based ( I cant remember if its QDI or SuperMicro )
> Network card = Unbranded RTL8029 PCI
> 
> 
> Thanks for your time :-)
> 

I aim to please. :)  I'm running out of ideas.  I will be sure to 
rebuild perl before I release msysDTK-1.0.0 next week.  Perhaps a fresh 
build will help, but that's like sticking a needle in a haystack trying 
to find the roach, i.e. it's not likely to help.

Earnie.

>From: "Dave Rowbotham" <gandalf@...>
>To: <MinGW-MSYS@...>
>Subject: Re: [Mingw-msys] Re: Perl causes an error in libperl.dll
>Date: Sat, 30 Nov 2002 12:59:47 -0000
>
>Hi There
>
> > What is the output of
> >    type -a perl
> > from with the MSYS shell?
>
>perl is /mingw/bin/perl

Apparently you extracted msysDTK into your MinGW directory (/mingw) instead 
of your MSYS root directory (/). Unfortunately there isn't an uninstall for 
tar.gz files so you may need to remove and reinstall MinGW if you want to be 
sure msysDTK is uninstalled.


>perl is /mingw/bin/perl
>
>( no typo here,  it really does report it twice )

That just means /mingw/bin is in your PATH twice (which is fine).

>
>
>
>Regards
>
>Dave Rowbotham
>
>http://slashwilts.org

Luke


_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

Luke Dunstan wrote:
> 
> 
> 
>> From: "Dave Rowbotham" <gandalf@...>
>> To: <MinGW-MSYS@...>
>> Subject: Re: [Mingw-msys] Re: Perl causes an error in libperl.dll
>> Date: Sat, 30 Nov 2002 12:59:47 -0000
>>
>> Hi There
>>
>> > What is the output of
>> >    type -a perl
>> > from with the MSYS shell?
>>
>> perl is /mingw/bin/perl
> 
> 
> Apparently you extracted msysDTK into your MinGW directory (/mingw) 
> instead of your MSYS root directory (/). Unfortunately there isn't an 
> uninstall for tar.gz files so you may need to remove and reinstall MinGW 
> if you want to be sure msysDTK is uninstalled.
> 

Well, nice catch Luke.  But with 1.0.8 it shouldn't matter, although it 
would still be faster for msys-1.0.dll dependent binaires to live in 
/bin.  Perhaps the error is due to reading the binary to find the dll 
entries to figure out if it is an MSYS binary.

Earnie.

On Saturday 30 November 2002 5:56 pm, Earnie Boyd wrote:
> I aim to please. :)  I'm running out of ideas.  I will be sure to
> rebuild perl before I release msysDTK-1.0.0 next week.

Ok, that sounds good.

I just downloaded MsysDVLPR , I havnt looked at it yet, does it contain e=
verything I need to  build Msys perl, or do I do that some other way?=20

Maybe if I can build Msys on my system I can figure out whats going on ( =
results posted back here of course ), or does MsysDVLPR rely on the perl =
in the toolkit?

My Win98ME is an upgrade over Win98SE, I also keep it regularly updated v=
ia microsofts web updates program. =20

Cheers

Dave

http://slashwilts.org

Hi There

On Saturday 30 November 2002 7:21 pm, you wrote:

> > Apparently you extracted msysDTK into your MinGW directory (/mingw)
> > instead of your MSYS root directory (/).
I was running out of ideas ;-),

>> Unfortunately there isn't an
> > uninstall for tar.gz files so you may need to remove and reinstall Mi=
nGW
> > if you want to be sure msysDTK is uninstalled.
Yes indeed, this wouldnt be the first time I have blown up a compiler=20
installation ;-)=20

I will delete everything ( mingw compiler folder and msys ), and reinstal=
l=20
Msys , MsysDTK and MingW . Any likely theories on a prefered installation=
=20
order/destination accepted.

Cheers

Dave

Dave Rowbotham wrote:
> Hi There
> 
> On Saturday 30 November 2002 7:21 pm, you wrote:
> 
> 
>>>Apparently you extracted msysDTK into your MinGW directory (/mingw)
>>>instead of your MSYS root directory (/).
>>
> I was running out of ideas ;-),
> 
> 
>>>Unfortunately there isn't an
>>>uninstall for tar.gz files so you may need to remove and reinstall MinGW
>>>if you want to be sure msysDTK is uninstalled.
>>
> Yes indeed, this wouldnt be the first time I have blown up a compiler 
> installation ;-) 
> 
> I will delete everything ( mingw compiler folder and msys ), and reinstall 
> Msys , MsysDTK and MingW . Any likely theories on a prefered installation 
> order/destination accepted.
> 

It depends.  Some like to keep the directories separated in different 
roots.  So if you like

c:/mingw
c:/msys/1.0

Then install mingw first.

If you like

c:/msys/1.0
c:/msys/1.0/mingw

Then install msys first.

Earnie.

gandalf@... wrote:
> On Saturday 30 November 2002 5:56 pm, Earnie Boyd wrote:
> 
>>I aim to please. :)  I'm running out of ideas.  I will be sure to
>>rebuild perl before I release msysDTK-1.0.0 next week.
> 
> 
> Ok, that sounds good.
> 
> I just downloaded MsysDVLPR , I havnt looked at it yet, does it contain everything I need to  build Msys perl, or do I do that some other way? 
> 

Yes you should be able to build perl.  Make sure to unpack in /.

> Maybe if I can build Msys on my system I can figure out whats going on ( results posted back here of course ), or does MsysDVLPR rely on the perl in the toolkit?
> 

The only reason for perl is autoconf and automake which you don't need 
to build perl.  Any help with MSYS is much appreciated.  If you plan to 
help, come join us in the mingw-dvlpr group.

> My Win98ME is an upgrade over Win98SE, I also keep it regularly updated via microsofts web updates program.  
> 

We now know half the problem, so, this probably isn't relavant.

Earnie.

>From: Earnie Boyd <earnie_boyd@...>
>Reply-To: MinGW-MSYS@...
>To: Luke Dunstan <coder_infidel@...>
>CC: gandalf@...,  MinGW-MSYS@...
>Subject: Re: [Mingw-msys] Re: Perl causes an error in libperl.dll
>Date: Sat, 30 Nov 2002 14:21:33 -0500
>
>Luke Dunstan wrote:
>>
>>
>>
>>>From: "Dave Rowbotham" <gandalf@...>
>>>To: <MinGW-MSYS@...>
>>>Subject: Re: [Mingw-msys] Re: Perl causes an error in libperl.dll
>>>Date: Sat, 30 Nov 2002 12:59:47 -0000
>>>
>>>Hi There
>>>
>>> > What is the output of
>>> >    type -a perl
>>> > from with the MSYS shell?
>>>
>>>perl is /mingw/bin/perl
>>
>>
>>Apparently you extracted msysDTK into your MinGW directory (/mingw) 
>>instead of your MSYS root directory (/). Unfortunately there isn't an 
>>uninstall for tar.gz files so you may need to remove and reinstall MinGW 
>>if you want to be sure msysDTK is uninstalled.
>>
>
>Well, nice catch Luke.  But with 1.0.8 it shouldn't matter, although it 
>would still be faster for msys-1.0.dll dependent binaires to live in /bin.  
>Perhaps the error is due to reading the binary to find the dll entries to 
>figure out if it is an MSYS binary.
>
>Earnie.

Ideally it shouldn't matter, but IIRC this was a crash rather than the DLL 
not found error. I gather that many GNU and other applications hardcode 
installation paths in various places, and probably most ports of this 
software to MSYS/Cygwin wouldn't change this because it is just easier not 
to. This is in contrast to, for example, MinGW GCC which has been modified 
to use paths relative to the executable directory. I think it is better to 
just use the approved installation directory for most MSYS-dependent 
software, because finding these problems can indeed be a needle/haystack 
exercise.

Luke


Luke


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Luke Dunstan wrote:
> 
> 
> Ideally it shouldn't matter, but IIRC this was a crash rather than the 
> DLL not found error. I gather that many GNU and other applications 
> hardcode installation paths in various places, and probably most ports 
> of this software to MSYS/Cygwin wouldn't change this because it is just 
> easier not to. This is in contrast to, for example, MinGW GCC which has 
> been modified to use paths relative to the executable directory. I think 
> it is better to just use the approved installation directory for most 
> MSYS-dependent software, because finding these problems can indeed be a 
> needle/haystack exercise.
> 

Yes, you're correct.

Earnie.

Hi There,

FWIW,

I installed clean MingW into d:\mingw

and MSysDTK the msys '/' , then I ran gdb perl which gave me this output

[>>>snip<<<]
Starting program: D:\MSYS\BIN/perl.exe

Program received signal SIGILL, Illegal instruction
0x61a52849 in ?? ()
(gdb)
[>>>snip<<]


Cheers

Dave