Re: OpenCASCADE 6.9.1

2015-11-08 Thread Thierry Thomas
Le ven 30 oct 15 à 12:08:36 +0100, Andrea Venturoli écrivait : > Hello. > This is what I've come up with, by modifying your port. Just committed, thanks for your help! -- Th. Thomas. pgpmAMB3K8YNU.pgp Description: PGP signature

Re: OpenCASCADE 6.9.1

2015-10-31 Thread Thierry Thomas
Le sam 31 oct 15 à 11:40:52 +0100, Andrea Venturoli écrivait : > I think it can be done, but I'll let Thierry (the port maintainer) decide. > I'm happy to help, but I don't want to step too much into his way. Thanks Andrea for your help! I'll check it ASAP. In the meantime, the distfile is ava

Re: OpenCASCADE 6.9.1

2015-10-31 Thread Robert Huff
Andrea Venturoli writes: > On 10/30/15 13:25, Kurt Jaeger wrote: > > > There's no public distfile, only available if one registers ? > > Exactly. During the time before the advent of OpewnJDK, one had to do something similar to get the sources to Sun's Java. No re-hosting allowed. `

Re: OpenCASCADE 6.9.1

2015-10-31 Thread Andrea Venturoli
On 10/31/15 11:11, Kurt Jaeger wrote: databases/sqldeveloper/Makefile has a construct in its Makefile that helps the user to understand where he has to go and where he has to put the distfile: IMHO it would be better for everyone if we hosted the distfile somewhere else and let the port infra

Re: OpenCASCADE 6.9.1

2015-10-31 Thread Kurt Jaeger
Hi! > > There's no public distfile, only available if one registers ? > > Exactly. > > I believe the license (LGPL) allow redistribution, though, so the > distfile could be hosted somewhere else. > > This has never been a problem in previous releases of the port. It's a usability problem if o

Re: OpenCASCADE 6.9.1

2015-10-31 Thread Andrea Venturoli
On 10/30/15 13:25, Kurt Jaeger wrote: There's no public distfile, only available if one registers ? Exactly. I believe the license (LGPL) allow redistribution, though, so the distfile could be hosted somewhere else. This has never been a problem in previous releases of the port. bye

Re: OpenCASCADE 6.9.1

2015-10-30 Thread Kurt Jaeger
Hi! > This is what I've come up with, by modifying your port. > You might want to check because portlint/porttools give some warnings. > > Also, due to the obsolescence and vulnerability of freeimage, I didn't > even try to build with VIS. I had a quick look at this. There's no public distfile

Re: OpenCASCADE 6.9.1

2015-10-30 Thread Andrea Venturoli
On 10/19/15 21:36, Thierry Thomas wrote: Nothing special, but I've been travelling in Africa, and now I'm late with my ports... ATM I'm working on Code_Aster, so if you have some time to work on OpenCASCADE, that would be fine! Thanks Hello. This is what I've come up with, by modifying your

Re: OpenCASCADE upgrade trouble

2014-12-02 Thread Andrea Venturoli
On 12/02/14 18:36, Thierry Thomas wrote: Could you please put it somewhere or send it to me directly? Sorry, I thought I did, but used the wrong address... Now you should have got it. bye & Thanks av. ___ freebsd-ports@freebsd.org mailing l

Re: OpenCASCADE upgrade trouble

2014-12-02 Thread Thierry Thomas
Le mar 2 déc 14 à 9:38:57 +0100, Andrea Venturoli écrivait : > > Could you please send me your build log (compressed, because it's > > huge!) > > Please, find it attached. > Problem is, there is no custom.sh in stage or work. It seems that the mailing list remove the attachments... Could you

Re: OpenCASCADE upgrade trouble

2014-12-02 Thread Andrea Venturoli
On 12/01/14 23:02, Thierry Thomas wrote: Could you please send me your build log (compressed, because it's huge!) Please, find it attached. Problem is, there is no custom.sh in stage or work. or try to deinstall it before the build? I don't think this would help, given the above. bye

Re: OpenCASCADE upgrade trouble

2014-12-02 Thread Andrea Venturoli
On 12/01/14 22:46, David Wolfskill wrote: Please read ports/UPDATING entry 20141127; its advice may well be relevant. Thanks for your answer, but this is not related. BTW I checked my port tree and have no such problem. Anyhow, I remember having this problem in the past; it was packing list

Re: OpenCASCADE upgrade trouble

2014-12-01 Thread David Wolfskill
On Mon, Dec 01, 2014 at 11:02:45PM +0100, Thierry Thomas wrote: > ... > > > Any hint? > > > > > > > Please read ports/UPDATING entry 20141127; its advice may well be > > relevant. > > Thanks David for the hint, but I'm not sure that it applies here, > because OpenCascade does not use Perl di

Re: OpenCASCADE upgrade trouble

2014-12-01 Thread Thierry Thomas
Le lun 1 déc 14 à 22:46:04 +0100, David Wolfskill écrivait : > > Hello. Hello, > > Today I tried updating OpenCASCADE to 6.8.0_1. > > > > However the process ends with: > > > > > ===> Registering installation for opencascade-6.8.0_1 > > > pkg-static: > > > lstat(/usr/ports/cad/opencascad

Re: OpenCASCADE upgrade trouble

2014-12-01 Thread David Wolfskill
On Mon, Dec 01, 2014 at 10:42:55PM +0100, Andrea Venturoli wrote: > Hello. > > Today I tried updating OpenCASCADE to 6.8.0_1. > > However the process ends with: > > > ===> Registering installation for opencascade-6.8.0_1 > > pkg-static: > > lstat(/usr/ports/cad/opencascade/work/stage/usr/loca

Re: OpenCASCADE upgrade fails on i386

2014-05-15 Thread Thierry Thomas
Le jeu 15 mai 14 à 10:57:13 +0200, Andrea Venturoli écrivait : > Hello. Hello, > >... > > Creating bzip'd tar ball in > > '/var/tmp/usr/ports/cad/opencascade/work/pkg/opencascade-6.7.1_1.tbz' > > tar: OpenCAS/custom_gcc_64_.sh: Cannot stat: No such file or directory > > tar: Error exit delaye

Re: OpenCASCADE

2013-04-04 Thread Stephen Montgomery-Smith
On 04/03/2013 12:34 PM, Andrea Venturoli wrote: > Also interesting is cat/netgen, whose Makefile states: >> .if ${PORT_OPTIONS:MOCC} >> BROKEN= The opencascade port needs to be updated before OCC >> will work > (this is why I'm cc-ing stephen). My initial naive attempts to build netgen wi

Re: OpenCASCADE

2013-04-03 Thread Andrea Venturoli
On 03/24/13 13:58, Thierry Thomas wrote: Have you checked that the ports depending on OpenCASCADE are really incompatible with this latest release? Somewhat... According to FreshPorts, there are 14 ports which require OpenCASCADE, all in category "cad". First is opencascade-tutorial, which

Re: OpenCASCADE

2013-03-24 Thread Thierry Thomas
Le ven 22 mar 13 à 14:58:48 +0100, Andrea Venturoli écrivait : > Hello. Hello Andrea, > Several months ago, I sent you a port skeleton for OpenCASCADE 6.5.2. > The version in ports is still at 6.3. > In the meanwhile 6.5.2 is already old, as 6.5.3 is out. > > I understand there are other ports

Re: OpenCASCADE

2013-03-22 Thread Max Brazhnikov
On Fri, 22 Mar 2013 14:58:48 +0100 Andrea Venturoli wrote: > Hello. > > Several months ago, I sent you a port skeleton for OpenCASCADE 6.5.2. > The version in ports is still at 6.3. > In the meanwhile 6.5.2 is already old, as 6.5.3 is out. > > I understand there are other ports in the tree which

Re: OpenCASCADE port outdated

2011-09-09 Thread Thierry Thomas
Le mar 6 sep 11 à 17:10:01 +0200, Andrea Venturoli écrivait : > Hello. Hello, > Port is at 6.3, but 6.5.1 is out. > Is upgrading under way or planned? Yes, I know, but unfortunately I have been too busy. Hope to work on it RSN. Anyway, patches are welcome! Regards, -- Th. Thomas. __

Re: Problem with devel/libtool22? [was Re: OpenCASCADE marked broken]

2010-04-10 Thread Thierry Thomas
Le Mar 6 avr 10 à 8:14:57 +0200, Andrea Venturoli écrivait : > Are you sure OpenCASCADE requires f77? > I looked into the source and didn't find any file like "*.f" or "*.for", > although of course they might have other extension or be generated > during the build process. > Also I can confi

Re: Problem with devel/libtool22? [was Re: OpenCASCADE marked broken]

2010-04-05 Thread Andrea Venturoli
On 04/06/10 00:26, Thierry Thomas wrote: Le Mar 23 mar 10 à 22:37:24 +0100, Andrea Venturoli écrivait : Just to let you know this used to work on 6.3, though I cannot test it anymore now. I can compile it without any problem on 7.2/i386, though I remove "USE_FORTRAN=yes". The latter is to av

Problem with devel/libtool22? [was Re: OpenCASCADE marked broken]

2010-04-05 Thread Thierry Thomas
Le Mar 23 mar 10 à 22:37:24 +0100, Andrea Venturoli écrivait : > Just to let you know this used to work on 6.3, though I cannot test it > anymore now. > > I can compile it without any problem on 7.2/i386, though I remove > "USE_FORTRAN=yes". > > The latter is to avoid compilation with gcc4.4,