Gabriel Dos Reis wrote:
> Waldek Hebisch <[EMAIL PROTECTED]> writes:
>
> | I looked at hypertex pages and AFAICS I can use a simple sed script
> | in a loop to fix paths in .pht files:
> |
> | sed 's,/doc/viewports/,/share/viewports/,g'
> |
> | After copying images from silver (to correct corrup
> | In principle "user" can type-in parse tree by hand and call the translator.
> | More realistically, one can add code which directly generates Spad like
> | parse trees and then calls translator to output Aldor.
potentially aldor can also generate these parse trees.
memory fails me about why t
Ralf Hemmecke wrote:
> To make it what I did, I included my commands in /trunk/axiom/ChangLog
> (date 2006-09-13 and 2006-09-14). I must have thought that these
> commands might be useful in the future. ;-)
>
> That should help.
>
I first tried fully automatic way and in the meantime I read sv
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| > root <[EMAIL PROTECTED]> writes:
| >
| > | > | It turns out that (see lines 152, 154of the build-interpsys function
| > | > | in util.lisp) there are lists of functions which will trigger
| > | > | autoloading of files for a specific purpose.
| > | >
Ralf fixes are revisions 136 and 137 on SF /trunk. I tried to
use
svn merge -r 135:137 https://svn.sourceforge.net/svnroot/axiom/trunk
(and also more fine grained variations) but that fails due to
truncated connections. However I can do (and did) the changes easily
on local copy:
cd src/hype
> root <[EMAIL PROTECTED]> writes:
>
> | > | It turns out that (see lines 152, 154of the build-interpsys function
> | > | in util.lisp) there are lists of functions which will trigger
> | > | autoloading of files for a specific purpose.
> | >
> | > translation comes after parsing, which already a
root <[EMAIL PROTECTED]> writes:
| > | It turns out that (see lines 152, 154of the build-interpsys function
| > | in util.lisp) there are lists of functions which will trigger
| > | autoloading of files for a specific purpose.
| >
| > translation comes after parsing, which already autoloaded def.
> | It turns out that (see lines 152, 154of the build-interpsys function
> | in util.lisp) there are lists of functions which will trigger
> | autoloading of files for a specific purpose.
>
> translation comes after parsing, which already autoloaded def.lisp.
>
> What am I missing?
You're missin
root <[EMAIL PROTECTED]> writes:
| > | > If we agree that last part of '$AXIOM' corresponds to architecture
specific
| > | > subdirectory, then also '$AXIOM/../share/viewports' would allow sharing.
| > |
| > | The $AXIOM variable points to "the final distribution" directory.
| > | It is possible
> | > If we agree that last part of '$AXIOM' corresponds to architecture
> specific
> | > subdirectory, then also '$AXIOM/../share/viewports' would allow sharing.
> |
> | The $AXIOM variable points to "the final distribution" directory.
> | It is possible to copy $AXIOM anywhere and get a complet
root <[EMAIL PROTECTED]> writes:
[...]
| It turns out that (see lines 152, 154of the build-interpsys function
| in util.lisp) there are lists of functions which will trigger
| autoloading of files for a specific purpose.
translation comes after parsing, which already autoloaded def.lisp.
What a
root <[EMAIL PROTECTED]> writes:
| > This patchlet updates GCL to the most recent version of GCL-2.6.8pre
| > (as of yesterday night, central time). It also has us stop applying
| > toploop.patch: the patch failed to apply cleanly because the portion of
| > code it touches had been slightly re
root <[EMAIL PROTECTED]> writes:
| > If we agree that last part of '$AXIOM' corresponds to architecture specific
| > subdirectory, then also '$AXIOM/../share/viewports' would allow sharing.
|
| The $AXIOM variable points to "the final distribution" directory.
| It is possible to copy $AXIOM anywh
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| Gabriel Dos Reis wrote:
| > Do you think you have a spare cycle to backport Ralf's fixes to
| > build-improvements?
| >
|
| Ralf fixes are revisions 136 and 137 on SF /trunk. I tried to
| use
|
| svn merge -r 135:137 https://svn.sourceforge.net/svn
root <[EMAIL PROTECTED]> writes:
| Gaby,
|
| The def.lisp file occurs in two places but for different reasons.
| If you look at the function build-interpsys in util.lisp.pamphlet
| you see that it takes several arguments.
|
| load-files
| parse-files -- contains the first instance of def.lisp
|
>
> | Tim --
> |
> | def.lisp is loaded twice into debugsys.
>
> This patch -- applied to build-improvements -- removes the duplicate
> load.
This patch is incorrect and should be removed.
It turns out that (see lines 152, 154of the build-interpsys function
in util.lisp) there are lists o
Gabriel Dos Reis wrote:
> Do you think you have a spare cycle to backport Ralf's fixes to
> build-improvements?
>
Ralf fixes are revisions 136 and 137 on SF /trunk. I tried to
use
svn merge -r 135:137 https://svn.sourceforge.net/svnroot/axiom/trunk
(and also more fine grained variations) but
> This patchlet updates GCL to the most recent version of GCL-2.6.8pre
> (as of yesterday night, central time). It also has us stop applying
> toploop.patch: the patch failed to apply cleanly because the portion of
> code it touches had been slightly reworked. Consequently, I remove
> the patc
> If we agree that last part of '$AXIOM' corresponds to architecture specific
> subdirectory, then also '$AXIOM/../share/viewports' would allow sharing.
The $AXIOM variable points to "the final distribution" directory.
It is possible to copy $AXIOM anywhere and get a complete system.
The $OBJ/$SY
Gaby,
The def.lisp file occurs in two places but for different reasons.
If you look at the function build-interpsys in util.lisp.pamphlet
you see that it takes several arguments.
load-files
parse-files -- contains the first instance of def.lisp
comp-files
browse-files
translate-files -- contains
> On Friday, October 27, 2006 6:05 PM Waldek Hebisch wrote:
> >
> > I have noticed that most viewports in build-imporvements is
> > corrupted. Namely, viewports directories contain compressed
> > bitmaps. Trying to decompress them produces messuge like:
> >
> > zcat:
> > build-improvements/src
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| I looked at hypertex pages and AFAICS I can use a simple sed script
| in a loop to fix paths in .pht files:
|
| sed 's,/doc/viewports/,/share/viewports/,g'
|
| After copying images from silver (to correct corruption which I described
| in anothe mail)
Hi,
This patchlet updates GCL to the most recent version of GCL-2.6.8pre
(as of yesterday night, central time). It also has us stop applying
toploop.patch: the patch failed to apply cleanly because the portion of
code it touches had been slightly reworked. Consequently, I remove
the patch alt
I looked at hypertex pages and AFAICS I can use a simple sed script
in a loop to fix paths in .pht files:
sed 's,/doc/viewports/,/share/viewports/,g'
After copying images from silver (to correct corruption which I described
in anothe mail) and applying this script I was able to see graphic
exampl
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
| Tim --
|
| def.lisp is loaded twice into debugsys.
This patch -- applied to build-improvements -- removes the duplicate
load.
Built and tested on an x86-suse-linux.
-- Gaby
2006-10-26 Gabriel Dos Reis <[EMAIL PROTECTED]>
* debugsys.l
What I know for sure is that I have five students who all have hard
time with Axiom silver and I had to give them
axiom.build-improvements. One group is working on formal power series,
and the other is working on algorithmic differentiation.
What exactly is the goal of the formal power series g
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Friday, October 27, 2006 6:11 PM Gaby wrote:
| > ...
| > I would like to see changes Tim makes to axiom--silver--1 sent to
| > this list or to the axiom-commits list. That helps keeping track
| > of the changes.
| >
|
| With the Tailor in place, I
On Friday, October 27, 2006 6:11 PM Gaby wrote:
> ...
> I would like to see changes Tim makes to axiom--silver--1 sent to
> this list or to the axiom-commits list. That helps keeping track
> of the changes.
>
With the Tailor in place, I think this will automatically happen.
Tailor creates the
On Friday, October 27, 2006 6:05 PM Waldek Hebisch wrote:
>
> I have noticed that most viewports in build-imporvements is
> corrupted. Namely, viewports directories contain compressed
> bitmaps. Trying to decompress them produces messuge like:
>
> zcat:
> build-improvements/src/hyper/viewports
Waldek Hebisch <[EMAIL PROTECTED]> writes:
| I have noticed that most viewports in build-imporvements is
| corrupted. Namely, viewports directories contain compressed
| bitmaps. Trying to decompress them produces messuge like:
|
| zcat:
build-improvements/src/hyper/viewports/AssortedGraphicsEx
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Friday, October 27, 2006 3:06 PM Waldek Hebisch wrote:
| > ...
| > Bill Page wrote:
| > > If you are able to identify and annonate the chunks of this
| > > changeset that represent deletions, additions and those that
| > > need further discussion, I t
On Friday, October 27, 2006 3:06 PM Waldek Hebisch wrote:
> ...
> Bill Page wrote:
> > If you are able to identify and annonate the chunks of this
> > changeset that represent deletions, additions and those that
> > need further discussion, I think that would be great. Except
> > for the issue of
I have noticed that most viewports in build-imporvements is
corrupted. Namely, viewports directories contain compressed
bitmaps. Trying to decompress them produces messuge like:
zcat:
build-improvements/src/hyper/viewports/AssortedGraphicsExamplePage1.VIEW/image.bm.Z:
corrupt input.
Correspon
"Alfredo Portes" <[EMAIL PROTECTED]> writes:
| On 27 Oct 2006 23:03:47 +0200, Gabriel Dos Reis
| <[EMAIL PROTECTED]> wrote:
| > "Alfredo Portes" <[EMAIL PROTECTED]> writes:
| >
| > | > | Now make complains there is no X11/Xlib.h file.
| > | >
| > | > Ah. Now, we need to know more about your syste
Martin Rubey <[EMAIL PROTECTED]> writes:
| Dear Gaby,
|
| Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
|
| > One group is working on formal power series,
|
| this group should definitively get into touch with Ralf, Antoine and me.
I'm CC:ing them.
Please, be "gentle" with them, they are CS
Martin,
On Friday, October 27, 2006 4:42 PM you wrote:
> ...
> BTW, I think that issuetracker really needs one improvement:
> we need to be able to run old versions of axiom there. Many
> many of the bug reports are strange to read, because the
> examples provided don't fail anymore.
>
Agreed.
> > For me personally, autoconf support is more important than
> > almost everything else, the reason being that I would really
> > like to see more Axiom developers. The more standard our build
> > environment is, the easier that will be. Seconly increasing
> > the number of type of supported plat
On 27 Oct 2006 23:03:47 +0200, Gabriel Dos Reis
<[EMAIL PROTECTED]> wrote:
"Alfredo Portes" <[EMAIL PROTECTED]> writes:
| > | Now make complains there is no X11/Xlib.h file.
| >
| > Ah. Now, we need to know more about your system. :-(
| >
| > Could you check whether X11/Xlib.h is there (say /us
"Alfredo Portes" <[EMAIL PROTECTED]> writes:
| > | Now make complains there is no X11/Xlib.h file.
| >
| > Ah. Now, we need to know more about your system. :-(
| >
| > Could you check whether X11/Xlib.h is there (say /usr/X11/include)? I
| > would be surprised if your system is setup with X11.
|
Martin Rubey <[EMAIL PROTECTED]> writes:
[...]
| And of course, it's high time for a free aldor compiler, and for dependent
| types in axiom. But I guess, all that won't happen in the near future.
free Aldor source may not happen very soon, but we may have better
support for dependent types in A
Dear Gaby,
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> One group is working on formal power series,
this group should definitively get into touch with Ralf, Antoine and me.
Ralf and myself have (toghether with extreme support from Christian and
Nicolas) an implementation of Combinatorial Spe
root <[EMAIL PROTECTED]> writes:
[...]
| are you trying to say that silver patches get backported into branches?
I'm suggesting that every patch against silver be made as dealing
conceptually with one thing, so that branch maintainers can decide
whether they want to have them for the purpose of
root <[EMAIL PROTECTED]> writes:
| > Diffing patches against Gold seems problematic to me. I
| > would prefer for patches to be against Silver if possible.
| > But this is mostly "cherry picking" anyway, so at least
| > with most SCM tools (maybe darcs is an exception) it is
| > necessary to use a
root <[EMAIL PROTECTED]> writes:
| > For me personally, autoconf support is more important than
| > almost everything else, the reason being that I would really
| > like to see more Axiom developers. The more standard our build
| > environment is, the easier that will be. Seconly increasing
| > th
| Now make complains there is no X11/Xlib.h file.
Ah. Now, we need to know more about your system. :-(
Could you check whether X11/Xlib.h is there (say /usr/X11/include)? I
would be surprised if your system is setup with X11.
I think in Debian this is in the package: libx11-dev
___
root <[EMAIL PROTECTED]> writes:
> > I don't think there are very many of these and I believe that
> > all of them have already been posted to the mailing list.
>
> I awoke this morning to a whole series of bug status reports
> changed to closed. Perhaps this is correct but I didn't see
> changes
> I don't think there are very many of these and I believe that
> all of them have already been posted to the mailing list.
I awoke this morning to a whole series of bug status reports
changed to closed. Perhaps this is correct but I didn't see
changes to the source code patched and tested. I'm go
> Diffing patches against Gold seems problematic to me. I
> would prefer for patches to be against Silver if possible.
> But this is mostly "cherry picking" anyway, so at least
> with most SCM tools (maybe darcs is an exception) it is
> necessary to use a fair amount of manual manipulation of
> pat
On 10/27/2006 10:10 PM, Gabriel Dos Reis wrote:
"Page, Bill" <[EMAIL PROTECTED]> writes:
| Tim,
|
| On Friday, October 27, 2006 1:56 PM you wrote:
| > Gaby wrote:
| > > What you want is not to merge branch-improvements back to
| > > trunk at this moment. Rather, you want to minimize dista
> For me personally, autoconf support is more important than
> almost everything else, the reason being that I would really
> like to see more Axiom developers. The more standard our build
> environment is, the easier that will be. Seconly increasing
> the number of type of supported platforms is v
> Here is how I see the situation:
>
> | || |
> | |darcs and |
> |next big = hg mirrors |
> |experiment | |
> gold | /|
> gold < |
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
> "Page, Bill" <[EMAIL PROTECTED]> writes:
> | Here is how I see the situation:
> |
> | | || |
> | | |darcs and |
> | |next big = hg mirrors |
> |
Francois Maltey <[EMAIL PROTECTED]> writes:
[...]
| > Please, restart asfresh (e.g. erase directory axiom-local and restart
| > from there, you don't need to touch the directory "axiom" where you
| > downloaded Axiom to).
|
| The previous step is right.
OK, great.
| Now make complains there is
"Page, Bill" <[EMAIL PROTECTED]> writes:
| Tim,
|
| On Friday, October 27, 2006 1:56 PM you wrote:
| > Gaby wrote:
| > > What you want is not to merge branch-improvements back to
| > > trunk at this moment. Rather, you want to minimize distance
| > > as much as possible. Concretely, that mean
Francois Maltey <[EMAIL PROTECTED]> writes:
| I dislike the root.staff owner.
Personnaly, I do not recommend building Axiom as superuser. There are
questionable commands in the build process that usually get rejected when
you're not root. And that is OK. If you're building as root, they
could
Francois Maltey <[EMAIL PROTECTED]> writes:
| No file found, but there is a link :
|
| ls -l /usr/local/axiom-local/mnt/linux/bin/document
|
| lrwxrwxrwx 1 root staff 42 2006-10-27 20:43
| /usr/local/axiom-local/mnt/linux/bin/document
|-> ../../../axiom/silver/src/scripts/document
root <[EMAIL PROTECTED]> writes:
| > The problem is not there. I think I've seen the error you're urnning
| > into before. It has to do with symbolic links working only portably
| > when given absolute path. I'm in the process of updating and making
| > sure my "theory" is right. But, basicall
Hi Gabriel,
It seems it's right.
> The problem is not there. I think I've seen the error you're urnning
> into before. It has to do with symbolic links working only portably
> when given absolute path. I'm in the process of updating and making
> sure my "theory" is right. But, basically, inst
Gabriel Dos Reis <[EMAIL PROTECTED]> writes:
| Francois Maltey <[EMAIL PROTECTED]> writes:
|
| | root <[EMAIL PROTECTED]> writes:
| |
| | > are you using a bash shell?
| |
| | Yes I do. Is-it an error ?
|
| No.
|
| The problem is not there. I think I've seen the error you're urnning
| into b
Tim,
On Friday, October 27, 2006 1:56 PM you wrote:
> Gaby wrote:
> > What you want is not to merge branch-improvements back to
> > trunk at this moment. Rather, you want to minimize distance
> > as much as possible. Concretely, that means backporting
> > some patches on silver to that branch
> The problem is not there. I think I've seen the error you're urnning
> into before. It has to do with symbolic links working only portably
> when given absolute path. I'm in the process of updating and making
> sure my "theory" is right. But, basically, instead of doing
>
> lndir ../axio
root <[EMAIL PROTECTED]> writes:
> the path seems correct. so it must be one of:
>
> the file is not executable
> the file is being read by the wrong shell
> the file contains junk
> bad karma
>
> so i'm trying to decide.
> can you execute the document command by hand?
>
> change to /usr/local/
Francois Maltey <[EMAIL PROTECTED]> writes:
| root <[EMAIL PROTECTED]> writes:
|
| > are you using a bash shell?
|
| Yes I do. Is-it an error ?
No.
The problem is not there. I think I've seen the error you're urnning
into before. It has to do with symbolic links working only portably
when gi
> > I have fetsche /silver from SourceForge. I do not understand why
> > you write about big differences. The biggest difference is that
> > /silver contains .arch-ids subdirectories. AFAICS essential differences
> > are tiny (869 lines). /silver has tla-1.1.tar.gz (IIRC removed
> > from /trunk)
nope. i'm just trying to guess.
the path seems correct. so it must be one of:
the file is not executable
the file is being read by the wrong shell
the file contains junk
bad karma
so i'm trying to decide.
can you execute the document command by hand?
change to /usr/local/axiom-local/src/interp a
root <[EMAIL PROTECTED]> writes:
> are you using a bash shell?
Yes I do. Is-it an error ?
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
are you using a bash shell?
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
Hi Gabriel,
> | cd /usr/loca/
of corse, it's cd /usr/local
> | svn co https://svn.sourceforge.net/svnroot/axiom/trunk axiom
> | svn co https://svn.sourceforge.net/svnroot/axiom/trunk axiom
> | # I make it twice because my adsl link is too slow
> | mkdir axiom-local
> | cd axiom-local
> | lndir
Francois Maltey <[EMAIL PROTECTED]> writes:
| Hi,
|
| I follow the commands of the
|
| http://wiki.axiom-developer.org/AxiomSilverBranch
|
| in orderto compile a new axiom.
|
| So I do as root :
|
| cd /usr/loca/
| svn co https://svn.sourceforge.net/svnroot/axiom/trunk axiom
| svn co https:
Bill Page wrote:
> On Friday, October 27, 2006 9:08 AM Waldek Hebisch wrote:
> > Also, /trunk has added ChangeLog to some subdirectories.
> >
>
> Maybe we need to discuss this ChangeLog policy. At one
> point Gaby started adding per directory ChangeLogs, but
> Tim has only every used one central
Hi,
I follow the commands of the
http://wiki.axiom-developer.org/AxiomSilverBranch
in orderto compile a new axiom.
So I do as root :
cd /usr/loca/
svn co https://svn.sourceforge.net/svnroot/axiom/trunk axiom
svn co https://svn.sourceforge.net/svnroot/axiom/trunk axiom
# I make it twice becau
root <[EMAIL PROTECTED]> writes:
| > It appears that we now have at least two "trunks" under SVN --
| > ignoring for the moment, all the variations under other SCMs. That is
| > going to be more confusing to people already confused with the current
| > state of the affairs. We need to agree on T
root <[EMAIL PROTECTED]> writes:
| > What you want is not to merge branch-improvements back to trunk at
| > this moment. Rather, you want to minimize distance as much as
| > possible. Concretely, that means backporting some patches on silver
| > to that branch -- not the other way around.
|
| m
root <[EMAIL PROTECTED]> writes:
| > When build-improvements is ready to be merged into trunk, I'll propose
| > it. Build-improvements is ready when the TODO list has been moved to
| > "done" section and tested adequately. If you believe you want merge
| > piecemeal, go for it. Just beware that
> It appears that we now have at least two "trunks" under SVN --
> ignoring for the moment, all the variations under other SCMs. That is
> going to be more confusing to people already confused with the current
> state of the affairs. We need to agree on THE trunk.
well i'm in the process of merg
Camm Maguire <[EMAIL PROTECTED]> writes:
| Greetings! Please be aware that in most cases this message is,
| unfortunately, misleading about memory corruption. Segfaults are
| grouped here with a number of other errors which the error handler
| cannot properly process, usually because of some bug
> What you want is not to merge branch-improvements back to trunk at
> this moment. Rather, you want to minimize distance as much as
> possible. Concretely, that means backporting some patches on silver
> to that branch -- not the other way around.
merging build-improvements can happen "when it
On Friday, October 27, 2006 1:28 PM Waldek Hebisch wrote:
> ...
>
> $AXIOM/bin/clef -e $AXIOM/bin/AXIOMsys
>
Cool. Thanks.
Regards,
Bill Page.
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axio
On Friday, October 27, 2006 1:01 PM Gabriel Dos Reis wrote:
>
> Waldek Hebisch writes:
> ...
> |
> |>> System error:
> |Caught fatal error [memory may be damaged]
>
> I've been running into this "memory may be damaged" stuff very
> often these days ]with students, everything is possible
Greetings! Please be aware that in most cases this message is,
unfortunately, misleading about memory corruption. Segfaults are
grouped here with a number of other errors which the error handler
cannot properly process, usually because of some bug in the error
handler. Of course you can see if y
Bill Page wrote:
> Waldek Hebisch <[EMAIL PROTECTED]> writes:
> > When AXIOMsys is run via clef ^D\n exits it.
>
> I am not sure how to create this situation. What options
> to the 'axiom' script did you use?
>
$AXIOM/bin/clef -e $AXIOM/bin/AXIOMsys
--
Waldek Hebi
root <[EMAIL PROTECTED]> writes:
| > Let me know what you think of this arrangement.
|
| You do realize that this leaves the build-improvement branch as
| a true fork since it is no longer "rooted" at axiom49 in the SVN tree.
|
| I think we need a person to volunteer to be the "patch-pusher"
| b
Waldek Hebisch <[EMAIL PROTECTED]> writes:
[...]
| All this is based on system trace. AFAICS when AXIOMsys runs
| standalone there is no select loop. I tried to give "(1) ->\n"
| and then ^C to standalone AXIOMsys -- the trace looks quite similar
| but AXIOMsys produces reasonable error message
"Page, Bill" <[EMAIL PROTECTED]> writes:
| On Friday, October 27, 2006 11:53 AM Gaby wrote:
| >
| > Tim Daly wrote writes:
| >
| > [...]
| >
| > | There are a large number of "fixes" being applied which appear
| > | to have nothing to do with autotools, such as the sttaylor fix
| > | and the sag
> When build-improvements is ready to be merged into trunk, I'll propose
> it. Build-improvements is ready when the TODO list has been moved to
> "done" section and tested adequately. If you believe you want merge
> piecemeal, go for it. Just beware that that is going to cause troubles
> and I d
root wrote:
> Apparently the ptys are opened in raw mode and do not interpret the
> control characters but pass them down the pipe to AXIOMsys. However
> the (read) from axiom simply gets the cntrl-D and tries to parse it.
>
> I'm not really sure how this should be handled. Clearly you don't
> wan
On Friday, October 27, 2006 12:07 PM Ralf Hemmecke wrote:
>
> On 10/27/2006 05:28 PM, Bill Page wrote:
> > On Friday, October 27, 2006 11:06 AM Tim Daly wrote:
> >> Bill Page wrote: [new /silver root at SourceForge]
> > ...
> > Yes, I thought about that. That is another reason why I decided
> > no
On Friday, October 27, 2006 11:53 AM Gaby wrote:
>
> Tim Daly wrote writes:
>
> [...]
>
> | There are a large number of "fixes" being applied which appear
> | to have nothing to do with autotools, such as the sttaylor fix
> | and the sage change. Worse yet, it appears that the sage
> | connection
"Page, Bill" <[EMAIL PROTECTED]> writes:
[...]
| I agree that build-improvements is rapidly gaining distance
| on /trunk and Axiom Gold. In my opinion (but I don't know how
| Gaby feels about this), build-improvements is now nearly stable
| enough to be merged back.
There are a couple of issues
root <[EMAIL PROTECTED]> writes:
| > Let me know what you think of this arrangement.
|
| You do realize that this leaves the build-improvement branch as
| a true fork since it is no longer "rooted" at axiom49 in the SVN tree.
|
| I think we need a person to volunteer to be the "patch-pusher"
| b
On 10/27/2006 05:28 PM, Page, Bill wrote:
On Friday, October 27, 2006 11:06 AM Tim Daly wrote:
Bill Page wrote: [new /silver root at SourceForge]
Let me know what you think of this arrangement.
You do realize that this leaves the build-improvement branch
as a true fork since it is no longer "r
Ralf Hemmecke <[EMAIL PROTECTED]> writes:
| > | > There is yet another issue: It seems that latex -source-specials puts
| > | > the absolute path of the original file into the dvi. I guess that at
| > | > least kdvi won't mind for forward search (i.e., when clicking on
| > | > INT.spad in HyperDoc
root <[EMAIL PROTECTED]> writes:
[...]
| There are a large number of "fixes" being applied which appear to
| have nothing to do with autotools, such as the sttaylor fix and the
| sage change. Worse yet, it appears that the sage connection won't work
| with gold so sage users cannot get the lates
> >
> > Your automatic procedure should show the top entry in CHANGELOG
> > of:
>
> Looks ok to me:
>
> http://axiom.svn.sourceforge.net/viewvc/axiom/silver/CHANGELOG?revision=
> 218&view=markup
>
> ...
>
> Original author: Tim Daly <[EMAIL PROTECTED]>
> Date: 2006-10-26 15:16:20-04:00
>
>
Tim,
On Friday, October 27, 2006 11:06 AM you wrote:
>
> Your automatic procedure should show the top entry in CHANGELOG
> of:
>
> 20061026 tpd src/interp/setq.lisp add Christian Aistleitner
>
> If this is NOT the top entry then something is broken.
>
Looks ok to me:
http://axiom.svn.source
> Greetings, and thanks!
>
> Can anyone see what this might suggest in the sman code?
>
> Take care,
>
> Waldek Hebisch <[EMAIL PROTECTED]> writes:
>
> > root wrote:
> > > Camm,
> > >
> > > Architecturally there is a process called sman which starts up
> > > other processes including axiomsys,
| > There is yet another issue: It seems that latex -source-specials puts
| > the absolute path of the original file into the dvi. I guess that at
| > least kdvi won't mind for forward search (i.e., when clicking on
| > INT.spad in HyperDoc the correct line will appear),
|
| I don't quite underst
patch applied as axiom--silver--1--patch-4
> On Debian systems, it is common to run the stable distribution, and
> then reserve a specific area of disk for the unstable distribution,
> which one can use as if it were the entire installed OS via 'dchroot
> unstable'. To make this work, certain di
On Friday, October 27, 2006 11:06 AM Tim Daly wrote:
> Bill Page wrote: [new /silver root at SourceForge]
> > Let me know what you think of this arrangement.
>
> You do realize that this leaves the build-improvement branch
> as a true fork since it is no longer "rooted" at axiom49 in
> the SVN tre
> On Debian systems, it is common to run the stable distribution, and
> then reserve a specific area of disk for the unstable distribution,
> which one can use as if it were the entire installed OS via 'dchroot
> unstable'. To make this work, certain directories have to be
> accessible to both sys
1 - 100 of 131 matches
Mail list logo
