Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

2019-02-23 Thread Dima Pasechnik
On Sat, Feb 23, 2019 at 6:31 PM Diane Bruce  wrote:
[...]
> Dima, gerald has always been very helpful in all my communications> with him. 
> > Have you filed a PR for the fix? dropped  him an email?

Diane,
well, after reading many threads  on this issue I stumbled upon
https://forums.freebsd.org/threads/freebsd-11-2-libgcc_s-so-1-error.67031/
---it advises to add to  /etc/libmap.conf the line

libgcc_s.so.1 /usr/local/lib/gccX/libgcc_s.so.1

---where X to be replaced with the major gfortran version  one uses.

By the way, is this anywhere in the current documentation? These kinds
of things seem to be documented for FreeBSD 7.3,
cf. 
https://docs.freebsd.org/doc/7.3-RELEASE/usr/share/doc/en/articles/custom-gcc/configuring-ports-gcc.html
but then everything that needs this hack was  supposed to be resolved?

Naturally, this is ugly and should not be needed, and nothing like
this is needed on Linux (or Solaris).

As what I do on FreeBSD is porting a largish Python library
(basically, an update to the current Sagemath version (8.6) what's
inhttps://www.freshports.org/math/sage/, but the 1st goal would be
more modest, just an ability to build and run in the "user space", not
as a FreeBSD port), these kinds of workarounds aren't really feasible,
as long as "finished product" is concerned.

In fact, I started working on this on FreeBSD 11, where the math
library was lacking standard symbols for a number of complex
functions, and stopped, as I felt it's just too much of a hassle to
work around, and picked it up again after in FreeBSD 12 this has been
resolved (Steve (kargl) played a major role in it, I gather).

>
> I know we (gerald and ?? can't remember) tried a static lib change
> a few years ago. I believe it didn't work at the time due to missing
> symbols which we have since added.

I am trying to understand what the situation is. If everything that is
needed for this fix is already there, then what's precluding it from
going forward?

I've also looked at using flang instead of gfortran (it's great that
FreeBSD has it available), but it seems to come with its own set of
issues...

Thanks,
Dima
http://users.ox.ac.uk/~coml0531/
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

2019-02-23 Thread Diane Bruce
On Sat, Feb 23, 2019 at 10:52:03AM +, Dima Pasechnik wrote:
> On Sat, Feb 23, 2019 at 12:07 AM Steve Kargl
>  wrote:
> >
> > On Sat, Feb 23, 2019 at 09:19:01AM +1100, Dave Horsfall wrote:
> > > On Fri, 22 Feb 2019, Tijl Coosemans wrote:
> > >
> > > > If I were the lang/gcc maintainer this -rpath problem would be my number
> > > > one priority.  The current maintainer has never proposed any solutions
> > > > and when I submit patches he always resists.  I'm done wasting my time
> > > > fighting him.
> > >
> > > I'm late to this discussion (not being a Fortran/Python user) but is there
> > > any way to remove a recalcitrant maintainer?
> > >
> >
> > Dave,
> >
> > Can you explain what you mean?  The maintainer of the lang/gcc
> > ports is a long-time member of the GCC steering committee
> > and a long-time maintainer of all gcc FreeBSD ports.  There
> > are very few FreeBSD users (like 3 of us) who have commit access
> > to the gcc tree.  Seems like a dubious idea to remove one of
> > those 3.
> 
> Given the amount of time unsuspecting and half-suspecting users wasted
> on making Fortran code (often in form of a Python extension) working
> on FreeBSD (e.g. I probably wasted weeks), time is high to do
> something, e.g. commit the said patches---there is an agreement that
> they are correct, right?
> 
> Dima
> http://users.ox.ac.uk/~coml0531/

Dima, gerald has always been very helpful in all my communications
with him. Have you filed a PR for the fix? dropped  him an email?

