You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
(1) |
Mar
(13) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
(2) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Rocky B. <ro...@gn...> - 2020-03-15 12:12:21
|
A new release based on 4.3 has been added. https://github.com/rocky/remake/releases/tag/release_4.3%2Bdbg-1.5 has the release notes. Personally I really like the --search-parent or -c option added |
From: Rocky B. <ro...@gn...> - 2017-08-22 11:03:15
|
And on github. On github the default branch is this version and will be the latest version. "master" may be one of these branches. Each release we support, e.g. 3.82, 4.1, 4.2.1, has a branch. Specific points along those branches are tagged with a release. |
From: Rocky B. <ro...@gn...> - 2015-09-08 11:53:48
|
HI - Narrow down the Makefile into a small example that shows the problem, then open up an issue in the github project. Thanks. On Sat, Sep 5, 2015 at 6:11 AM, Russell Shaw <rj...@ne...> wrote: > Hi, > I'm using remake-4.1+dbg1.1 on a 17575 line Makefile for building gcc. > > In build-gcc i type: /usr/local/bin/remake -X > > then: > > remake<0> b maybe-all-gotools > Breakpoint 1 on target maybe-all-gotools: file Makefile, line 10701. > > then: > > remake<1> c > > but remake stops after one target instead of continuing to the breakpoint. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bashdb-remake mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-remake > |
From: Russell S. <rj...@ne...> - 2015-09-05 10:11:36
|
Hi, I'm using remake-4.1+dbg1.1 on a 17575 line Makefile for building gcc. In build-gcc i type: /usr/local/bin/remake -X then: remake<0> b maybe-all-gotools Breakpoint 1 on target maybe-all-gotools: file Makefile, line 10701. then: remake<1> c but remake stops after one target instead of continuing to the breakpoint. |
From: Rocky B. <ro...@gn...> - 2015-06-05 23:12:06
|
Slight correction. The document that describes the callgrind output format is http://valgrind.org/docs/manual/cl-format.html On Fri, Jun 5, 2015 at 6:56 PM, Rocky Bernstein <ro...@gn...> wrote: > This latest release adds an option --profile which will profile the make > run and produce data files in callgrind format. > > kcachgrind is a nice tool for reading the callgrind output format. However > there is also dot2graph as well as valgrind_annotate. > > A description of the profile data format can be found in > http://valgrind.org/docs/manual/cl-manual.html > |
From: Rocky B. <ro...@gn...> - 2015-06-05 22:56:22
|
This latest release adds an option --profile which will profile the make run and produce data files in callgrind format. kcachgrind is a nice tool for reading the callgrind output format. However there is also dot2graph as well as valgrind_annotate. A description of the profile data format can be found in http://valgrind.org/docs/manual/cl-manual.html |
From: Rocky B. <ro...@gn...> - 2015-01-01 02:22:19
|
Just in time for 2015, I've put out a version of remake that is based on GNU Make 4.1. Enjoy! |
From: Rocky B. <ro...@gn...> - 2013-04-30 14:21:10
|
No, I am not aware of something for Eclipse. Perhaps someone else on the list is. On Tue, Apr 30, 2013 at 9:42 AM, john moule <evi...@ya... > wrote: > Hi, > > From http://bashdb.sourceforge.net/remake/ I see there is a DDD front end > for remake. Are you aware of one for the Eclipse IDE? > > cheers john > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > Bashdb-remake mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-remake > > |
From: john m. <evi...@ya...> - 2013-04-30 13:48:59
|
Hi, From http://bashdb.sourceforge.net/remake/ I see there is a DDD front end for remake. Are you aware of one for the Eclipse IDE? cheers john |
From: Rocky B. <ro...@gn...> - 2013-02-28 20:59:01
|
On Thu, Feb 28, 2013 at 10:35 AM, Myles Dear (mdear) <md...@ci...>wrote: > Not sure if my request made it to the mailing list, because I sent this > before confirming my subscription.**** > > > Resending just to be sure …**** > > ** ** > > *From:* Myles Dear (mdear) > *Sent:* Tuesday, February 26, 2013 6:26 PM > *To:* 'bas...@li...' > *Subject:* Can latest debug code be back-ported to gmake 3.80 ?**** > > ** ** > > Hello, remake experts.**** > > ** ** > > I have been trying to solve some thorny gmake issues in a large complex > software project.**** > > ** ** > > I would very much like to use your debug extensions to gmake, but find > myself unable to do so because my project’s baseline gmake is using 3.80 > (and I’m using the latest 3.82+dbg0.9). Additional failure points are > being hit with the newer gmake (which is not unexpected), but I don’t want > to solve these problems until the project decides to go with a newer gmake > version (which may be years down the line, or not at all).**** > > ** ** > > Is it feasible to port the latest debug code back to gmake 3.80 ? > I think so if you want to undertake. I'm not going to, but I'll assist if you or others that want to. > **** > > ** ** > > Thanks,**** > > <Myles>**** > > ** ** > > ** ** > > [image: cisco-logo-for-email-signature]**** > > ** ** > > *Myles Dear* > > Embedded White-Box Test Designer**** > > Automation Core Team**** > > Network Operating System Technology Group (NOSTG)**** > > **** > > Tel: *+1 (613) 254-4594***** > > Mobile: *+1 (613) 858-2120***** > > Fax: *+1 (613) 254-3701***** > > Email: md...@ci...**** > > Cisco Systems Canada l www.cisco.com** > > 2000 Innovation Dr, Kanata, ON, K2K 3E8**** > > ** ** > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > Bashdb-remake mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-remake > > |
From: PLC S. <sa...@pl...> - 2012-05-16 20:05:31
|
Dear sir, Good news, in all the industrial automation products we produced, best-selling in year 2011 are: (one)Profibus cable and profibus connector(0BA52,0BB52,0BA12,0BB12,0BA42,0BB42) (two)S7-300/S7-400 front connector(392-1AJ00,392-1AM00) (three)PLC adapter(USB,Ethernet) for Siemens S7-200/300/400,Mitsubishi,Allen-Bradley,GE,OMRON,Schneider and etc. (four)CP5611,CP5611-A2,CP5512,CP5512 Express Card (five)S7-200/300 Input,Output Modules Good quality and cheap(as low as small part of original) Thanks for your support! Best Regards News of_Kollewin |
From: Rocky B. <ro...@gn...> - 2012-01-13 03:03:37
|
On Thu, Jan 12, 2012 at 8:35 AM, Basile Starynkevitch < ba...@st...> wrote: > On Wed, Jan 11, 2012 at 09:52:01PM -0500, Rocky Bernstein wrote: > > On Wed, Jan 11, 2012 at 9:37 AM, Basile Starynkevitch < > > ba...@st...> wrote: > > > > > Hello All, > > > > > > I am not able to compiling the latest GIT remake > > > > Read README.md which also appears in https://github.com/rocky/remake > > Thanks for the tip. I followed the instructions there > I have updated them now to deal with the problems you've noticed. Reread that or look at the commit log for what's changed. The sucky thing about the way things stand is partly because we are keeping closer to the GNU make code. And currently "make update" is broken because of translators sites or something. The doc weirdness is sort of my fault, although the wacky way that autoconf works doesn't help matters. > > $ autoreconf -i > $ ./configure > $ make -k update > $ make && make check && sudo make install > > And I am getting > > pcbasile.x86_64 src/Tools/remake 14:34 % make -w > make: Entering directory `/usr/src/Tools/remake' > make all-recursive > make[1]: Entering directory `/usr/src/Tools/remake' > Making all in glob > make[2]: Entering directory `/usr/src/Tools/remake/glob' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/usr/src/Tools/remake/glob' > Making all in config > make[2]: Entering directory `/usr/src/Tools/remake/config' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/usr/src/Tools/remake/config' > Making all in po > make[2]: Entering directory `/usr/src/Tools/remake/po' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/usr/src/Tools/remake/po' > Making all in doc > make[2]: Entering directory `/usr/src/Tools/remake/doc' > restore=: && backupdir=".am$$" && \ > rm -rf $backupdir && mkdir $backupdir && \ > if (/bin/bash /usr/src/Tools/remake/config/missing --run makeinfo > --version) >/dev/null 2>&1; then \ > for f in remake.info remake.info-[0-9] remake.info-[0-9][0-9] > remake.i[0-9] remake.i[0-9][0-9]; do \ > if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ > done; \ > else :; fi && \ > if /bin/bash /usr/src/Tools/remake/config/missing --run makeinfo > -I . \ > -o remake.info `test -f 'remake.texi' || echo './'`remake.texi; \ > then \ > rc=0; \ > else \ > rc=$?; \ > $restore $backupdir/* `echo "./remake.info" | sed 's|[^/]*$||'`; > \ > fi; \ > rm -rf $backupdir; exit $rc > remake.texi:35: @include `version-remake.texi': No such file or directory. > remake.texi:78: warning: undefined flag: EDITION. > remake.texi:78: warning: undefined flag: UPDATED-MONTH. > remake.texi:129: warning: undefined flag: EDITION. > remake.texi:129: warning: undefined flag: UPDATED-MONTH. > makeinfo: Removing output file `remake.info' due to errors; use --force > to preserve. > make[2]: *** [remake.info] Error 1 > make[2]: Leaving directory `/usr/src/Tools/remake/doc' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/src/Tools/remake' > make: *** [all] Error 2 > make: Leaving directory `/usr/src/Tools/remake' > > > Cheers. > -- > Basile STARYNKEVITCH http://starynkevitch.net/Basile/ > email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 > 8, rue de la Faiencerie, 92340 Bourg La Reine, France > *** opinions {are only mines, sont seulement les miennes} *** > |
From: Basile S. <ba...@st...> - 2012-01-12 13:55:16
|
On Wed, Jan 11, 2012 at 09:52:01PM -0500, Rocky Bernstein wrote: > On Wed, Jan 11, 2012 at 9:37 AM, Basile Starynkevitch < > ba...@st...> wrote: > > > Hello All, > > > > I am not able to compiling the latest GIT remake > > Read README.md which also appears in https://github.com/rocky/remake Thanks for the tip. I followed the instructions there $ autoreconf -i $ ./configure $ make -k update $ make && make check && sudo make install And I am getting pcbasile.x86_64 src/Tools/remake 14:34 % make -w make: Entering directory `/usr/src/Tools/remake' make all-recursive make[1]: Entering directory `/usr/src/Tools/remake' Making all in glob make[2]: Entering directory `/usr/src/Tools/remake/glob' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/Tools/remake/glob' Making all in config make[2]: Entering directory `/usr/src/Tools/remake/config' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/Tools/remake/config' Making all in po make[2]: Entering directory `/usr/src/Tools/remake/po' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/Tools/remake/po' Making all in doc make[2]: Entering directory `/usr/src/Tools/remake/doc' restore=: && backupdir=".am$$" && \ rm -rf $backupdir && mkdir $backupdir && \ if (/bin/bash /usr/src/Tools/remake/config/missing --run makeinfo --version) >/dev/null 2>&1; then \ for f in remake.info remake.info-[0-9] remake.info-[0-9][0-9] remake.i[0-9] remake.i[0-9][0-9]; do \ if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ done; \ else :; fi && \ if /bin/bash /usr/src/Tools/remake/config/missing --run makeinfo -I . \ -o remake.info `test -f 'remake.texi' || echo './'`remake.texi; \ then \ rc=0; \ else \ rc=$?; \ $restore $backupdir/* `echo "./remake.info" | sed 's|[^/]*$||'`; \ fi; \ rm -rf $backupdir; exit $rc remake.texi:35: @include `version-remake.texi': No such file or directory. remake.texi:78: warning: undefined flag: EDITION. remake.texi:78: warning: undefined flag: UPDATED-MONTH. remake.texi:129: warning: undefined flag: EDITION. remake.texi:129: warning: undefined flag: UPDATED-MONTH. makeinfo: Removing output file `remake.info' due to errors; use --force to preserve. make[2]: *** [remake.info] Error 1 make[2]: Leaving directory `/usr/src/Tools/remake/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/Tools/remake' make: *** [all] Error 2 make: Leaving directory `/usr/src/Tools/remake' Cheers. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les miennes} *** |
From: Rocky B. <ro...@gn...> - 2012-01-12 02:52:08
|
On Wed, Jan 11, 2012 at 9:37 AM, Basile Starynkevitch < ba...@st...> wrote: > Hello All, > > I am not able to compiling the latest GIT remake > pcbasile.x86_64 src/Tools/remake 15:35 % make > make all-recursive > make[1]: Entering directory `/usr/src/Tools/remake' > Making all in glob > make[2]: Entering directory `/usr/src/Tools/remake/glob' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/usr/src/Tools/remake/glob' > Making all in config > make[2]: Entering directory `/usr/src/Tools/remake/config' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/usr/src/Tools/remake/config' > Making all in po > make[2]: Entering directory `/usr/src/Tools/remake/po' > test -z "be.gmo da.gmo de.gmo es.gmo fi.gmo fr.gmo ga.gmo gl.gmo he.gmo > hr.gmo id.gmo it.gmo ja.gmo ko.gmo lt.gmo nl.gmo pl.gmo pt_BR.gmo ru.gmo > sv.gmo tr.gmo uk.gmo vi.gmo zh_CN.gmo" || make be.gmo da.gmo de.gmo es.gmo > fi.gmo fr.gmo ga.gmo gl.gmo he.gmo hr.gmo id.gmo it.gmo ja.gmo ko.gmo > lt.gmo nl.gmo pl.gmo pt_BR.gmo ru.gmo sv.gmo tr.gmo uk.gmo vi.gmo zh_CN.gmo > make[3]: Entering directory `/usr/src/Tools/remake/po' > make[4]: Entering directory `/usr/src/Tools/remake/po' > File be.po does not exist. If you are a translator, you can create it > through 'msginit'. > make[4]: *** [be.po-create] Error 1 > make[4]: Leaving directory `/usr/src/Tools/remake/po' > make[3]: *** [be.po] Error 2 > make[3]: Leaving directory `/usr/src/Tools/remake/po' > make[2]: *** [stamp-po] Error 2 > make[2]: Leaving directory `/usr/src/Tools/remake/po' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/usr/src/Tools/remake' > make: *** [all] Error 2 > > > What I am doing wrong? > Read README.md which also appears in https://github.com/rocky/remake > > (Or how to compile the latest remake from GIT?) > > The ./configure script had no arguments, if that matter. > > The system is a Debian/GNU/Linux/Sid/AMD64 > > The compiler is gcc-4.6 from Debian > > > Regards. > -- > Basile STARYNKEVITCH http://starynkevitch.net/Basile/ > email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 > 8, rue de la Faiencerie, 92340 Bourg La Reine, France > *** opinions {are only mines, sont seulement les miennes} *** > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > Bashdb-remake mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-remake > |
From: Basile S. <ba...@st...> - 2012-01-11 14:37:54
|
Hello All, I am not able to compiling the latest GIT remake pcbasile.x86_64 src/Tools/remake 15:35 % make make all-recursive make[1]: Entering directory `/usr/src/Tools/remake' Making all in glob make[2]: Entering directory `/usr/src/Tools/remake/glob' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/Tools/remake/glob' Making all in config make[2]: Entering directory `/usr/src/Tools/remake/config' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/Tools/remake/config' Making all in po make[2]: Entering directory `/usr/src/Tools/remake/po' test -z "be.gmo da.gmo de.gmo es.gmo fi.gmo fr.gmo ga.gmo gl.gmo he.gmo hr.gmo id.gmo it.gmo ja.gmo ko.gmo lt.gmo nl.gmo pl.gmo pt_BR.gmo ru.gmo sv.gmo tr.gmo uk.gmo vi.gmo zh_CN.gmo" || make be.gmo da.gmo de.gmo es.gmo fi.gmo fr.gmo ga.gmo gl.gmo he.gmo hr.gmo id.gmo it.gmo ja.gmo ko.gmo lt.gmo nl.gmo pl.gmo pt_BR.gmo ru.gmo sv.gmo tr.gmo uk.gmo vi.gmo zh_CN.gmo make[3]: Entering directory `/usr/src/Tools/remake/po' make[4]: Entering directory `/usr/src/Tools/remake/po' File be.po does not exist. If you are a translator, you can create it through 'msginit'. make[4]: *** [be.po-create] Error 1 make[4]: Leaving directory `/usr/src/Tools/remake/po' make[3]: *** [be.po] Error 2 make[3]: Leaving directory `/usr/src/Tools/remake/po' make[2]: *** [stamp-po] Error 2 make[2]: Leaving directory `/usr/src/Tools/remake/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/Tools/remake' make: *** [all] Error 2 What I am doing wrong? (Or how to compile the latest remake from GIT?) The ./configure script had no arguments, if that matter. The system is a Debian/GNU/Linux/Sid/AMD64 The compiler is gcc-4.6 from Debian Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les miennes} *** |
From: Rocky B. <ro...@gn...> - 2011-04-17 14:22:42
|
Have you ever wanted "rake tasks" for GNU Make? That is you have some strange Makefile and you want to see the interesting targets, that you can run "make *target-name*" on? Well I have. So I added it. remake --targets shows a list of explicit target names. Implicit patterns such as those that have % in them are not in this list. As a nod to *rake*, *remake --tasks* does the same thing. Still in the list are file names which are likely to be boring and those extension-matching patterns. So if you want to exclude these from the list, try: remake --tasks | grep -v '/' | grep -v '\.' The longer story is this. Inside the debugger, it is useful to see a list of locations you can stop at or set a breakpoint. This is called "info targets". Run "help info targets" for information on how to run that. After putting this in, I realized it might be interesting just to list the target names. So that was next added. And then I found myself running: echo "info targets name" | remake --debugger This shows also the debugger prompts and has is a little cumbersome, so I added it as an option. Down the line, I will probably split off --targets from --tasks. The later will exclude targets without commands to remake the targets. For example with file names that are supposed to exist and are not derived from some other file would be excluded. Also I should exclude targets that match extensions like *.c.o* |
From: Rainer M. <ra...@ma...> - 2011-03-31 19:15:41
|
Hello, I am the maintainer of remake in MacPorts [1], a package mangement system for Mac OS X. With the latest remake-3.82+dbg-0.4 I noticed there is a reremake in addition to normal remake created during 'make install'. Both files are identical. .../bin/remake .../bin/reremake I assume this is a mistake and is not done intentionally? Rainer [1] http://macports.org |
From: Rocky B. <ro...@gn...> - 2011-03-26 03:34:30
|
I've just released a new version of the GNU Make debugger (with better tracing and error reporting) which is based on the the GNU Make 3.82 sources. The file NEWS.readme in the distribution has more detail, but suffice it to say this is an important rewrite and release. Things are lot cleaner now and the code runs the GNU 3.82 regression tests. |
From: Aleksey Y. <ale...@gm...> - 2010-11-30 19:20:17
|
Hello, I'm trying to understand the relationship of "remake" building process with the "readline" library. My machine has the "readline" library already installed, and also I've installed a most recent version of this library. If I build the remake without the --with-readline option, then it works OK in the debugging mode (option -X). If I build the remake with the --with-readline option, the configure warns me, that the readline library isn't found, and the built remake can't debug. This warning is below: configure: WARNING: libreadline is needed for the debugger. I'll build "make" configure: WARNING: with trace support, but you won't be able enter the configure: WARNING: debugger. The library exists in its normal location: afy:> ls -l /usr/lib/libreadline* -rw-r--r-- 1 root root 300808 May 6 2009 /usr/lib/libreadline.a lrwxrwxrwx 1 root root 16 Dec 9 2009 /usr/lib/libreadline.so -> libreadline.so.5* lrwxrwxrwx 1 root root 18 Dec 9 2009 /usr/lib/libreadline.so.4 -> libreadline.so.4.3* -rwxr-xr-x 1 root root 192228 Jul 15 2006 /usr/lib/libreadline.so.4.3* lrwxrwxrwx 1 root root 18 Dec 9 2009 /usr/lib/libreadline.so.5 -> libreadline.so.5.1* -rwxr-xr-x 1 root root 208808 May 6 2009 /usr/lib/libreadline.so.5.1* So - it looks like the --with-readline option works in opposite way. Also I can't find a way to link the remake with the latest readline library I've installed myself... My questions: (1) What options/envars should I use to configure the remake to point to the readline library I want? (2) What's the role of the --with-readline option? Thanks AY |
From: Rocky B. <ro...@gn...> - 2010-04-25 14:22:34
|
If you want ddd to run remake as its inferior debugger and you have ddd-3.3.12 or greater installed, use the option --make. Run "ddd --help" for a list of all options. On Thu, Apr 22, 2010 at 7:09 PM, Aleksey Yakovlev < ale...@gm...> wrote: > Hello, > > I'm new to remake... > Just wandering - how to integrate it with DDD? > > Thanks, > Aleksey > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bashdb-remake mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-remake > > |
From: Aleksey Y. <ale...@gm...> - 2010-04-22 23:10:03
|
Hello, I'm new to remake... Just wandering - how to integrate it with DDD? Thanks, Aleksey |
From: R. B. <ro...@pa...> - 2008-10-25 14:28:14
|
I've ported the remake code for GNU make 3.80+ to GNU make 3.81. and am planning an alpha release around Oct 27. The repository is on github at: http://github.com/rocky/remake/tree/master |
From: R. B. <ro...@pa...> - 2007-11-17 15:27:38
|
What things do people find most helpful in debugging from emacs? What things in general are lacking? (Of course, I'm mostly interested in the languages cited above and improving debugging interaction with those, but other information could be helpful as well.) One thing I notice regarding edebug which seems different than gud debugging is that it sets up (I guess) a recursive edit on the program begin debugged so that it can bind keys to debug functions like step, next, and so on. Do people generally find it useful when debugging to set the program read only so that it can't be modified while debugging? Or is this an annoyance? For Emacs Lisp code, I find C-x C-e helpful and use that a lot. For these other programming languages that could be bound to eval using the debugger. (And if not debugging, it might fall back to running the expression in a comint shell buffer). |
From: R. B. <ro...@pa...> - 2007-05-18 02:52:23
|
These options from the GNU Make manual may be of help. `-p' `--print-data-base' Print the data base (rules and variable values) that results from reading the makefiles; then execute as usual or as otherwise specified. This also prints the version information given by the `-v' switch (see below). To print the data base without trying to remake any files, use `make -qp'. To print the data base of predefined rules and variables, use `make -p -f /dev/null'. The data base output contains filename and linenumber information for command and variable definitions, so it can be a useful debugging tool in complex environments. `-q' `--question' "Question mode". Do not run any commands, or print anything; just return an exit status that is zero if the specified targets are already up to date, one if any remaking is required, or two if an error is encountered. *Note Instead of Executing the Commands: Instead of Execution. However if this doesn't doesn't do it, then the most sure way to get what you want done is to dig in and do it ;-) Patches to remake are most welcome. And I bet the same is true with GNU make. guy...@vi... writes: > Hi, > > I recently read and tried to implement makefiles based on a webcast I Googled named: "Muli-Target, Multi-Platform Make: Building Everything from one Makefile" @ http://www.cmcrossroads.com/content/view/6921/153/ > > I liked the ideas presented, since I'm developing on multi-platforms, and I'm trying to tame an old large C application with very messy MAKEDEPENDS, recursive MAKES, and other hoops and jumps, such as > pre-pre-processor steps depending on targets, platforms, DB, etc. > > The premise of having makefiles included in the main makefile (instead of recursive) works nicely, but when I'm trying to troubleshoot the makefiles, that's when it starts going sour. It's sometimes hard to > figure which variables are what, especially when using variables inside variables "ie: ($(module)_prog1)" and in what sequence they present themselves, etc. I have special targets to print out variables, and also to print out all variables, but... > > It would be nice if: > MAKE has a -E option (like the gcc -E) to dump the fully expanded source (or makefile in this case) to STDOUT (or a file), after pass 1 (after all the includes are done and the variables are computed, but before any target decisions are made (in pass 2). > > I was looking to see if REMAKE had such an option, and even though it definitely has some new > interesting debugging capabilities, I still couldn't find an equivalent to -E. > > Any suggestions and/or any ideas how much effort would be required to add this to REMAKE?? > > Regards,Guy > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Bashdb-remake mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-remake > |
From: <guy...@vi...> - 2007-05-17 13:44:32
|
Hi, I recently read and tried to implement makefiles based on a webcast I Googled named: "Muli-Target, Multi-Platform Make: Building Everything from one Makefile" @ http://www.cmcrossroads.com/content/view/6921/153/ I liked the ideas presented, since I'm developing on multi-platforms, and I'm trying to tame an old large C application with very messy MAKEDEPENDS, recursive MAKES, and other hoops and jumps, such as pre-pre-processor steps depending on targets, platforms, DB, etc. The premise of having makefiles included in the main makefile (instead of recursive) works nicely, but when I'm trying to troubleshoot the makefiles, that's when it starts going sour. It's sometimes hard to figure which variables are what, especially when using variables inside variables "ie: ($(module)_prog1)" and in what sequence they present themselves, etc. I have special targets to print out variables, and also to print out all variables, but... It would be nice if: MAKE has a -E option (like the gcc -E) to dump the fully expanded source (or makefile in this case) to STDOUT (or a file), after pass 1 (after all the includes are done and the variables are computed, but before any target decisions are made (in pass 2). I was looking to see if REMAKE had such an option, and even though it definitely has some new interesting debugging capabilities, I still couldn't find an equivalent to -E. Any suggestions and/or any ideas how much effort would be required to add this to REMAKE?? Regards,Guy |