You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2010 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Linoo G. <lee...@ya...> - 2013-06-06 14:37:35
|
http://lebusinessducoin.com/ljmug/%hahoenbfpecrg%/%qqkbullocxaa% |
From: Richard O'K. <ok...@cs...> - 2012-09-17 04:00:43
|
v% uname -a Linux vex.otago.ac.nz 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux v% gcc --version gcc (GCC) 4.4.2 20091027 (Red Hat 4.4.2-7) [snip] v% g++ --version g++ (GCC) 4.4.2 20091027 (Red Hat 4.4.2-7) [snip] Initially the program would not compile. Many files needed #include <stdlib.h> and/or #include <stdio.h> and/or #include <string.h>. It seemed advisable to add -m32 to CFLAGS and CXXFLAGS. There is a place where there's a switch with an EOF case but the Bits type is apparently unsigned. ./check.sh: line 6: 26032 Segmentation fault (core dumped) ./pc > ./Results/pc.log FAIL: check.sh ================================================= 1 of 1 tests failed Please report to y-a...@li... ================================================= Results/pc.log is empty. |
From: Linoo G. <lee...@ya...> - 2010-01-07 21:07:13
|
Hello i use with opensuse 11.1 and gcc 4.2.1 i have some problems , please help me, ( make[3]: Entering directory `/home/dell/Thesis/yapi-2.0.0/tst/exit' ../check.sh: line 6: 9036 Segmentation fault ./pc > ./Results/pc.log FAIL: check.sh ================================================= 1 of 1 tests failed Please report to y-a...@li... ================================================= make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/home/dell/Thesis/yapi-2.0.0/tst/exit' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/dell/Thesis/yapi-2.0.0/tst/exit' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/dell/Thesis/yapi-2.0.0/tst' make: *** [check-recursive] Error 1 ) |
From: Linoo G. <lee...@ya...> - 2010-01-04 08:10:31
|
Hello i have some problems when i type make check , but for making install there is no error. does yapi work correctly? " make[3]: Entering directory `/home/dell/Thesis/yapi-2.1.1/tst/exit' ../check.sh: line 6: 3727 Segmentation fault ./pc > ./Results/pc.log FAIL: check.sh ================================================= 1 of 1 tests failed Please report to y-a...@li... ================================================= make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/home/dell/Thesis/yapi-2.1.1/tst/exit' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/dell/Thesis/yapi-2.1.1/tst/exit' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/dell/Thesis/yapi-2.1.1/tst' make: *** [check-recursive] Error 1 " |
From: Linoo G. <lee...@ya...> - 2009-12-21 09:48:48
|
Hello when i want to make check yapi , these messae were appeared: make[2]: Leaving directory `/home/dell/Desktop/Thesis/yapi-2.1.1/src' make[1]: Leaving directory `/home/dell/Desktop/Thesis/yapi-2.1.1/src' Making check in tst make[1]: Entering directory `/home/dell/Desktop/Thesis/yapi-2.1.1/tst' Making check in exit make[2]: Entering directory `/home/dell/Desktop/Thesis/yapi-2.1.1/tst/exit' make check-TESTS make[3]: Entering directory `/home/dell/Desktop/Thesis/yapi-2.1.1/tst/exit' ../check.sh: line 6: 7675 Segmentation fault ./pc > ./Results/pc.log FAIL: check.sh ================================================= 1 of 1 tests failed Please report to y-a...@li... ================================================= make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/home/dell/Desktop/Thesis/yapi-2.1.1/tst/exit' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/dell/Desktop/Thesis/yapi-2.1.1/tst/exit' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/dell/Desktop/Thesis/yapi-2.1.1/tst' make: *** [check-recursive] Error 1 |
From: sandeep y. <iit...@gm...> - 2009-11-29 17:38:04
|
Hi, I am trying to install in my computer.But, I am getting the following error. I will be glad if you can help me in installing it. make[2]: Entering directory `/home/sandeep/Desktop/yapi-2.1.1/tst/exit' make check-TESTS make[3]: Entering directory `/home/sandeep/Desktop/yapi-2.1.1/tst/exit' ./check.sh: line 6: 26106 Segmentation fault ./pc > ./Results/pc.log FAIL: check.sh ================================================= 1 of 1 tests failed Please report to y-a...@li... ================================================= make[3]: *** [check-TESTS] Error 1 make[3]: Leaving directory `/home/sandeep/Desktop/yapi-2.1.1/tst/exit' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/home/sandeep/Desktop/yapi-2.1.1/tst/exit' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/sandeep/Desktop/yapi-2.1.1/tst' make: *** [check-recursive] Error 1 Waiting for your earliest reply, Sincerely, -- Y.SANDEEP Final year Under Graduate Computer Science and Engineering Indian Institute of Technology,Kharagpur West Bengal,India-721302 contact no-09734438120 |
From: Michael B. <be...@cs...> - 2009-02-24 14:55:12
|
Dear y-api team, I'm a PhD student and wanted to test your Y-API environment. I've recently checked out your cvs-yapi repository and tried to compile the project to execute some examples. My first problem was compiling on a 64-bit machine. The architecture was unknown and some type conversation were wrong, e.g. void* to int results in loss of precision. I solved the problem by using an intrepid32 chroot environment and setting up some 32-bit flags (CC="gcc -m32" CXX="c++ -m32"). Compilation seems to work, but I needed to fix some includes and missed methods declaration. Finally I got the project compiled but "make check" results in: > make[3]: Entering directory `/home/beyer/svn/misc/yapi/yapi/tst/jpeg' > ./check.sh: line 6: 1509 Segmentation fault ./jpeg $SRCDIR/Stimuli/shuttle ./Results/shuttle > FAIL: check.sh > ================================================= > 1 of 1 tests failed > Please report to y-a...@li... > ================================================= I'm astonished. I thought due to the usage of yapi in many research papers, such problems are already fixed. Then I ask me the question "Is this project still alive, because the last change log is from 2006? Are there any other developments based on YAPI?". I hope you can give me some hints about the current status of the project. Thank you very much in advance, for giving me some informations. Best regards Micha -- If you are not the adressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support. Dipl.-Ing. Michael Beyer Technical University of Berlin Software Engineering for Embedded Systems Fak. IV Sekretariat FR5-6, Raum FR 5024, Franklinstr. 28/29, D-10587 Berlin, Germany Tel.: +49(30)314-73 451, Fax: +49(30)314-73 488 eMail: be...@cs... Subsequently a list with all things I had to fix: yapi/src/impl/rteimpl/fifoimpl.cc // added due to usage of INT_MAX #include <limits.h> yapi/src/base/check.cc // added due to usage of strcmp #include <string.h> yapi/src/rte/cosy/cosyprocess.cc // added due to usage of free #include <stdlib.h> yapi/src/rte/cosy/cosynetwork.h // added due to friend declaration conflicts void handler1(void* arg); void handler2(void* arg); void fatal_func(void* arg); void clean_func(void* arg); void zero0_func(void* arg); void zero1_func(void* arg); void zero2_func(void* arg); yapi/src/util/count.cc // added due to usage of strcmp #include <string.h> yapi/src/util/decodetype.cc // changed to usage of strncpy // #include <string> // Warum wird hier die Endung benötigt? #include <string.h> yapi/src/dotty/dotty.cc // added due to usage of getenv, strlen, strcpy. strcat #include <string.h> yapi/yapi/tst/jpeg/backend.cc // added due to usage of malloc #include <stdlib.h> yapi/yapi/tst/jpeg/dmx.cc // added due to usage of exit at line 44 #include <stdlib.h> yapi/yapi/tst/jpeg/frontend.cc // added due to usage of exit at line 40 #include <stdlib.h> yapi/yapi/tst/jpeg/main.cc // added due to usage of exit at line 21 #include <stdlib.h> yapi/yapi/tst/jpeg/sof.h // manually added by Michael Beyer due to usage void abort(); yapi/yapi/tst/jpeg/sof.cc // added due to usage of exit #include <stdlib.h> * and * // added due to usage of abort() void SOF::abort() { printf("\n"); printf("%s:\n", fullName()); printf("\tERROR:\tAbnormal end of decompression process!\n"); exit(1); } yapi/yapi/tst/jpeg/vld.cc // added due to usage of exit #include <stdlib.h> yapi/yapi/tst/pcv/main.cc // added due to usage of exit #include <stdlib.h> |
From: <su...@cs...> - 2008-11-01 17:32:46
|
Dear Sir/Madam, I downloaded the YAPI-2.1.0. When tried to install on Fedora 8 is giving following error in the cosynetwork.cc if /bin/sh ../../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/api -I../../../src/impl/rteimpl -I../../../src/base -I../../../src/rte/rapi -I../../../src/kernel/kapi -I../../../src/util -g -O2 -MT cosynetwork.lo -MD -MP -MF ".deps/cosynetwork.Tpo" -c -o cosynetwork.lo cosynetwork.cc; \ then mv -f ".deps/cosynetwork.Tpo" ".deps/cosynetwork.Plo"; else rm -f ".deps/cosynetwork.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/api -I../../../src/impl/rteimpl -I../../../src/base -I../../../src/rte/rapi -I../../../src/kernel/kapi -I../../../src/util -g -O2 -MT cosynetwork.lo -MD -MP -MF .deps/cosynetwork.Tpo -c cosynetwork.cc -fPIC -DPIC -o .libs/cosynetwork.o cosynetwork.cc: In function 'void handler1(void*)': cosynetwork.cc:188: error: 'fatal_func' was not declared in this scope cosynetwork.cc:189: error: 'clean_func' was not declared in this scope cosynetwork.cc: In function 'void handler2(void*)': cosynetwork.cc:201: error: 'zero0_func' was not declared in this scope cosynetwork.cc:204: error: 'fatal_func' was not declared in this scope cosynetwork.cc:205: error: 'clean_func' was not declared in this scope cosynetwork.cc: In function 'void zero0_func(void*)': cosynetwork.cc:230: error: 'zero1_func' was not declared in this scope cosynetwork.cc:231: error: 'zero2_func' was not declared in this scope make[4]: *** [cosynetwork.lo] Error 1 make[4]: Leaving directory `/home/sunil/YAPI/yapi-2.1.0/src/rte/cosy' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/sunil/YAPI/yapi-2.1.0/src/rte' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/sunil/YAPI/yapi-2.1.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/sunil/YAPI/yapi-2.1.0' make: *** [all] Error 2 I could not make out what those variable refer to. I tried to declare them as function but it did not work.It will be great help if you kindly help me. Thank you going through the mail. Warm Regards Sunil shah M.S(research) Indian Institute of Technology Delhi New Delhi -110016 India |