./Configure -doptimize='-g'
make
Making x2p stuff
make[1]: Entering directory `/home/william/p/perl-5.8.8/x2p'
You haven't done a "make depend" yet!
make[1]: *** [hash.o] Error 1
make[1]: Leaving directory `/home/william/p/perl-5.8.8/x2p'
make: *** [translators] Error 2
When I run
make depend
sh ./makedepend MAKE=make
./makedepend: Already running, exiting.
test -s perlmain.c && touch perlmain.c
cd x2p; make depend
make[1]: Entering directory `/home/william/p/perl-5.8.8/x2p'
sh ../makedepend MAKE=make
../makedepend: Already running, exiting.
make[1]: Leaving directory `/home/william/p/perl-5.8.8/x2p'
How to solve this ? Thanks
Do not multi-post!
http://www.nntp.perl.org/group/perl.beginners/2008/05/msg100925.html
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
Ops, sorry, I thought that was different mailing list.
I was thrilled at first, because I thought finally someone has given
the solution. ;-)
So what? By multi-posting, without letting people know that you did,
there is a risk that people spend time helping you on one place without
knowing that the problem was resolved on the other place. Please show
the Perl community some respect by not abusing its resources that way.
Ok, maybe I put my question in this way. How can I build another
version of Perl with the debugging information ? So that I can still
use the non-debugging version of Perl ? Thanks
I have done this before and found it very helpful, because the
solution that both group given are different and helpful, they became
part and parcel to complete each other. When I got the solution, I did
nd would post the solution on the other if I got the solution on the
respective group.
Btw, I did respect the community and said sorry, I never know that
comp.lang.perl.misc is almost the same.
> On May 26, 8:44 pm, Gunnar Hjalmarsson <nore...@gunnar.cc> wrote:
>> Keenlearner wrote:
>> > On May 26, 8:16 pm, Gunnar Hjalmarsson <nore...@gunnar.cc> wrote:
>> >> Keenlearner wrote:
>> >>> Hello, I have perl interpreter install using sypnatic package
>> >>> manager,
>
>> >>> now I want to reinstall perl from the source ...
>> >> Do not
>> >> multi-post!http://www.nntp.perl.org/group/perl.beginners/2008/05
> /msg100925.html
>>
>> > Ops, sorry, I thought that was different mailing list.
That is a different group, that's right.
Therefore, you should not multi-post.
If you do not understand what you are being asked not to do, you could
use a search engine to figure it out:
http://www.google.com/search?q=multi-posting
>> --
>> Gunnar Hjalmarsson
>> Email:http://www.gunnar.cc/cgi-bin/contact.pl
Do *NOT* quote signs.
> I have done this before and found it very helpful, because the
> solution that both group given are different and helpful,
See, that is exactly what you are being asked not to do.
Why should people waste time and energy answering a question you already
got answered somewhere else.
> they became part and parcel to complete each other.
That's great for you.
> Btw, I did respect the community and said sorry, I never know that
> comp.lang.perl.misc is almost the same.
I don't know what you mean by that but you are probably mistaken.
Sinan
--
A. Sinan Unur <1u...@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
comp.lang.perl.misc guidelines on the WWW:
http://www.rehabitation.com/clpmisc/
> How can I build another version of Perl with the debugging information ?
Read the instructions that came with the distribution.
> So that I can still use the non-debugging version of Perl ? Thanks
Install the debugging version in a different location.
Find out how to do that by reading the instructions rather than asking
someone else to read them for you.
Sorry, apologise me. I would read. Thanks.
Actually it _is_ a different list. This news group and the nntp.perl.org
server are separate, so calling it multi-posting is not really correct
(that implies posting to multiple groups on the same server.) I don't
see why one cannot post in both areas, as it can increase the possible
results (since they are completely separate.)
--
szr
One *can* post separately to both places but IMO one should usually not
do so without *very* good reason. So far as I can see, the arguments
against multi-posting mostly apply.
- People who frequent both places end up seeing the question several times.
- People who don't frequent both places end up wasting time answering
questions that have been already answered elsewhere.
etc.
There may be an argument for posting first in one place, waiting a week
and posting in another place if no answers have been obtained. In this
case it would be polite to mention that the question has already been
posted in the other place. I doubt this is ever necessary for the two
places in question.
Just my ¤0.02 worth.
--
RGB
Because doing so is ruthless.
To me, the fact that they are on separate servers is irrelevant. IMO,
you abuse the community just as much by posting to both simultaneously,
whether the correct term is multi-posting or something else.
>it can increase the possible
> results (since they are completely separate.)
It happened here that it has higher probability of getting various
and
better result. Also I learned more. I would not want to waste my time
too, if posting at multi places would give the same result.
http://www.nntp.perl.org/group/perl.beginners/2008/05/msg100775.html
http://groups.google.com/group/comp.lang.perl.misc/browse_thread/thread/5e2d923994e833d9#
> There may be an argument for posting first in one place, waiting a week
> and posting in another place if no answers have been obtained. In this
> case it would be polite to mention that the question has already been
> posted in the other place.
I would try hard not to multi-post, but if I need so I would do the
above.
Rather than keep arguing this, does anyone still remember the main
problem ?
After I ran,
./Configure -Dusethreads -Dprefix=p/perl/ -Doptimize='-g'
Then
make
Making DynaLoader (static)
make[1]: Entering directory `/home/william/p/perl-5.8.8/ext/
DynaLoader'
Makefile out-of-date with respect to ../../lib/Config.pm ../../
config.h
Cleaning current config before rebuilding Makefile...
make -f Makefile.old clean > /dev/null 2>&1
../../miniperl "-I../../lib" "-I../../lib" Makefile.PL
"INSTALLDIRS=perl" "PERL_CORE=1" "LIBPERL_A=libperl.a"
Processing hints file hints/linux.pl
Writing Makefile for DynaLoader
==> Your Makefile has been rebuilt. <==
==> Please rerun the make command. <==
false
make[1]: *** [Makefile] Error 1
make[1]: Leaving directory `/home/william/p/perl-5.8.8/ext/
DynaLoader'
Extracting xsubpp (with variable substitutions)
make[1]: Leaving directory `/home/william/p/perl-5.8.8/utils'
Making x2p stuff
make[1]: Entering directory `/home/william/p/perl-5.8.8/x2p'
You haven't done a "make depend" yet!
make[1]: *** [hash.o] Error 1
make[1]: Leaving directory `/home/william/p/perl-5.8.8/x2p'
make: *** [translators] Error 2
Above are the two portions of errors that I am having. Thanks
I agree when it's on the same service or network, but when it's two
complete separate domains it would seem perfectly reasonable, as long as
the poster takes care to pass on accepted answers to the other thread.
This would be sort of like cross-posting, in an indirect way.
> To me, the fact that they are on separate servers is irrelevant. IMO,
> you abuse the community just as much by posting to both
> simultaneously, whether the correct term is multi-posting or
> something else.
Again, I disagree that it's just plain wrong to post in multiple venues.
As long as the person posting informs the other venues of solutions that
they got or derived from another, it shouldn't be a problem.
--
szr
http://bugs.openembedded.org/show_bug.cgi?id=2035
http://www.nntp.perl.org/group/perl.perl5.porters/2008/02/msg133863.html
PS. Slowly slowy I climb, although I was thrown with rocks and people
ignore me while I am climbing because of a mistake that I made which
could not be forgiven by them, at time it is so daunting. But with
persistent and perseverance, I manage to reach the top of the
mountain. A thousand miles begins with a single step.
Sorry and thanks
WIlliam
I didn't really make a mistake. Some people like to make way too much
hype about such trivial matters. Like I said, there has never really
been any taboo against posting in multiple completely separate venues
that are on the same subject, though it is customary to, if you receive
a useful answer in venue "A", to share that answer in "B", "C", etc.
Again, I compare this to cross posting in venues (like Usenet) that have
such a facility. Many people would see not sharing an answer as rude,
not the multiple posting itself, though there are some that have yet to
distinguish between personal opinions and guidelines all should adhere
to.
--
szr