On Sun, 28 Jul 2013 14:10:21 +0200 "O. Hartmann" <[email protected]> wrote:
> On Sun, 28 Jul 2013 11:03:46 +0200 > "O. Hartmann" <[email protected]> wrote: > > > On Sun, 28 Jul 2013 10:51:57 +0300 > > Pekka Jääskeläinen <[email protected]> wrote: > > > > > On 07/27/2013 03:56 AM, Erik Schnetter wrote: > > > > I am currently not aware of any build or test failures for the > > > > release branch. I have thus created a new release candidate, > > > > pocl-0.8rc8. > > > > > > There was a couple of regressions with VML: > > > https://launchpad.net/pocl/+milestone/0.8 > > > > > > https://bugs.launchpad.net/pocl/+bug/1204572 > > > https://bugs.launchpad.net/pocl/+bug/1204427 > > > > > > Do you have ideas for them I could try? > > > > > > Also, what about the FreeBSD issues, have those been resolved with > > > the latest RCs, Oliver? > > > > > > > Hello Pekka. > > > > I'm quite time constraint at the moment, sorry for the silence and > > late response. > > > > I just did some builds of RC8 and it build fine, but I didn't do > > tests (I will do this immediately). > > > > My primary concern is more LLVM-3.3 and the way the maintainer of > > the port devel/llvm in FreeBSD. There has been a branch devel/llvm33 > > refelcting llvm-3.3 as well as in future llvm-3.4 and so on, but the > > binaries are tagged "llvm-$VERSION, so llvm-info is becoming > > llvm-info33 now. I ran into trouble using LLVM 3.3 via the port and > > so I'm stuck with devel/llvm, which is in effect LLVM 3.2. This is > > posssibly about to change soon. > > > > I didn't look into POCL whether the LLVM binaries used are somehow > > maintained via variables like LLVM-INFO pointing to something that > > is searched/provided for and can be exchanged by the "port system" > > or the autotool environment automatically. In this matter, I'm > > still a novice with autotools. > > > > At this very moment, on FreeBSD-10.0 CURRENT the testsuite is stuck > > somehow in an endless loop and I guess it is due to llvm-3.2 (the > > base system is using clang 3.3 by now). > > > > I will check on that. > > > > Oliver > > FreeBSD's port maintainer tagg their LLVM binaries with "MajorMinor" > like llvm-config33. POCL's autotool environment is looking for > llvm-config-3.3, llvm-config-3.4 et cetera, that is usually the way it > is done in Linux distros. > > I guess life would go easier for me (and FreeBSD fellows) if the > autoconfiguration also would look for the existence of FreeBSD-style > tagged versions of the LLVM binaries. I would appreciate that. > > > Oliver Attached, the diff of configure.ac which solves the problem. Sorry for the hasty noises ... oh
patch-configure.ac
Description: Binary data
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
