Make problem #6302
Comments
From whamad@strong.comHi, I just downloaded perl 5.6.1 I ran the Configure Then, when I did run the make command I am getting this make: *** No rule to make target `<built-in>', needed by `miniperlmain.o'. Do you know what am I missing?? Waleed *****DISCLOSURE STATEMENT***** |
From @doughera88On 12 Feb 2003, Waleed Hamad wrote:
The fix is simply to delete all the lines in 'makefile' that contain This is also fixed in perl-5.8.0, which you might consider using instead.
Nothing, really. It's a change in gcc-3's output that appeared after -- |
From whamad@strong.comAndy, I do have a quick question though, The question I have is, Please get back to me on this, and again thank you so much for your help. Waleed -----Original Message----- On 12 Feb 2003, Waleed Hamad wrote:
The fix is simply to delete all the lines in 'makefile' that contain This is also fixed in perl-5.8.0, which you might consider using instead.
Nothing, really. It's a change in gcc-3's output that appeared after -- *****DISCLOSURE STATEMENT***** |
From whamad@strong.comAndy, Ran the make command and I got the following make: *** No rule to make target `<command', needed by `miniperlmain.o'. Does that mean I need to delete the <command line> as well?? Waleed -----Original Message----- On 12 Feb 2003, Waleed Hamad wrote:
The fix is simply to delete all the lines in 'makefile' that contain This is also fixed in perl-5.8.0, which you might consider using instead.
Nothing, really. It's a change in gcc-3's output that appeared after -- *****DISCLOSURE STATEMENT***** |
From whamad@strong.comAndy, Ran the make command and I got the following make: *** No rule to make target `<command', needed by `miniperlmain.o'. Does that mean I need to delete the <command line> as well?? Waleed -----Original Message----- On 12 Feb 2003, Waleed Hamad wrote:
The fix is simply to delete all the lines in 'makefile' that contain This is also fixed in perl-5.8.0, which you might consider using instead.
Nothing, really. It's a change in gcc-3's output that appeared after -- *****DISCLOSURE STATEMENT***** |
From whamad@strong.comAndy, I deleted both <build in> and <command line> from the makefile Making utilities Making x2p stuff Any Suggestions?? Please let me know, Thanks, -----Original Message----- On 12 Feb 2003, Waleed Hamad wrote:
The fix is simply to delete all the lines in 'makefile' that contain This is also fixed in perl-5.8.0, which you might consider using instead.
Nothing, really. It's a change in gcc-3's output that appeared after -- *****DISCLOSURE STATEMENT***** |
From @TuxOn Thu 13 Feb 2003 16:05, Waleed Hamad <whamad@strong.com> wrote:
Yep. Safe to remove them.
-- |
From @TuxOn Thu 13 Feb 2003 16:12, Waleed Hamad <whamad@strong.com> wrote:
The easiest (but not the fastest) solution is to change makedepend.SH $sed \ Or, if you do it the .* way $sed \ and then restart all over. # make distclean
-- |
From @nwc10On Thu, Feb 13, 2003 at 08:53:09AM -0600, Waleed Hamad wrote:
You mean about 40 additional modules downloaded from CPAN?
It's safest to build them once for your perl 5.6.1 perl5.6.1 Makefile.PL and then again for perl 5.8.0 perl5.8.0 Makefile.PL (where you replace perl5.6.1 and perl5.8.0 with your names for your two Or if you prefer, perl5.6.1 -MCPAN -e shell and perl5.8.0 -MCPAN -e shell Nicholas Clark |
From whamad@strong.comThank you so very much for all the help that you are trying to provide. I am still having the problem though, and I hope you will continue helping After I received your email here is what I have done. #1. Ran the make distclean I got this error make: *** No rule to make target `<.*>', needed by `miniperlmain.o'. Stop. So Are you trying to tell me that instead of doing these steps I just #1. Edit the makedepend.SH file #2. ran the make distclean and the Configure again If that is the case, what shall I do with the <command line> ?? Please let me know, -----Original Message----- On Thu 13 Feb 2003 16:12, Waleed Hamad <whamad@strong.com> wrote:
The easiest (but not the fastest) solution is to change makedepend.SH $sed \ Or, if you do it the .* way $sed \ and then restart all over. # make distclean
-- *****DISCLOSURE STATEMENT***** |
From @TuxOn Thu 13 Feb 2003 16:58, Waleed Hamad <whamad@strong.com> wrote:
Swap point 2 and 3
-- |
From whamad@strong.comOk, Also what shall I do about the <command line> Please take a look at the steps below
-----Original Message----- On Thu 13 Feb 2003 16:58, Waleed Hamad <whamad@strong.com> wrote:
Swap point 2 and 3
-- *****DISCLOSURE STATEMENT***** |
From @TuxOn Thu 13 Feb 2003 17:13, Waleed Hamad <whamad@strong.com> wrote:
Don't care. It's duplicate at the moment, just leave it in or out, whatever
Looks OK
-- |
From enache@rdslink.roOn Thu, Feb 13, 2003 at 10:13:06AM -0600, Waleed Hamad wrote: Follow this steps and you should be OK: 1. unpack the 5.6.1 distribution (the '$' is the shell prompt) Adi |
From whamad@strong.comAdi, Please look below cc1: warning: changing search order for system directory -----Original Message----- On Thu, Feb 13, 2003 at 10:13:06AM -0600, Waleed Hamad wrote: Follow this steps and you should be OK: 1. unpack the 5.6.1 distribution (the '$' is the shell prompt) Adi *****DISCLOSURE STATEMENT***** |
|
@doughera88 - Status changed from 'open' to 'stalled' |
From @doyPerl 5.6 has been out of support for quite some time. Are there still |
|
The RT System itself - Status changed from 'stalled' to 'open' |
From @jkeenanOn Sun Jun 24 09:45:48 2012, doy wrote:
There has effectively been no correspondence in this RT in nearly ten Thank you very much. |
|
@jkeenan - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#20881 (status was 'rejected')
Searchable as RT20881$
The text was updated successfully, but these errors were encountered: