Create and use a new module

82 views
Skip to first unread message

ctenllado

unread,
Nov 2, 2009, 8:05:23 AM11/2/09
to pocc-users
Hi:

I am trying to learn how to create and use a new module following the
manual. As it suggests I used autoskelet-0.1 to create the
cudascheduler module:

./make_project.sh cudascheduler /path_to_pocc/optimizers templates/
project_bin_static_shared NOTICE.cuda

This creates a directory called cudascheduler in /path_to_pocc/
optimizers/. However neither bootstrap.sh nor automake.am are copied
(I don't know if they should).

When I do the pocc-util alternate cuda the process ends with errors,
it couldn't find the bootstrap.sh. Then I copied some missing files
manually but at the end the pocc-util alternate cuda ends with the
following error:

[PoCC] Configuring cudascheduler in /path_to_pocc/optimizers/
cudascheduler with --disable-static --enable-shared --prefix=/
path_to_pocc/optimizers/install-cudascheduler --with-scoplib=/
path_to_pocc/ir/install-scoplib
configure: WARNING: unrecognized options: --with-scoplib
configure: error: cannot find sources (project/include/project/
common.h) in . or ..
Error in configuration of cudascheduler

If I execute a ls in cudascheduler directory:

aclocal.m4 autom4te.cache bootstrap.sh config configure
configure.ac error.c foo.c include list.c Makefile.am
Makefile.in xmalloc.c xstrdup.c xstrerror.c

and in cudascheduler/include/cudascheduler:

common.h config-h.in error.h foo.h list.h


Can you help me?

Louis-Noel Pouchet

unread,
Nov 2, 2009, 4:56:09 PM11/2/09
to pocc-...@googlegroups.com
ctenllado wrote:
> Hi:
>
> I am trying to learn how to create and use a new module following the
> manual. As it suggests I used autoskelet-0.1 to create the
> cudascheduler module:
>
> ./make_project.sh cudascheduler /path_to_pocc/optimizers templates/
> project_bin_static_shared NOTICE.cuda
>

There is a mistake in the doc, my apologies. The correct line is:
$> ./make_project.sh cudascheduler
/full/path/to/pocc/optimizers/cudascheduler
templates/project_bin_static_shared NOTICE.cuda

The difference is the addition of /cudascheduler to the 1st argument of
the script.
The problem is that when using the buggy command line, you have added
crappy content to the optimizers/ script. Please delete the
optimizers/cudascheduler directory before re-running make_project.sh and
pocc-util alternate cuda.
For the other files, they are all useless but the directories
install-letsee, install-pluto, letsee and pluto. So delete all others
before re-running make_project.sh.

This should solve your problem.

++

--
Louis-Noel Pouchet
louis-noe...@inria.fr

Reply all
Reply to author
Forward
0 new messages