cachecc1-list Mailing List for cachecc1
Brought to you by:
bpc
Menu
▾
▴
cachecc1-list — Mailing list for cachecc1 users
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: WAYN - P. r. <inv...@wh...> - 2011-04-27 09:45:19
|
Hi, You have yet to confirm whether you would like to connect with Ross Cameron. Please choose from the following options: Accept Ross's connection request: http://www.wayn.com/invite/19767-moegbe/fqdvo8-9qeb4tqrnger7 Reject Ross's connection request: http://www.wayn.com/-/19768-moegbe?m=1282278&c=531037960 Best regards, The WAYN Team -------------- To stop receiving add friend requests from Ross Cameron, click here: http://www.wayn.com/-/19769-moegbe?m=1282278&c=531037960 To stop receiving any notifications from WAYN, click here: http://www.wayn.com/-/19770-moegbe?c=531037960 |
|
From: WAYN - R. C. r. <inv...@wh...> - 2011-04-05 00:29:34
|
Hi, Ross Cameron invited you to join WAYN on March 10th 2011. Join Ross Cameron now: http://www.wayn.com/invite/19446-lvdc9f/fqdvo8-9qeb4tqrnger7 Connect with Ross and meet over 15 million members worldwide who have a passion for travel and do what they love: http://www.wayn.com/invite/19765-lvdc9f/fqdvo8-9qeb4tqrnger7 See you online! The WAYN Team -------------- To stop receiving add friend requests from Ross Cameron, click here: http://www.wayn.com/-/19448-lvdc9f?m=1282278&c=531037960 To stop receiving any notifications from WAYN, click here: http://www.wayn.com/-/19449-lvdc9f?c=531037960 |
|
From: WAYN <inv...@wh...> - 2011-03-10 13:06:32
|
Hi, Ross Cameron has left you a message on WAYN. To read message from Ross click on the link below: http://www.wayn.com/invite/23061-kwtc2c/fqdvo8-9qeb4tqrnger7 All the best, The WAYN Team ---------------------------------------- To stop receiving invite requests from Ross Cameron, click here: http://www.wayn.com/-/23068-kwtc2c?m=1282278&c=531037960 To stop receiving any notification from WAYN, click here: http://www.wayn.com/-/23069-kwtc2c?c=531037960 |
|
From: Kelly O'H. <Kel...@Su...> - 2008-04-08 18:49:31
|
Dito. We don't use it for formal Release Engineering builds, but we use it all the time to build the jdk in our automated build&test system. Just wish we had it on Windows for Visual Studio. -kto Ross Cameron wrote: > I still use it for bulk building a LOT of packages for my embedded OS, > haven't needed to upgrade in AAAAAAAAGES but would appreciate the > project not dying off :( > > On Tue, Apr 8, 2008 at 3:09 PM, Simon Braunschmidt > <sbr...@go...> wrote: >> Hi >> >> is cachecc1 still supported or used? >> >> Last version is 0.3 from 2004. >> >> I used it for a while but now i tracked down a bug in the linux kernel >> build system for arm architecture to the usage of cachecc1. The bug >> was actually the resuse of binary data that did in fact change, but >> the assembler call for cachecc1 read it from cache. >> >> I can provide a detailed description of the steps to reproduce the >> bug, or compare: >> http://groups.google.com/group/fa.linux.kernel/msg/7ae8172becd5e51f >> (piggy.o gets wrongly compiled with data from cache) >> >> It seems that the cachecc1 project is effectively dead so I really >> recommend to make this clear on the link to it from ccache homepage. >> >> Best Regards >> Simon Braunschmidt >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Register now and save $200. Hurry, offer ends at 11:59 p.m., >> Monday, April 7! Use priority code J8TLD2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> _______________________________________________ >> Cachecc1-list mailing list >> Cac...@li... >> https://lists.sourceforge.net/lists/listinfo/cachecc1-list >> > > > |
|
From: Simon B. <sbr...@go...> - 2008-04-08 17:52:49
|
Take special care when it comes to source code files that include
other files into them.
While cachecc1 while most probably take care of all kinds of #include,
the problem in my case came from an .incbin statement in an assembler
( .S ) file.
In the linux kernel build process the kernel gets built into a
./vmlinux kernel image. From this object some parts are copied into
./arch/arm/boot/Image (im hacking on arm as you can see). The Image
gets gzipped to ./arch/arm/boot/compressed/piggy.gz.
>From the piggy.gz the piggy.o file is compiled:
pseudo assembler code, compare piggy.S:
section .piggydata
:start_
.incbin "./arch/arm/boot/compressed/piggy.gz"
:end_
The problem seems to be that cachecc1 does not see that the source
piggy.S or the parameters to compile piggy.o changed and it does not
know about the binary include in piggy.S, so it serves the compile
request from cache.
The piggy.o the basis for all compressed, self extracting kernel
images, so they will not change but be served from cache all the time
when using cachecc1.
Maybe the .incbin command is new to gcc resp. as and is already
accounted for in ccache, can someone comment on this?
Be aware that the problem may be unnoticed for a while, as it was in
my case, because the resulting binaries may be run as regular, they
only dont get any changes.
2008/4/8, Ross Cameron <ros...@li...>:
> I still use it for bulk building a LOT of packages for my embedded OS,
> haven't needed to upgrade in AAAAAAAAGES but would appreciate the
> project not dying off :(
>
>
> On Tue, Apr 8, 2008 at 3:09 PM, Simon Braunschmidt
> <sbr...@go...> wrote:
> > Hi
> >
> > is cachecc1 still supported or used?
> >
> > Last version is 0.3 from 2004.
> >
> > I used it for a while but now i tracked down a bug in the linux kernel
> > build system for arm architecture to the usage of cachecc1. The bug
> > was actually the resuse of binary data that did in fact change, but
> > the assembler call for cachecc1 read it from cache.
> >
> > I can provide a detailed description of the steps to reproduce the
> > bug, or compare:
> > http://groups.google.com/group/fa.linux.kernel/msg/7ae8172becd5e51f
> > (piggy.o gets wrongly compiled with data from cache)
> >
> > It seems that the cachecc1 project is effectively dead so I really
> > recommend to make this clear on the link to it from ccache homepage.
> >
> > Best Regards
> > Simon Braunschmidt
> >
>
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> > Register now and save $200. Hurry, offer ends at 11:59 p.m.,
> > Monday, April 7! Use priority code J8TLD2.
> > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> > _______________________________________________
> > Cachecc1-list mailing list
> > Cac...@li...
> > https://lists.sourceforge.net/lists/listinfo/cachecc1-list
> >
>
>
>
>
> --
> I have heard there are troubles of more than one kind.
> Some come from ahead and some from behind.
> But I've bought a big bat. I'm all ready you see.
> Now my troubles are going to have toubles with me!
> -- Dr. Seuss
>
|
|
From: Ross C. <ros...@li...> - 2008-04-08 16:00:48
|
I still use it for bulk building a LOT of packages for my embedded OS, haven't needed to upgrade in AAAAAAAAGES but would appreciate the project not dying off :( On Tue, Apr 8, 2008 at 3:09 PM, Simon Braunschmidt <sbr...@go...> wrote: > Hi > > is cachecc1 still supported or used? > > Last version is 0.3 from 2004. > > I used it for a while but now i tracked down a bug in the linux kernel > build system for arm architecture to the usage of cachecc1. The bug > was actually the resuse of binary data that did in fact change, but > the assembler call for cachecc1 read it from cache. > > I can provide a detailed description of the steps to reproduce the > bug, or compare: > http://groups.google.com/group/fa.linux.kernel/msg/7ae8172becd5e51f > (piggy.o gets wrongly compiled with data from cache) > > It seems that the cachecc1 project is effectively dead so I really > recommend to make this clear on the link to it from ccache homepage. > > Best Regards > Simon Braunschmidt > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Register now and save $200. Hurry, offer ends at 11:59 p.m., > Monday, April 7! Use priority code J8TLD2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Cachecc1-list mailing list > Cac...@li... > https://lists.sourceforge.net/lists/listinfo/cachecc1-list > -- I have heard there are troubles of more than one kind. Some come from ahead and some from behind. But I've bought a big bat. I'm all ready you see. Now my troubles are going to have toubles with me! -- Dr. Seuss |
|
From: Simon B. <sbr...@go...> - 2008-04-08 13:09:16
|
Hi is cachecc1 still supported or used? Last version is 0.3 from 2004. I used it for a while but now i tracked down a bug in the linux kernel build system for arm architecture to the usage of cachecc1. The bug was actually the resuse of binary data that did in fact change, but the assembler call for cachecc1 read it from cache. I can provide a detailed description of the steps to reproduce the bug, or compare: http://groups.google.com/group/fa.linux.kernel/msg/7ae8172becd5e51f (piggy.o gets wrongly compiled with data from cache) It seems that the cachecc1 project is effectively dead so I really recommend to make this clear on the link to it from ccache homepage. Best Regards Simon Braunschmidt |
|
From: Steve D. <st...@de...> - 2004-09-13 20:26:59
|
I get the following error when building on OSX 10.3.5: % make gcc -o obj/cachecc1.o cachecc1.c -c -O -Wall -Werror -fPIC cachecc1.c: In function `exec_cachecc1': cachecc1.c:306: warning: visibility attribute not supported in this configuration; ignored make: *** [obj/cachecc1.o] Error 1 -- Steve |
|
From: Gavin <ga...@ve...> - 2004-08-01 19:55:56
|
I use noatime,nodiratime in my mount options (big performance boost in = some circumstances). To help find and delete old files in cachecc1 cache dir (e.g. using = tmpwatch tool to delete "old" files from /tmp), does cachecc1 "touch" = files' ctime (or mtime) if, and only if, they are actually used during a = compile? I've been using cachecc1 with Gentoo for a few months now with excellent = results. Cheers, Gavin |
|
From: <ben...@id...> - 2004-05-25 09:06:52
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Lars <lar...@gm...> - 2004-05-21 19:54:58
|
Hi, i had the LD_PRELOAD and LD_PRELOAD_32 set to the location of the cachecc1.= so and got into trouble, because the name resolution didnt work any more: root@kasi:~# cat /etc/resolv.conf nameserver 192.168.1.11 search buch.netz root@kasi:~# nslookup -sil firewall Server: 192.168.1.11 Address: 192.168.1.11#53 Name: firewall.buch.netz Address: 192.168.1.11 root@kasi:~# ping firewall ping: unknown host firewall root@kasi:~# fgrep host /etc/nsswitch.conf hosts: files dns=20 so my idea to set the enviroment on startup for the whole system was a bad = one. (/etc/profile) regards Lars T=E4uber |
|
From: Benoit Poulot-C. <bp...@tu...> - 2004-04-21 09:51:01
|
Hi Gavin, > After deleting all files in the cachedir, I compiled cachecc1. > Thus, the contents of the cachedir relate only to cachecc1. > There are two broken symbolic links in cachecc1's cachedir. > Is this normal (maybe associated with not using IGNOREWARNINGS), > or should I investigate further? Yes, it is normal. cachecc1 use (danglink) symbolic links to store short data, for two reasons : 1) if it is short enough, it will be stored in the inode (it may depend on the filesystem) and save space, and time... 2) to read it, one syscall (readlink) is enough. It is faster than 3 (open+read+close). -- Benoit |
|
From: Gavin <ga...@ve...> - 2004-04-20 20:27:32
|
Hi Benoit, After deleting all files in the cachedir, I compiled cachecc1. Thus, the contents of the cachedir relate only to cachecc1. There are two broken symbolic links in cachecc1's cachedir. Is this normal (maybe associated with not using IGNOREWARNINGS), or should I investigate further? Thanks, Gavin P.S. I really like cachecc1 .. pretty cool tool. /var/tmp/cachedir/as+: total 4 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./ drwxrwsrwx 18 portage portage 2048 Apr 20 12:54 ../ lrwxr-xr-x 1 portage portage 22 Apr 20 12:54 1y7lOvQ5d8Hj5d1egikDva = -> g5L5xSOp5QGfh1F5oZ1dm5 /var/tmp/cachedir/cc1: total 4 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./ drwxrwsrwx 18 portage portage 2048 Apr 20 12:54 ../ lrwxr-xr-x 1 portage portage 22 Apr 20 12:54 fRlxYAyfXSHXGy5S4GSY14 = -> AMXA15yA_8lK2rvlJFIAoD # cd cachedir; find . -ls 2049 2 drwxrwsrwx 18 portage portage 2048 Apr 20 12:54 . 2055 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./as+ 2056 0 lrwxr-xr-x 1 portage portage 22 Apr 20 12:54 = ./as+/1y7lOvQ5d8Hj5d1egikDva -> g5L5xSOp5QGfh1F5oZ1dm5 2075 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./Xo 2076 2 -rw-r--r-- 1 portage portage 1172 Apr 20 12:54 = ./Xo/Wc6VXXj1@4Tl8HBhtBnc 2077 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./DI 2078 2 -rw-r--r-- 1 portage portage 1008 Apr 20 12:54 = ./DI/RM4Z_c1gOE5qdxEDTt3G 2059 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./sz 2060 12 -rw-r--r-- 1 portage portage 11597 Apr 20 12:54 = ./sz/oy80LApfrnGPAgoknRUb 2081 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./r6 2082 2 -rw-r--r-- 1 portage portage 1000 Apr 20 12:54 = ./r6/hDa0MFV21Cp5tUgGY84I 2084 18 -rw-r--r-- 1 root root 17992 Apr 20 12:54 = ./COPYING 2079 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./Pv 2080 2 -rw-r--r-- 1 portage portage 463 Apr 20 12:54 = ./Pv/7iiw86l4nJJ3wGTUk1Um 2061 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./fB 2062 4 -rw-r--r-- 1 portage portage 3896 Apr 20 12:54 = ./fB/ByrvMRrtv_KOsC5hjh0D 2071 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./DT 2072 6 -rw-r--r-- 1 portage portage 4512 Apr 20 12:54 = ./DT/2e4Ddrxpd7NbHV_OxLgR 2085 4 -rw-r--r-- 1 root root 2627 Apr 20 12:54 = ./README.cachecc1 2054 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 = ./gcc3_4037c6ba_16140_2080b_306 2073 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./tK 2074 4 -rw-r--r-- 1 portage portage 2660 Apr 20 12:54 = ./tK/QZyXToAU@pT_Ibrk60oQ 2053 8 -rw-r--r-- 1 portage portage 7119 Apr 20 12:54 = ./gb_cc_nosandbox.log 2069 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./Y3 2070 4 -rw-r--r-- 1 portage portage 3172 Apr 20 12:54 = ./Y3/ajtloxRROQJPPLm2@YfR 2050 6 -rw-r--r-- 1 portage portage 4317 Apr 20 12:54 = ./env.21794 2067 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./uX 2068 8 -rw-r--r-- 1 portage portage 7191 Apr 20 12:54 = ./uX/C4kDnPyie9k@jReIMReB 2057 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./6m 2058 10 -rw-r--r-- 1 portage portage 8196 Apr 20 12:54 = ./6m/7IpBhHMoj6KvsUvM4hfl 2083 2 -rw-r--r-- 1 root root 969 Apr 20 12:54 = ./README.distcc 2051 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./cc1 2052 0 lrwxr-xr-x 1 portage portage 22 Apr 20 12:54 = ./cc1/fRlxYAyfXSHXGy5S4GSY14 -> AMXA15yA_8lK2rvlJFIAoD 2065 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./R1 2066 6 -rw-r--r-- 1 portage portage 4600 Apr 20 12:54 = ./R1/17DmurAGgq82db9llmaJ 2063 2 drwxr-sr-x 2 portage portage 2048 Apr 20 12:54 ./28 2064 12 -rw-r--r-- 1 portage portage 11544 Apr 20 12:54 = ./28/Pf9TFMiLMzQqoN4ThLhm |
|
From: Benoit Poulot-C. <bp...@us...> - 2004-03-28 22:26:06
|
Hi, I have just released cachecc1-0.3. As tuxfamily.org is dead, I have moved the project to sourceforge. The new home page is : http://cachecc1.sourceforge.net/ The new release can be downloaded from : http://prdownloads.sourceforge.net/cachecc1/cachecc1-0.3.tar.gz?downloadAn arch repository can be found at : http://cachecc1.sourceforge.net/arch The mailing list has moved to : http://sourceforge.net/mail/?group_id=91955 Members of the cachecc1.tuxfamily.org mailing list are invited to join the new mailing list. The most important feature of this release is probably the interface with distcc, that allows to distribute compilations that are not cached. -- Benoit |