I know we (gerald and ?? can't remember) tried a static lib change
a few years ago. I believe it didn't work at the time due to missing
symbols which we have since added. 


> 
> >
> > --
> > Steve

Diane
-- 
- d...@freebsd.org d...@db.net http://artemis.db.net/~db
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: FreeCAD 0.17 && /lib//libgcc_s.so.1

2019-02-23 Thread Dima Pasechnik
On Sat, Feb 23, 2019 at 12:07 AM Steve Kargl
 wrote:
>
> On Sat, Feb 23, 2019 at 09:19:01AM +1100, Dave Horsfall wrote:
> > On Fri, 22 Feb 2019, Tijl Coosemans wrote:
> >
> > > If I were the lang/gcc maintainer this -rpath problem would be my number
> > > one priority.  The current maintainer has never proposed any solutions
> > > and when I submit patches he always resists.  I'm done wasting my time
> > > fighting him.
> >
> > I'm late to this discussion (not being a Fortran/Python user) but is there
> > any way to remove a recalcitrant maintainer?
> >
>
> Dave,
>
> Can you explain what you mean?  The maintainer of the lang/gcc
> ports is a long-time member of the GCC steering committee
> and a long-time maintainer of all gcc FreeBSD ports.  There
> are very few FreeBSD users (like 3 of us) who have commit access
> to the gcc tree.  Seems like a dubious idea to remove one of
> those 3.

Given the amount of time unsuspecting and half-suspecting users wasted
on making Fortran code (often in form of a Python extension) working
on FreeBSD (e.g. I probably wasted weeks), time is high to do
something, e.g. commit the said patches---there is an agreement that
they are correct, right?

Dima
http://users.ox.ac.uk/~coml0531/

>
> --
> Steve
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


FreeBSD ports you maintain which are out of date

2019-02-23 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
lang/adacontrol | 1.18r9  | 1.20r9
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


freecad cannot build

2019-02-23 Thread ajtiM via freebsd-ports
All ports are built on FreeBSD-Release-12-p3 (amd64). I did install
package for french/med because french/aster doesn't build on amd64. But
on the end of building freecad I got:

/usr/bin/ld: error: unable to find library -lCoin
/usr/bin/ld: error: unable to find library -lGL
/usr/bin/ld: error: unable to find library -lXext
/usr/bin/ld: error: unable to find library -lSM
/usr/bin/ld: error: unable to find library -lICE
/usr/bin/ld: error: unable to find library -lX11
c++: error: linker command failed with exit code 1 (use -v to see
invocation) *** [lib/libFreeCADGui.so] Error code 1

make[4]: stopped in /usr/ports/cad/freecad/work/.build
1 error

make[4]: stopped in /usr/ports/cad/freecad/work/.build
*** [src/Gui/CMakeFiles/FreeCADGui.dir/all] Error code 2

make[3]: stopped in /usr/ports/cad/freecad/work/.build
--- src/Mod/TechDraw/App/CMakeFiles/TechDraw.dir/all ---
---
src/Mod/TechDraw/App/CMakeFiles/TechDraw.dir/DrawProjGroupItem.cpp.o
--- In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Mod/TechDraw/App/DrawProjGroupItem.cpp:30:
In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Base/Console.h:32:
In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Base/PyExport.h:42:
In file included
from /usr/local/include/python2.7/Python.h:88: 
/usr/local/include/python2.7/unicodeobject.h:534:5:
warning: 'register' storage class specifier is deprecated and
incompatible with C++17 [-Wdeprecated-register] register PyObject
*obj, /* Object */
^ /usr/local/include/python2.7/unicodeobject.h:553:5: warning:
'register' storage class specifier is deprecated and incompatible with
C++17 [-Wdeprecated-register] register PyObject *obj  /* Object */
^ /usr/local/include/python2.7/unicodeobject.h:575:5: warning:
'register' storage class specifier is deprecated and incompatible with
C++17 [-Wdeprecated-register] register const wchar_t *w,  /* wchar_t
buffer */ ^ /usr/local/include/python2.7/unicodeobject.h:593:5:
warning: 'register' storage class specifier is deprecated and
incompatible with C++17 [-Wdeprecated-register] register wchar_t
*w,/* wchar_t buffer */ ^ In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Mod/TechDraw/App/DrawProjGroupItem.cpp:30:
In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Base/Console.h:32:
In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Base/PyExport.h:42:
In file included
from /usr/local/include/python2.7/Python.h:97: 
/usr/local/include/python2.7/stringobject.h:173:5:
warning: 'register' storage class specifier is deprecated and
incompatible with C++17 [-Wdeprecated-register] register PyObject
*obj, /* string or Unicode object */
^ /usr/local/include/python2.7/stringobject.h:174:5: warning:
'register' storage class specifier is deprecated and incompatible with
C++17 [-Wdeprecated-register] register char **s,  /* pointer to
buffer variable */
^ /usr/local/include/python2.7/stringobject.h:175:5: warning:
'register' storage class specifier is deprecated and incompatible with
C++17 [-Wdeprecated-register] register Py_ssize_t *len/* pointer to
length variable or NULL ^ 7 warnings generated. ---
src/Mod/TechDraw/App/CMakeFiles/TechDraw.dir/DrawParametricTemplate.cpp.o
--- In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Mod/TechDraw/App/DrawParametricTemplate.cpp:29:
In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Base/Exception.h:33:
In file included
from /usr/local/include/python2.7/Python.h:88: 
/usr/local/include/python2.7/unicodeobject.h:534:5:
warning: 'register' storage class specifier is deprecated and
incompatible with C++17 [-Wdeprecated-register] register PyObject
*obj, /* Object */
^ /usr/local/include/python2.7/unicodeobject.h:553:5: warning:
'register' storage class specifier is deprecated and incompatible with
C++17 [-Wdeprecated-register] register PyObject *obj  /* Object */
^ /usr/local/include/python2.7/unicodeobject.h:575:5: warning:
'register' storage class specifier is deprecated and incompatible with
C++17 [-Wdeprecated-register] register const wchar_t *w,  /* wchar_t
buffer */ ^ /usr/local/include/python2.7/unicodeobject.h:593:5:
warning: 'register' storage class specifier is deprecated and
incompatible with C++17 [-Wdeprecated-register] register wchar_t
*w,/* wchar_t buffer */ ^ In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Mod/TechDraw/App/DrawParametricTemplate.cpp:29:
In file included
from 
/usr/ports/cad/freecad/work/FreeCAD-0.17-13541-g9948ee4f1/src/Base/Exception.h:33:
In file included
from /usr/local/include/python2.7/Python.h:97: 
/usr/local/include/python2.7/stringobject.h:173:5:
warning: 'register' storage class 

Any user of esound daemon?

2019-02-23 Thread Baptiste Daroussin
Hello everyone,

esound daemon is a very long time abandonware, it is not used anymore by most
modern desktops applications.

I think it is time to start deprecating it and removing the infrastructure parts
(in ports) that supports it.

Are there any esound users left that can raise a voice to explain why and how
they are using esound? In my latest playing directly with I couldn't find any
value added compared to directly using OSS for example or using any of the other
daemons

Best regards,
Bapt


signature.asc
Description: PGP signature