Menu
▾
▴
corelinux-develop
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-30 20:40:05
|
1- the documentation missing files did you check in /usr/doc/libcorelinux-doc-0.4.26/ps /usr/doc/libcorelinux-doc-0.4.26/pdf I have them 2- cleanup I just added the rule it was commented sorry 3- shared library links corrected I included only libcl++.so.* and not libcl++.so* that's why it wasn't there I will update the cvs I just check the rpm building on my side PS: * the -j 2 option for make will be removed also(not everybody have a bi-pro) regards C. -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | If it doesn't work, force it. Cambridge MA 02139 | If it breaks, it needed Tel (Office) : (00 1) (617) 253 0229 | replacing anyway. Fax (Office) : (00 1) (617) 258 8559 | http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Frank V. C. <fr...@co...> - 2000-07-30 20:50:12
|
Christophe Prud'homme wrote: > > 1- the documentation missing files > > did you check in > /usr/doc/libcorelinux-doc-0.4.26/ps > /usr/doc/libcorelinux-doc-0.4.26/pdf They were empty. The actual build files were in the /latex directory but never made it to gzip or rpm. I will run again and pipe output to file. > 2- cleanup > > I just added the rule > it was commented sorry Checked in? > 3- shared library links > > corrected I included only libcl++.so.* and not libcl++.so* > that's why it wasn't there Why? Don't -lcl look for libcl++.so ? > I will update the cvs > I just check the rpm building on my side > > PS: > * the -j 2 option for make will be removed also(not everybody have a bi-pro) I have one I just sold at a tag sale (2x133 PII). I'm saving up for a MP zeon machine. > regards > C. > > -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | If it doesn't work, force it. > Cambridge MA 02139 | If it breaks, it needed > Tel (Office) : (00 1) (617) 253 0229 | replacing anyway. > Fax (Office) : (00 1) (617) 258 8559 | > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-30 20:57:07
|
>>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:
Frank> Christophe Prud'homme wrote:
>>
>> 1- the documentation missing files
>>
>> did you check in /usr/doc/libcorelinux-doc-0.4.26/ps /usr/doc/libcorelinux-doc-0.4.26/pdf
Frank> They were empty. The actual build files were in the /latex directory but never made it to
Frank> gzip or rpm. I will run again and pipe output to file.
I will investigate also
>> 2- cleanup
>>
>> I just added the rule it was commented sorry
Frank> Checked in?
Not yet
>> 3- shared library links
>>
>> corrected I included only libcl++.so.* and not libcl++.so* that's why it wasn't there
Frank> Why? Don't -lcl look for libcl++.so ?
at some point there is a rule saying what of kind files you want in certain location
and I put this . between so and * therefore libcl++.so was not included
now it is fixed
Frank> I'm saving up for a MP zeon machine.
what is that ?
zeon == xeon ?
if so we have a xeon here and I found that the xeon are much ado about nothing
It is more expensive and the gain is not so clear
|
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-30 21:01:30
|
>> 2- cleanup
>>
>> I just added the rule it was commented sorry
Frank> Checked in?
there is stuff in /var/tmp/libcorexxxxx and /usr/src/redhat/libcorelxxxxxx
do you want both removed ?
neither were removed
now /var/tmp/libcorexxxx is removed
and /usr/src/redhat/libcorexxx is cleanup (using make distclean)
comments ?
C.
|
|
From: Frank V. C. <fr...@co...> - 2000-07-30 21:00:58
|
Christophe Prud'homme wrote: > > >>>>> "Frank" == Frank V Castellucci <fr...@co...> writes: > > Frank> Christophe Prud'homme wrote: > >> > >> 1- the documentation missing files > >> > >> did you check in /usr/doc/libcorelinux-doc-0.4.26/ps /usr/doc/libcorelinux-doc-0.4.26/pdf > > Frank> They were empty. The actual build files were in the /latex directory but never made it to > Frank> gzip or rpm. I will run again and pipe output to file. > I will investigate also ok > > >> 2- cleanup > >> > >> I just added the rule it was commented sorry > > Frank> Checked in? > Not yet cool > > >> 3- shared library links > >> > >> corrected I included only libcl++.so.* and not libcl++.so* that's why it wasn't there > > Frank> Why? Don't -lcl look for libcl++.so ? > at some point there is a rule saying what of kind files you want in certain location > and I put this . between so and * therefore libcl++.so was not included > now it is fixed your a GOD! > > Frank> I'm saving up for a MP zeon machine. > what is that ? > zeon == xeon ? heh, heh, yes Xeon > if so we have a xeon here and I found that the xeon are much ado about nothing > It is more expensive and the gain is not so clear No, I have done benchmarks with UP and SMP with PIII and Xeon, with the kind of workloads I have (lots of ephemeral (in memory) stuff) it has about 25-40% improvement in throughput. Frank |
|
From: Frank V. C. <fr...@co...> - 2000-07-30 21:05:28
|
Christophe Prud'homme wrote: > > >> 2- cleanup > >> > >> I just added the rule it was commented sorry > > Frank> Checked in? > > there is stuff in /var/tmp/libcorexxxxx and /usr/src/redhat/libcorelxxxxxx > do you want both removed ? > neither were removed > now /var/tmp/libcorexxxx is removed > and /usr/src/redhat/libcorexxx is cleanup (using make distclean) Hmm. So your methodology is to do build then distclean? That's fine. And yes, it is good that ANYTHING in /var/tmp is removed. I will keep looking after this build to see what else so hold off for about 20 mins. Is that ok? -- Frank V. Castellucci |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-30 21:12:45
|
>>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:
Frank> Hmm. So your methodology is to do build then distclean? That's fine. And yes, it is good
the make distclean is done in /usr/src/redhat/libcorelinux-0.4.26 not in your cvs copy
the thing is that the make rpm create a dist and copy it in /usr/src/redhat/SOURCES
(rpm requirement) the sources are untargzipped in /usr/src/redhat/BUILD
Frank> that ANYTHING in /var/tmp is removed. I will keep looking after this build to see what
Frank> else so hold off for about 20 mins. Is that ok?
yes I will update in a minute
as for the doc for me it works fine. strange.
--
Christophe Prud'homme | Its name is Public Opinion.
MIT, 77, Mass Ave, Rm 3-243 | It is held in reverence.
Cambridge MA 02139 | It settles everything.
Tel (Office) : (00 1) (617) 253 0229 | Some think it is the voice of God.
Fax (Office) : (00 1) (617) 258 8559 | -- Mark Twain
http://augustine.mit.edu/~prudhomm |
Following the hacker spirit
|
|
From: Frank V. C. <fr...@co...> - 2000-07-30 21:16:33
|
Christophe Prud'homme wrote: > > >>>>> "Frank" == Frank V Castellucci <fr...@co...> writes: > Frank> Hmm. So your methodology is to do build then distclean? That's fine. And yes, it is good > the make distclean is done in /usr/src/redhat/libcorelinux-0.4.26 not in your cvs copy > the thing is that the make rpm create a dist and copy it in /usr/src/redhat/SOURCES > (rpm requirement) the sources are untargzipped in /usr/src/redhat/BUILD Everything but the resulting RPM files should be removed. Because it does not do delta builds, as you pointed out, it is just a waste of space to keep it around. > > Frank> that ANYTHING in /var/tmp is removed. I will keep looking after this build to see what > Frank> else so hold off for about 20 mins. Is that ok? > yes I will update in a minute > > as for the doc for me it works fine. strange. I'm running again with a log to see what the problem may be. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-30 21:24:07
|
ok I update the spec and Makefile.am, now everything should be ok! except the doc maybe C. |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-07-30 21:33:44
|
I forgot to mention that it would be good to keep the way the examples are named I mean the one containing the main() function because that is how the Makefile generation script(debian/genmake/pl) knows how to build the executables. And don't duplicate filenames :) because everything is copied in the same directory C. |
|
From: Frank V. C. <fr...@co...> - 2000-07-30 21:36:02
|
Christophe Prud'homme wrote: > > I forgot to mention that it would be good > to keep the way the examples are named I mean the one containing the main() > function because that is how the Makefile generation script(debian/genmake/pl) > knows how to build the executables. > And don't duplicate filenames :) because everything is copied in the same > directory > > C. Ok, no PDF and PS again. I have log file (although nothing seems clear). Can you IRC irc.linux.com #sourceforge ? That way I can describe what I see? -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
