[Haskell] Vacancy Professor Software Technology
Dear colleague,Want to teach and do research in an exciting environment, in the fourth most happy city on earth (http://www.bbc.com/travel/feature/20131022-living-in-the-worlds-happiest-places)? Or do you think a colleague might be a suitable candidate? Let us know. We have a vacancy for:Full Professor Software Technology (0.8 – 1.0 fte)The full professor directs and supervises research in the field of software technology, specifically in the design and development of formalisms and methodologiesfor effective program construction and program analysis. She or he develops new initiatives, aiming at research programs in software technology that are relevantfor software systems in general and for the departmental focus domain of game technology. This includes the acquisition of external research funds at the nationaland international level, and the dissemination, of research results and its applications, to the relevant research communities. The initiatives should be developedin line with worldwide trends in software technology such as software generation, domain-specific languages, and multi-core programming.The full professor has a leading role in teaching and supervision. She or he contributes to the department’s curriculum development at all levels: BSc, MSc, andPhD. The full professor plays an active role in the leadership and administrative duties of the Division of Software Systems, the Department and/or Faculty. ProfileCandidates must have an excellent track record in research, teaching and leadership, as exemplified by:Research:• A PhD degree in Computer Science or a closely related scientific field.• An excellent publication record, including papers in high-impact journals and conference proceedings.• Proven ability to obtain extramural funding for research and to provide leadership in collaborative research programs.Teaching:• Experience and enthusiasm for teaching and student supervision.• Experience and leadership in curriculum development.• Academic leadership:• An active role in leading (national and international) activities in the area of the chair and participation in academic communities.• An established international network of research partnerships with other leading research groups and institutions.• Experience in administrative roles at department or faculty level.Utrecht University employs a system of quality assessment for teaching and research with consequences for career development. This implies that, in addition tohaving a PhD in a relevant field of research, a successful candidate also possesses appropriate senior level academic teaching and research qualifications. TheFaculty may use an assessment as an instrument in the selection procedure. We offer a permanent position as full professor at 0.8 – 1.0 fte. The gross salary depends on qualifications and experience, and ranges between € 5,003.- and €7,285.- per month (salary scale H2, of the Collective Labour Agreement of the Dutch Universities).The salary is supplemented with a holiday bonus of 8% and an end-of-year bonus of 8.3% per year. In addition we offer: an excellent pension scheme, a partiallypaid parental leave, and flexible employment conditions. Conditions are based on the Collective Labour Agreement Dutch Universities.More information about terms of employment:http://www.uu.nl/EN/informationfor/jobseekers/Working-for-Utrecht-University/terms-of-employment/Pages/default.aspxAbout the department:§The Department of Information and Computing Sciences (http://www.cs.uu.nl/) has a strong national and international reputation in computer science and ininformation science. The department’s research activities are clustered into four divisions, viz. Software Systems, Artificial Intelligence, Virtual Worlds, andInteraction Technology. Each division is specialized in a specific research area within computer science and contributes from this area to the department’s overallfocus on Game Technology.The focus area of Game Technology deals with all technological aspects of games, and of interactive virtual experiences more in general; Game Technologyconstitutes one of the four strategic research themes of the Faculty of Science. While the research activities of the four computer-science divisions meet in theGame Technology area, research is not restricted to games application. Through collaboration with (often external) partners, the various divisions also connectwith the other strategic research themes of the university, viz. life sciences, sustainability, and youth and identity.The Department of Information and Computing Sciences offers educational bachelor programs in computer science and information science, and three (English)research master programs, viz. Computing Science, Game and Media Technology, and Business Informatics; the Department is further involved in the masterprogram Artificial Intelligence. Three years ago the Department introduced a track on Game Technology in the bachelor program in computer
Re: [arch-haskell] devtools version problem
Hello again,
With a little help of git bisect on the devtools repository (
https://projects.archlinux.org/devtools.git/), I have found the reason of
the following kind of messages:
Diff-0.3.0: cannot find libHSDiff-0.3.0.a on library path (use --force
to override)
The commit 0d16a9135055d0c998cac236608cb630c93f0ac7 (
https://projects.archlinux.org/devtools.git/commit/?id=0d16a9135055d0c998cac236608cb630c93f0ac7)
make !staticlibs default in makepkg.conf. So every chroot environment
containing this version will throw away static libraries when building
packages. The commit was pushed to arch repository 8 days ago, so only
newest chroot environments have this problem.
I see two solutions:
1. Change the makepkg.conf when creating the chroot environment to
remove !staticlibs,
or, better
2. Change cblrepo to add «options=('strip' 'staticlibs')» when generating
the PKGBUILDs.
Because I don't know if all packages have/need these static libraries, I
ask you, experienced arch-haskeller, to point me the right direction?
Best regards,
Fabien Dubosson
2013/10/28 Fabien Dubosson fabien.dubos...@gmail.com
Hi,
Continuing my investigations about my building problem, I think I have
found its cause and a way to reproduce it.
Briefly, the important point is that the chroot environment must be
created with devtools = 20130408 (the last version that has makechrootpkg
that support the -d flag). Once created, packages can be built even with
newest versions of devtools that doesn't support the -d flag (but this
requires to adapt the makeahpkg script to remove it).
At the opposite, if the chroot is created with a newer version, Haskell
packages will build and install, but with a message like:
Diff-0.3.0: cannot find libHSDiff-0.3.0.a on library path (use --force
to override)
To reproduce, run the following commands once with devtools 20130408 and
once with 20131020 (and don't forget to remove completely the habs-temp
folder between the two tests):
git clone https://github.com/StreakyCobra/habs.git habs-temp
cd habs-temp
cblrepo sync
cblrepo pkgbuild Diff
./makeahpkg -c -- Diff
# sudo rm habs-temp -rf
Can anybody confirm this behavior? Or is it just me?
Best regards,
Fabien Dubosson
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] devtools version problem
On Mon, Oct 28, 2013 at 12:39:31PM +0100, Fabien Dubosson wrote:
Hello again,
With a little help of git bisect on the devtools repository (
https://projects.archlinux.org/devtools.git/), I have found the reason of
the following kind of messages:
Diff-0.3.0: cannot find libHSDiff-0.3.0.a on library path (use --force
to override)
The commit 0d16a9135055d0c998cac236608cb630c93f0ac7 (
https://projects.archlinux.org/devtools.git/commit/?id=0d16a9135055d0c998cac236608cb630c93f0ac7)
make !staticlibs default in makepkg.conf. So every chroot environment
containing this version will throw away static libraries when building
packages. The commit was pushed to arch repository 8 days ago, so only
newest chroot environments have this problem.
Interesting. I suspect this is related to the discussions on the
Arch mailing list about static libs.
I see two solutions:
1. Change the makepkg.conf when creating the chroot environment
to remove !staticlibs, or, better
2. Change cblrepo to add «options=('strip' 'staticlibs')» when
generating the PKGBUILDs.
Because I don't know if all packages have/need these static
libraries, I ask you, experienced arch-haskeller, to point me the
right direction?
We absolutely do need the static libs to be included in the generated
packages. Ghc 7.6 uses static linking by default and thus all our
tool packages rely on static libs in order to build properly. It
could of course be changed but it'd require a change to cblrepo to
generate PKGBUILDs that uses `depends` rather than `makedepends`.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
Hard work may not kill me, but why take the chance.
pgpglsbDrZuE3.pgp
Description: PGP signature
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
[arch-haskell] Build machine broken!
A couple of things came up during the last few days that made me interested in upgrading the build machine I've been using. Unfortunately the system was so far out of date that the update wasn't very easy, and I managed to completely break it. Furthermore, the owner of the machine is on a trip so it's unlikely to be brought back to working order any time soon :( Unfortunately this means that I'm unlikely to perform any updates of [haskell-core] for a while. Unless of course someone comes forward with an offer of a (temporary) replacement ;) /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus Failure is not an option. It comes bundled with the software. pgpH2qlMXO7ac.pgp Description: PGP signature ___ arch-haskell mailing list arch-haskell@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
Re: [arch-haskell] devtools version problem
We absolutely do need the static libs to be included in the generated
packages. Ghc 7.6 uses static linking by default and thus all our
tool packages rely on static libs in order to build properly. It
could of course be changed but it'd require a change to cblrepo to
generate PKGBUILDs that uses `depends` rather than `makedepends`.
So I made a proposition (pull request to cblrepo) to explicitly include the
staticlibs option in generated PKGBUILD since this is the GHC default
linking (and also because it was suggested by Allan here:
https://mailman.archlinux.org/pipermail/arch-dev-public/2013-October/025542.html
)
Actually the generated PKGBUILDs seem to already use 'depends' and not
'makedepends', or am I missing the point?
I also noticed two points: First it seems the archlinux default idea is to
use dynamic linking:
https://mailman.archlinux.org/pipermail/arch-general/2013-October/034337.html.
Secondly GHC offers the possibility to build and use dynamic libraries:
http://www.haskell.org/ghc/docs/7.6.3/html/users_guide/using-shared-libs.html.
Based on these two facts, it appears possible to build the haskell
ecosystem on a dynamic library principle. It will of course require a large
refactoring, but does it worth it? It is just curiosity ;)
2013/10/28 Magnus Therning mag...@therning.org
On Mon, Oct 28, 2013 at 12:39:31PM +0100, Fabien Dubosson wrote:
Hello again,
With a little help of git bisect on the devtools repository (
https://projects.archlinux.org/devtools.git/), I have found the reason
of
the following kind of messages:
Diff-0.3.0: cannot find libHSDiff-0.3.0.a on library path (use
--force
to override)
The commit 0d16a9135055d0c998cac236608cb630c93f0ac7 (
https://projects.archlinux.org/devtools.git/commit/?id=0d16a9135055d0c998cac236608cb630c93f0ac7
)
make !staticlibs default in makepkg.conf. So every chroot environment
containing this version will throw away static libraries when building
packages. The commit was pushed to arch repository 8 days ago, so only
newest chroot environments have this problem.
Interesting. I suspect this is related to the discussions on the
Arch mailing list about static libs.
I see two solutions:
1. Change the makepkg.conf when creating the chroot environment
to remove !staticlibs, or, better
2. Change cblrepo to add «options=('strip' 'staticlibs')» when
generating the PKGBUILDs.
Because I don't know if all packages have/need these static
libraries, I ask you, experienced arch-haskeller, to point me the
right direction?
We absolutely do need the static libs to be included in the generated
packages. Ghc 7.6 uses static linking by default and thus all our
tool packages rely on static libs in order to build properly. It
could of course be changed but it'd require a change to cblrepo to
generate PKGBUILDs that uses `depends` rather than `makedepends`.
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
Hard work may not kill me, but why take the chance.
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
___
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell
