Re: math/oleo pkd-descr

[Montgomery-Smith, Stephen]

On 9/23/20 12:40 PM, Fernando Apesteguía wrote:
> WARNING: This message has originated from an External Source. This may be a 
> phishing expedition that can result in unauthorized access to our IT System. 
> Please use proper judgment and caution when opening attachments, clicking 
> links, or responding to this email.
> 
> On Wed, Sep 23, 2020 at 6:34 PM Montgomery-Smith, Stephen
>  wrote:
>>
>> Dear Ports and people who recently modified the math/olea port,
>>
>> Do people agree with me that pkg-descr assumes you already know what
>> oleo is?  Or is it considered that people should read COMMENT in
>> Makefile as well?
>>
>> I was thinking of changing pkg-descr to:
>>
>> Oleo is a light-weight spreadsheet that'll work in almost any
>> environment.  Oleo features a curses based interface (character mode),
>> and also a LessTif (Motif) based graphical user interface.
>>
>> https://www.gnu.org/software/oleo/oleo.html
> 
> I think your proposal improves the port. Please, feel free to submit a PR.
> 

Actually, I was going to commit it myself, (except someone else just did
it for me).  I just wanted to solicit opinions first.
___
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"

math/oleo pkd-descr

[Montgomery-Smith, Stephen]

Dear Ports and people who recently modified the math/olea port,

Do people agree with me that pkg-descr assumes you already know what
oleo is?  Or is it considered that people should read COMMENT in
Makefile as well?

I was thinking of changing pkg-descr to:

Oleo is a light-weight spreadsheet that'll work in almost any
environment.  Oleo features a curses based interface (character mode),
and also a LessTif (Motif) based graphical user interface.

https://www.gnu.org/software/oleo/oleo.html
___
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: Help with cad/netgen port

[Montgomery-Smith, Stephen]

On 6/1/20 6:30 AM, Jan Beich wrote:
> "Montgomery-Smith, Stephen"  writes:
> 
>> I am the maintainer of the cad/netgen port, and I am having some
>> difficulties.  The fetch parts of Makefile is:
>>
>> PORTNAME=   netgen
>> PORTVERSION=6.2.2004
>> DISTVERSIONPREFIX=  v
>>
>> USE_GITHUB= yes
>> GH_ACCOUNT= NGSolve
>> GH_PROJECT= netgen:1 pybind11:2
>> GH_TAGNAME= v${PORTVERSION}:1 v2.4.3:2
>> GH_SUBDIR=  external_dependencies/pybind11:2
> 
> There's no need to assign :group to the default distfile. Also, it maybe
> easier to read if you convert pybind11 to GH_TUPLE.
> 
> USE_GITHUB=   yes
> GH_ACCOUNT=   NGSolve
> GH_TUPLE= NGSolve:pybind11:v2.4.3:pybind11/external_dependencies/pybind11
> ___

Thank you.
___
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"

Help with cad/netgen port

[Montgomery-Smith, Stephen]

I am the maintainer of the cad/netgen port, and I am having some
difficulties.  The fetch parts of Makefile is:

PORTNAME=   netgen
PORTVERSION=6.2.2004
DISTVERSIONPREFIX=  v

USE_GITHUB= yes
GH_ACCOUNT= NGSolve
GH_PROJECT= netgen:1 pybind11:2
GH_TAGNAME= v${PORTVERSION}:1 v2.4.3:2
GH_SUBDIR=  external_dependencies/pybind11:2

When I perform "make makesum", the file distinfo lists
NGSolve-netgen-v6.2.2004_GH0.tar.gz twice.  This makes "make fetch" fail
until I edit out one of these entries.

Did I configure Makefile incorrectly, or is this a bug with "make makesum"?

Thanks, Stephen
___
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: Ports from github

[Montgomery-Smith, Stephen]

On 5/24/20 3:49 AM, Matthew Seaman wrote:
> On 24/05/2020 03:39, Montgomery-Smith, Stephen wrote:
>> Is there a "howto" that explains how to build a port from a project that
>> is on github?  The FreeBSD porters handbook seems to assume a lot of
>> knowledge is already understood.
> 
> Well, the only thing "different" about porting something from Github, as
> opposed to any other distfile location, occurs in the 'fetch' phase --
> actually pulling down the distfiles.  Once you've got past that, the
> rest of building the port is exactly the same as it would be if you got
> the distfiles from anywhere else.
> 
> So, minimally a Github using port will set the following variables:
> 
> PORTNAME= someport
> PORTVERSION= 1.2.3
> DISTVERSIONPREFIX= v
> USE_GITHUB= yes
> GH_ACCOUNT= someone
> 
> and it won't set:
> 
> MASTER_SITES
> DISTFILES
> 
> An example from amongst the ports I maintain is database/pg_citus:
> 
> PORTNAME=   citus
> PORTVERSION=9.3.0
> DISTVERSIONPREFIX=  v
> 
> USE_GITHUB= yes
> GH_ACCOUNT= citusdata
> 
> From this, the ports can work out that the Github project is:
> 
>https://github.com/citusdata/citus/
>   ^
>   GH_ACCOUNT
> ^
> PORTNAME
> 
> If you go to that project URL and look at their releases page:
> 
>   https://github.com/citusdata/citus/releases
> 
> you'll see the list of versions like so:
> 
>   v9.3.0
>   ^ 
>   | PORTVERSION
>   DISTVERSIONPREFIX
> 
> That's all that is needed for this port to be able to download a tarball
> of the project's sources.
> 
> Now, this is about the simplest possible example of what you might need
> when pulling sources from Github, and this pattern probably accounts for
> the largest fraction of the Github-using ports in the tree.
> 
> Beyond that, the next largest fraction will be projects where the
> PORTNAME doesn't quite match the GH project URL, or their release tags
> specify the version as (eg.) v1_2_3 rather than v1.2.3 -- all just minor
> tweaks so the ports can put together the right URL to pull the distfiles
> from.
> 
> Beyond that is where it can start to get pretty complicated though.
> Sometimes a project doesn't create formal releases, or you want to pull
> down a code base a few commits beyond the latest release, or the project
> uses a lot of different sub-projects linked into its tree from other
> github repositories.  Certain programs written in go are pretty
> notorious for this, and can end up with huge lists of distfiles.  See
> www/gitlab-pages for an example.
> 
> Finally, and only if you really want to blow your mind: throw in an
> unreasonable number of port options to the mix.  www/nginx is the
> pinnacle (or is it nadir?) here.
> 
> In general I'd offer the following three pieces of advice when trying to
> get to grips with a new area in porting:
> 
>   * Find a good example of a port that does something similar and
> blatantly copy it[*].
>   * Keep things as simple as possible (but no simpler).
>   * Work iteratively: start with something close, and make simple
> minimal changes, one at a time and testing as you go, to get it spot
> on.
> 
> [*] The trick here is not to copy a port that does things sub-optimally.
>  Sods law has it that if there's a dozen good examples you might copy,
> and one bad one, it's the bad one that will seem like the most enticing
> prospect.
> 
> If in doubt, ask.  It helps if you can provide a concrete example or a
> specific context for your questions, and indeed, trying to formulate
> such a question will often lead you directly to the answer yourself.
> 
>   Cheers,
> 
>   Matthew

Thank you.  That really helped a lot.  I was able to figure it out from
this point.



signature.asc
Description: OpenPGP digital signature

Ports from github

[Montgomery-Smith, Stephen]

Is there a "howto" that explains how to build a port from a project that
is on github?  The FreeBSD porters handbook seems to assume a lot of
knowledge is already understood.
___
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"

cad/gmsh port

[Montgomery-Smith, Stephen]

On 2020-03-10 23:42, Wen Heping wrote:
> Author: wen
> Date: Wed Mar 11 04:42:16 2020
> New Revision: 528205
> URL: https://svnweb.freebsd.org/changeset/ports/528205
> 
> Log:
>- Update to 4.5.4

> Modified: head/cad/gmsh/distinfo
> ==
> --- head/cad/gmsh/distinfoWed Mar 11 03:22:11 2020(r528204)
> +++ head/cad/gmsh/distinfoWed Mar 11 04:42:16 2020(r528205)
> @@ -1,3 +1,3 @@
> -TIMESTAMP = 1556494401
> -SHA256 (gmsh/gmsh-4.3.0-source.tgz) = 
> 54a236f5708bc105d5b60ddb2b95ea7062537ccd2720860377994c1a9bb86429
> -SIZE (gmsh/gmsh-4.3.0-source.tgz) = 13102102
> +TIMESTAMP = 1583193832
> +SHA256 (gmsh/gmsh-4.5.4-source.tgz) = 
> ccf8c74f43cbe3c371abe79862025d41642b3538a0148f018949494e3b3e2ecd
> +SIZE (gmsh/gmsh-4.5.4-source.tgz) = 13524750

For some reason fetch freezes when the ports tries to build cad/gmsh. 
But if I download the tarball via my web browser, it works.  Any ideas why?
___
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: math/octave-forge-audio port

[Montgomery-Smith, Stephen]

Thank you very much!


From: Fernando Apesteguía 
Sent: Monday, January 20, 2020 1:55:03 PM
To: Montgomery-Smith, Stephen
Cc: FreeBSD Ports
Subject: Re: math/octave-forge-audio port

On Sun, Jan 19, 2020 at 10:57 PM Montgomery-Smith, Stephen
 wrote:
>
> I am the maintainer of the math/octave-forge-audio port.  I am getting
> multiple reports of build errors from pkg-fallout@.  But I am unable to
> reproduce these errors.  Configure claims it cannot find RTMIDI.  But it
> does preinstall the audio/rtmidi port from packages before it tries to
> build octave-forge-audio.
>
> What are other people's experiences with this port?  I should add it
> only came operational very recently.
>
> If anyone else if having the same build error, can they send me their
> copy of config.log, which can be found in work/audio-2.0.0/src?

Try USES=pkgconfig

Cheers
>
> Thanks, Stephen
> ___
> 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"

math/octave-forge-audio port

[Montgomery-Smith, Stephen]

I am the maintainer of the math/octave-forge-audio port.  I am getting
multiple reports of build errors from pkg-fallout@.  But I am unable to
reproduce these errors.  Configure claims it cannot find RTMIDI.  But it
does preinstall the audio/rtmidi port from packages before it tries to
build octave-forge-audio.

What are other people's experiences with this port?  I should add it
only came operational very recently.

If anyone else if having the same build error, can they send me their
copy of config.log, which can be found in work/audio-2.0.0/src?

Thanks, Stephen
___
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: XXX needs Python 3.4 at least, but 2.7 was specified

[Montgomery-Smith, Stephen]

On 12/25/19 10:49 AM, Franco Fichtner wrote:
> 
>> On 25. Dec 2019, at 12:59 PM, D'Arcy Cain  wrote:
>>
>> On 12/24/19 5:56 PM, w.schwarzenfeld wrote:
>>> At least a workaround (maybe the sollutiion):
>>>
>>>
>>> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209881&action=diff
>>
>> Another workaround if you don't want to modify files in the repo is to
>> simply go into the problem folder, /usr/ports/graphics/graphene in the
>> OP's case, and run "make install" before returning to the original
>> build.  You may have to do it multiple times for different packages though.
> 
> While Poudriere is nice and all and does this automagically it is a major
> annoyance trending lately that you cannot build ports without these silly
> build errors.  If USES= python: is used it doesn't mean ports should
> just barf all over users with these non-errors when they don't build deps
> with that particular version that one didn't even specify for the deps.
> 
> It seems like USES enforces this recursively but should not as witnessed
> by this "workaround".  There's still a relevant DEFAULT_VERSIONS entry
> but it is happily ignored.
> 
> If all users need to use Poudriere just to have a chance at building
> ports we're at the point where Poudriere itself is becoming problematic
> for port framework quality, something that always seemed to linger in
> the background for the last couple of years and now it's finally here.
> 
> And yes, lang/rust was one recent example that has python:3.3+ now and
> fails to build somewhere down the dependency chain.
> 
> 
> Cheers,
> Franco

I agree with Franco.  I am surprised that this error has been known for
so long, and not fixed, when at least one effective solution exists.

Stephen
___
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"

XXX needs Python 3.4 at least, but 2.7 was specified

[Montgomery-Smith, Stephen]

When I try to build certain ports, I get the error message "XXX needs
Python 3.4 at least, but 2.7 was specified."  Below I give an example
when I try to build the x11/mate port.  It gets this error when it tries
to build graphics/graphene as a dependency.  If I then go to
graphics/graphene and then try to build the port directly, it works just
fine.  Somehow the x11/mate port, or one of its dependencies, is saying
to use Python 3.x.  Somehow the graphene port should figure out it is
supposed to be using Python 2.x, but it seems it cannot figure this out
for itself.

Is anyone else having this problem?  I have had it a very long time,
predating the switch from defaults Python 2.x to Python 3.x.  My theory
is that this error doesn't come up if you use tools like portmaster or
poudriere, and that is why no-one has tried to fix it.  But maybe I have
something strange in my setup, and no-one else experiences it.

Example follows:

cd /usr/ports/x11/mate && make install clean

. snipped ..

===>   gstreamer1-plugins-gl-1.14.4_2 depends on shared library:
libgraphene-1.0.so - not found
===>  graphene-1.10.0 needs Python 3.4 at least, but 2.7 was specified.
*** Error code 1

Stop.
make[6]: stopped in /usr/ports/graphics/graphene
*** Error code 1

Stop.
make[5]: stopped in /usr/ports/graphics/gstreamer1-plugins-gl
*** Error code 1

Stop.
make[4]: stopped in /usr/ports/www/webkit2-gtk3
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/x11/yelp
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/misc/mate-user-guide
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/x11/mate-base
*** Error code 1

Stop.
make: stopped in /usr/ports/x11/mate
___
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"

Problem with portupgrade and py27-tkinter

[Montgomery-Smith, Stephen]

I have both py27-tkinter and py36-tkinter installed.  When I do 
portupgrade, it tries to upgrade py27-tkinter to py36-tkinter:

portupgrade -a
[Reading data from pkg(8) ... - 1061 packages found - done]
** Detected a package name change: py27-tkinter 
(x11-toolkits/py-tkinter) -> 'py36-tkinter' (x11-toolkits/py-tkinter)
--->  Upgrading 'py27-tkinter-2.7.16_6' to 'py36-tkinter-3.6.8_6' 
(x11-toolkits/py-tkinter)
etc, etc.
___
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"

Strange interaction between py-pyglet and py-numpy

[Montgomery-Smith, Stephen]

Using python2.7, if I run this code:

import numpy as np
from pyglet.gl import *

everything works fine.  But if I put the same code in the other order:

from pyglet.gl import *
import numpy as np

I get:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python2.7/site-packages/numpy/__init__.py", line
142, in 
from . import add_newdocs
  File "/usr/local/lib/python2.7/site-packages/numpy/add_newdocs.py",
line 13, in 
from numpy.lib import add_newdoc
  File "/usr/local/lib/python2.7/site-packages/numpy/lib/__init__.py",
line 8, in 
from .type_check import *
  File "/usr/local/lib/python2.7/site-packages/numpy/lib/type_check.py",
line 11, in 
import numpy.core.numeric as _nx
  File "/usr/local/lib/python2.7/site-packages/numpy/core/__init__.py",
line 26, in 
raise ImportError(msg)
ImportError:
Importing the multiarray numpy extension module failed.  Most
likely you are trying to import a failed build of numpy.
If you're working with a numpy git repo, try `git clean -xdf` (removes all
files not under version control).  Otherwise reinstall numpy.

Original error was: /lib/libgcc_s.so.1: version GCC_4.8.0 required by
/usr/local/lib/gcc7/libgfortran.so.4 not found


Any ideas?
___
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: FreeBSD Port: firefox-63.0.1,1 multiple errors build

[Montgomery-Smith, Stephen]

On 10/31/18 6:42 PM, Yuri Pankov wrote:
> Yuri Pankov wrote:
>> Montgomery-Smith, Stephen wrote:
>>> On 10/31/18 1:12 PM, Alex V. Petrov wrote:
>>> [lots of build errors snipped]
>>>
>>> I found that when I downgraded rust-cbindgen to 0.6.6_1 that this fixed
>>> the build problems.  So I suspect it is version 0.6.7 of rust-cbindgen
>>> that is causing the build errors.
>>
>> Fails for me even with 0.6.6_1.
> 
> And it built with rust-cbindgen-0.6.7, so I'm now wondering if it's not
> about the version, and has something to do with the fact that 0.6.6_1
> was installed using pkg, and update to 0.6.7 was done using ports.
> 
> 


I tried it again, this time building rust-cbindgen directly from ports
after a "pkg delete", rather than using portupgrade.  Then the build of
firefox worked.

I only started using portupgrade recently.  I find it rather unreliable.
 I think the problem is that some ports need to be deleted before they
can be built successfully.


___
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: FreeBSD Port: firefox-63.0.1,1 multiple errors build

[Montgomery-Smith, Stephen]

On 10/31/18 1:12 PM, Alex V. Petrov wrote:
[lots of build errors snipped]

I found that when I downgraded rust-cbindgen to 0.6.6_1 that this fixed
the build problems.  So I suspect it is version 0.6.7 of rust-cbindgen
that is causing the build errors.
___
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: Problems with make fetchindex on FreeBSD-10

[Montgomery-Smith, Stephen]

On 07/16/18 13:38, Montgomery-Smith, Stephen wrote:
> I get this error message if I do "make fetchindex" on FreeBSD-10.
> 
> Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's
> Encrypt Authority X3
> 675258712:error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
> failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1191:
> fetch: https://www.FreeBSD.org/ports/INDEX-10.bz2: Authentication error

FYI - this fixed it:

https://forums.freebsd.org/threads/freebsd-as-a-host-with-bhyve.60561/
___
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"

Problems with make fetchindex on FreeBSD-10

[Montgomery-Smith, Stephen]

I get this error message if I do "make fetchindex" on FreeBSD-10.

Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's 
Encrypt Authority X3
675258712:error:14090086:SSL 
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify 
failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1191:
fetch: https://www.FreeBSD.org/ports/INDEX-10.bz2: Authentication error

Is this an error at my end or yours?  I have been successfully doing 
"make fetchindex" for many years from this same computer.

Thanks, Stephen
___
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: Building math/octave with QT4?

[Montgomery-Smith, Stephen]

On 06/12/2018 04:20 PM, Steve Kargl wrote:
> On Tue, Jun 12, 2018 at 08:28:07PM +0000, Montgomery-Smith, Stephen wrote:
>>
>> Or if you just send him a request without a patch, he may get
>> around to it sometime.
> 
> This seems to work.
> 
> cd /usr/ports
> svn merge -r 469260:469259 .
> 

What exactly are you doing when this error occurs?  (The one you didn't
include in the snippet above?)  I never experienced it myself.
___
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: Building math/octave with QT4?

[Montgomery-Smith, Stephen]

Sorry for top posting, but I am using Outlook to reply.


You should really send this request to the maintainer, because he could have 
very easily overlooked this email.  He is step...@freebsd.org.


If you submit a PR with a patch, preferably one which uses options to let the 
user decide whether to use QT4 or QT5, I'm sure he attend to it quite quickly, 
although his life is currently a little full, so it probably won't be 
immediately.


Or if you just send him a request without a patch, he may get around to it 
sometime.


From: owner-freebsd-po...@freebsd.org  on 
behalf of Steve Kargl 
Sent: Tuesday, June 12, 2018 3:19:27 PM
To: freebsd-ports@freebsd.org
Subject: Building math/octave with QT4?

Is it possible to build math/octave with QT4?
The recent switch to require QT5 in r469260
leads to an unusable octave (unless one's
intention is to debug QT5).

% gdb81 
/usr/local/libexec/octave/4.4.0/exec/amd64-portbld-freebsd12.0/octave-gui 
octave-gui.core
> bt
#0  0x0002056b244d in QVariant::QVariant(QVariant const&) ()
   from /usr/local/lib/qt5/libQt5Core.so.5
[Current thread is 1 (LWP 101275)]
(gdb) bt
#0  0x0002056b244d in QVariant::QVariant(QVariant const&) ()
   from /usr/local/lib/qt5/libQt5Core.so.5
#1  0x000227c233c9 in ?? ()
   from /usr/local/lib/qt5/plugins/sqldrivers/libqsqlite.so
#2  0x000227c1eba2 in ?? ()
   from /usr/local/lib/qt5/plugins/sqldrivers/libqsqlite.so
#3  0x000205117351 in QSqlResult::execBatch(bool) ()
   from /usr/local/lib/qt5/libQt5Sql.so.5
#4  0x000203cf9ca2 in ?? () from /usr/local/lib/qt5/libQt5Help.so.5
#5  0x000203cfbd42 in ?? () from /usr/local/lib/qt5/libQt5Help.so.5
#6  0x0002054b24ea in ?? () from /usr/local/lib/qt5/libQt5Core.so.5
#7  0x000200d7e426 in thread_start (curthread=0x232679100)
at /usr/src/lib/libthr/thread/thr_create.c:291
#8  0x in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffbebf4000

--
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"

RE: Committer help needed with math/octave

[Montgomery-Smith, Stephen]

Let me do it.  I'm not at my FreeBSD computer right now, and I don't remember 
my committer password.

From: owner-freebsd-po...@freebsd.org [owner-freebsd-po...@freebsd.org] on 
behalf of Steve Kargl [s...@troutmask.apl.washington.edu]
Sent: Friday, February 23, 2018 11:37 AM
To: freebsd-ports@freebsd.org
Subject: Committer help needed with math/octave

Per Maho's request can someone please commit the patch at

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225073

Maho has also asked to be dropped as maintainer.

--
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"

Problem building mate port

[Montgomery-Smith, Stephen]

When I build straight from ports:
cd /usr/ports/x11/mate && make install clean

I get error messages like this:
===>  gnome-doc-utils-0.20.10_4 needs Python 2.7 at most, but 3.6 was
specified.
*** Error code 1

If I do this:
cd /usr/ports/textproc/gnome-doc-utils && make install
it works just fine.  So somehow, when textproc/gnome-doc-utils is built 
as a dependency of mate, the PYTHON variable is incorrectly set.

I had this same problem several months ago, so it is an old issue. 
Presumably most people build their ports using one of those scripts that 
build the dependency ports separately, and maybe this is why this 
problem hasn't been observed or fixed.

Thanks, Stephen
___
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: can't link against math.h

[Montgomery-Smith, Stephen]

On 10/25/2017 09:05 PM, blubee blubeeme wrote:
> I wrote a simple test program to test and see if math.h has the function:
> exp10f

> Does FreeBSD math.h have expf10 and if so, how do I link against it?
> ___

I think exp10f is a Linux only function.  In its man page, it says it is
a GNU extension.

http://man7.org/linux/man-pages/man3/exp10.3.html

I would implement it using the pow function, e.g.

#define exp10f(x) (powf(10.,x))
___
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: LICENSE questions

[Montgomery-Smith, Stephen]

On 10/04/2016 06:47 AM, Mathieu Arnold wrote:
> Le 04/10/2016 à 09:29, Eitan Adler a écrit :
>> On 4 October 2016 at 00:25, Mathieu Arnold  wrote:
>>> Le 04/10/2016 à 03:58, Montgomery-Smith, Stephen a écrit :
>>>> Could we use USES=metaport to suppress these messages?
>>> Suppress what messages ?
>> 115 .if defined(LICENSE)
>> 119 .else
>> 120 DEV_WARNING+=   "Please set LICENSE for this port"
>> 121 .endif
> 
> Mmmm, this is a warning, not an error, it tells you "dude, maybe you
> need to do this".
> I don't see a good reason to complicate the logic more.
> 

Because naive port maintainers like myself might think they should add a
LICENSE to any metaport they happen to own.

One of the issues I have with LICENSE is that I don't see anything about
it in the porters handbook.  Otherwise that would be an excellent place
to tell maintainers of metaports not to license them.

Also the tone is quite commanding.  If it said "Consider setting LICENSE
for this port", that would be more acceptable.  Really, I think it
should say "Please set LICENSE for this port, unless this is a metaport".

Stephen



signature.asc
Description: OpenPGP digital signature

Re: LICENSE questions

[Montgomery-Smith, Stephen]

On 10/03/2016 07:34 AM, Eitan Adler wrote:
> On 3 October 2016 at 05:31, Montgomery-Smith, Stephen
>  wrote:
>> On 10/02/2016 05:27 PM, Eitan Adler wrote:
>>> On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
>>>  wrote:
>>>> So I have a couple of ports, science/cdf and graphics/opendx, which have
>>>> licenses I can't find in Mk/bsd.licenses.db.mk.  How do I set LICENSE in
>>>> those ports?
>>>
>>> The other answers are correct. If the license is standard (listed
>>> here: https://spdx.org/licenses/) we should add it to the main
>>> database.
>>>
>>>> An even tougher one is math/octave-forge-optim, where each individual
>>>> file has its own license.
>>>
>>> A "custom" license that merely states to check the distfiles should be
>>> sufficient.
>>
>> How about a meta port, whose dependencies all have different licenses?
>> Something similar?
> 
> meta-ports shouldn't define a license at all. I'm not sure we have a
> way to shut the warnings up though.

Could we use USES=metaport to suppress these messages?
___
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: LICENSE questions

[Montgomery-Smith, Stephen]

On 10/02/2016 05:27 PM, Eitan Adler wrote:
> On 2 October 2016 at 14:44, Montgomery-Smith, Stephen
>  wrote:
>> So I have a couple of ports, science/cdf and graphics/opendx, which have
>> licenses I can't find in Mk/bsd.licenses.db.mk.  How do I set LICENSE in
>> those ports?
> 
> The other answers are correct. If the license is standard (listed
> here: https://spdx.org/licenses/) we should add it to the main
> database.
> 
>> An even tougher one is math/octave-forge-optim, where each individual
>> file has its own license.
> 
> A "custom" license that merely states to check the distfiles should be
> sufficient.

How about a meta port, whose dependencies all have different licenses?
Something similar?
___
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: What is SONAME in port builds?

[Montgomery-Smith, Stephen]

On 10/02/2016 10:29 AM, Montgomery-Smith, Stephen wrote:
> I am trying to build the port graphics/opendx, and at the qa stage it says:
> 
> Error: /usr/local/dx/bin_freebsd/builder is linked to
> /usr/local/lib/libcdf.so which does not have a SONAME.
> science/cdf needs to be fixed.
> 
> What does this mean, and how do I fix it?

I came up with "a" solution:

https://svnweb.freebsd.org/ports?view=revision&revision=423146
___
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"

LICENSE questions

[Montgomery-Smith, Stephen]

So I have a couple of ports, science/cdf and graphics/opendx, which have
licenses I can't find in Mk/bsd.licenses.db.mk.  How do I set LICENSE in
those ports?

An even tougher one is math/octave-forge-optim, where each individual
file has its own license.
___
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"

What is SONAME in port builds?

[Montgomery-Smith, Stephen]

I am trying to build the port graphics/opendx, and at the qa stage it says:

Error: /usr/local/dx/bin_freebsd/builder is linked to
/usr/local/lib/libcdf.so which does not have a SONAME.
science/cdf needs to be fixed.

What does this mean, and how do I fix it?

BTW I am maintainer of both ports.
___
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: math/open-axiom gone?

[Montgomery-Smith, Stephen]

On 07/25/2016 09:18 PM, cpghost wrote:
> Hello,
> 
> after updating my ports tree, I've found out that math/open-axiom
> has been deleted! After math/fricas unusable with sbcl-1.3.x for
> many months and now gone too, I'm left with NO alternatives for
> that kind of software here.
> 
> Fortunately, I still have a working package of open-axiom on my machine,
> running with SBCL 1.3.1 right now:
> 
> $ pkg version -v | grep open-axiom
> open-axiom-1.4.2_3 ?   orphaned: math/open-axiom
> 
> $ uname -a
> FreeBSD phenom.fritz.box 10.3-STABLE FreeBSD 10.3-STABLE #0 r303311: Mon Jul 
> 25 20:42:34 CEST 2016 r...@phenom.fritz.box:/usr/obj/usr/src/sys/GENERIC  
> amd64
> 
> $ open-axiom
>  OpenAxiom: The Open Scientific Computation Platform 
>   Version: OpenAxiom 1.4.2
>  Built on Friday June 19, 2015 at 22:28:27 
> -
>Issue )copyright to view copyright notices.
>Issue )summary for a summary of useful system commands.
>Issue )quit to leave OpenAxiom and return to shell.
> -
> 
> (1) -> )quit
> 
> $ sbcl
> This is SBCL 1.3.1, an implementation of ANSI Common Lisp.
> More information about SBCL is available at .
> 
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> * (sb-ext:exit)
> 
> Do you recommend to switch to Debian GNU/Linux, where those packages
> are still actively maintained, or is there a chance in hell to see
> those ports reappear in the near future on FreeBSD?
> 
> Thanks,
> -cpghost.
> 

How did you manage to build math/open-axiom?  I tried building it again,
and I am still getting the errors.  You must have at least by-passed the
BROKEN within the port.

Also, regarding your last comment, I must admit that I also find myself
moving to Linux.  For certain tasks it works better than FreeBSD,
probably because it has a much larger base of volunteers, and also
because most people who write open source do it on Linux.


___
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: How to make installation conditional in pkg-plist

[Montgomery-Smith, Stephen]

On 07/26/2016 12:13 PM, Thierry Thomas wrote:
> Le mar 26 jul 16 à 18:57:16 +0200, Montgomery-Smith, Stephen 
> 
>  écrivait :
> 
>> Currently the ports math/vtk6 and science/paraview both try to install 
>> the same file: share/cmake/hdf5/libhdf5.settings.  It is described in 
>> this bug report.
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211334
>>
>> My proposed solution is that each port only installs the file if it 
>> doesn't already exist, and only deinstalls the file if it installed it. 
>> I am planning to figure out some kind of @exec solution for the pkg-plist.
>>
>> Has anyone already solved this problem in other situations?  I prefer 
>> not to reinvent something if good solutions already exist.
>>
>> Failing that, does anyone have good ideas on how to do this, or even 
>> alternative solutions?
> 
> This file is already installed by the port science/hdf5, but under
> $PREFIX/lib.
> 
> I would suggest to:
> - modify science/hdf5 to create a symlink under share/cmake/hdf5
> - patch math/vtk6 and science/paraview to not install this file.
> 
> Regards,
> 

math/vtk6 doesn't call hdf5 as a dependency, since it uses it's own home
grown version.  science/paraview does have hdf5 as a dependency, but I
don't know if it actually needs it.

One possibility is to simply delete share/cmake/hdf5/libhdf5.settings
from the pkg-plist for math/vtk6.  What does itdo anyway?

Stephen



signature.asc
Description: OpenPGP digital signature

How to make installation conditional in pkg-plist

[Montgomery-Smith, Stephen]

Currently the ports math/vtk6 and science/paraview both try to install 
the same file: share/cmake/hdf5/libhdf5.settings.  It is described in 
this bug report.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211334

My proposed solution is that each port only installs the file if it 
doesn't already exist, and only deinstalls the file if it installed it. 
I am planning to figure out some kind of @exec solution for the pkg-plist.

Has anyone already solved this problem in other situations?  I prefer 
not to reinvent something if good solutions already exist.

Failing that, does anyone have good ideas on how to do this, or even 
alternative solutions?

Thanks, Stephen
___
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: math/open-axiom gone?

[Montgomery-Smith, Stephen]

On 07/25/2016 09:18 PM, cpghost wrote:
> Hello,
> 
> after updating my ports tree, I've found out that math/open-axiom
> has been deleted! After math/fricas unusable with sbcl-1.3.x for
> many months and now gone too, I'm left with NO alternatives for
> that kind of software here.
> 
> Fortunately, I still have a working package of open-axiom on my machine,
> running with SBCL 1.3.1 right now:
> 
> $ pkg version -v | grep open-axiom
> open-axiom-1.4.2_3 ?   orphaned: math/open-axiom
> 
> $ uname -a
> FreeBSD phenom.fritz.box 10.3-STABLE FreeBSD 10.3-STABLE #0 r303311: Mon Jul 
> 25 20:42:34 CEST 2016 r...@phenom.fritz.box:/usr/obj/usr/src/sys/GENERIC  
> amd64
> 
> $ open-axiom
>  OpenAxiom: The Open Scientific Computation Platform 
>   Version: OpenAxiom 1.4.2
>  Built on Friday June 19, 2015 at 22:28:27 
> -
>Issue )copyright to view copyright notices.
>Issue )summary for a summary of useful system commands.
>Issue )quit to leave OpenAxiom and return to shell.
> -
> 
> (1) -> )quit
> 
> $ sbcl
> This is SBCL 1.3.1, an implementation of ANSI Common Lisp.
> More information about SBCL is available at .
> 
> SBCL is free software, provided as is, with absolutely no warranty.
> It is mostly in the public domain; some portions are provided under
> BSD-style licenses.  See the CREDITS and COPYING files in the
> distribution for more information.
> * (sb-ext:exit)
> 
> Do you recommend to switch to Debian GNU/Linux, where those packages
> are still actively maintained, or is there a chance in hell to see
> those ports reappear in the near future on FreeBSD?
> 
> Thanks,
> -cpghost.
> 

Yes, there is definitely a "chance in hell" that I'll try to fix this.
(Please be nice to us volunteers, or at least don't curse us until we
have proven we deserve it.)

Can you submit this as a bug at
https://bugs.freebsd.org/bugzilla/enter_bug.cgi?  Then the problem
report is in a place where I'll remember to work on this in a few days
time when I have the time.

Right now I'm working on this:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211334.  I do
generally reply to bug reports in a reasonably timely manner.

I should add that I created these ports quite a while ago when I was
looking for free symbolic math packages.  Now I don't use them any more.
 So if you (or anyone else) would like to take over as maintainer of
these ports, that would be wonderful.

BTW, all I did is mark them broken.  But broken ports tend to get
deleted after a while.  So this is the first I knew about it.

Thanks,
Stephen
___
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"

Weird error from pkg-fallout

[Montgomery-Smith, Stephen]

I am getting messages from pkg-fallout saying that the port cad/gmsh
does not build.  See here:

http://beefy3.nyi.freebsd.org/data/head-i386-default/p416942_s301941/logs/gmsh-2.12.0.log

The main error it seems to report is this:
*** Bad machine code: Using an undefined physical register ***

Does this mean that cad/gmsh does not build on FreeBSD-CURRENT?  Or is
this error some strange mismatch created by a jailed environment?
___
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: Help with making a port C11 compliant

[Montgomery-Smith, Stephen]

On 05/06/2016 04:35 PM, Walter Schwarzenfeld wrote:
> Write in the Makefiles of math/cln and math/GiNaC
> 
> USE_GCC= 4.7
> (you can also use 4.8 or 5)
> and
> CXXFLAGS+=  -D_GLIBCXX_USE_C99
> 
> I have tested it with 4.7 and 5 in the port and with gcc5 with poudriere
> in a 93amd64 jail (the test with 4.7 is running in the moment).
> And it builds fine.

If the suggestion by Brooks Davis doesn't work, I'll give this a try.
But I will wrap it in a ".if ${OSVERSION} < 100".

Thanks, Stephen
___
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"

Help with making a port C11 compliant

[Montgomery-Smith, Stephen]

Here is my problem:
http://beefy2.nyi.freebsd.org/data/93amd64-default/414631/logs/GiNaC-1.7.0.log

the configure script says:
configure: error: Standard ISO C++ headers are missing

In the Makefile I have the line:
USES=   compiler:c++11-lang

Is there anything else I need to do?  I should add that seems to be a
FreeBSD-9 only problem - it builds fine on FreeBSD-10 and higher.

Thanks, Stephen
___
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: Is there an equivalent of NO_EXTRACT?

[Montgomery-Smith, Stephen]

I think EXTRACT_ONLY will do the equivalent of what you need.


From: owner-freebsd-po...@freebsd.org [owner-freebsd-po...@freebsd.org] on 
behalf of Piotr Kubaj [pku...@riseup.net]
Sent: Tuesday, September 08, 2015 4:44 PM
To: freebsd-ports@FreeBSD.org
Subject: Is there an equivalent of NO_EXTRACT?

I'm a maintainer of a few ports. For the next update I'm preparing, I
want to make it possible to download some addons via options. The thing
is, they are downloaded as-is. They are not meant to be extracted
(although they are zips), since it's the program itself that manages it.
Is there such a possibility?

___
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: /usr/ports/devel/py-gobject3: typo?

[Montgomery-Smith, Stephen]

On 09/16/14 11:40, Janos Dohanics wrote:
> Hello All,
>
> trying to build/install /usr/ports/devel/py-gobject3:
>
> # make install clean
> ===>  Installing for py27-gobject3-3.8.1_2
> ===>   py27-gobject3-3.8.1_2 depends on package: pygobject3-common>=0 - found
> ===>   py27-gobject3-3.8.1_2 depends on file: 
> /usr/local/libdata/pkgconfig/pycairo.pc - found
> ===>   py27-gobject3-3.8.1_2 depends on file: /usr/local/bin/python2.7 - found
> ===>   py27-gobject3-3.8.1_2 depends on executable: python2 - found
> ===>   py27-gobject3-3.8.1_2 depends on shared library: libffi.so - found 
> (/usr/local/lib/libffi.so.6) - found (/usr/local/lib/gcc47/libffi.so.4)
> ===>   py27-gobject3-3.8.1_2 depends on shared library: libglib-2.0.so - 
> found (/usr/local/lib/libglib-2.0.so.0)
> ===>   py27-gobject3-3.8.1_2 depends on shared library: libpcre.so - found 
> (/usr/local/lib/libpcre.so.3)
> ===>   py27-gobject3-3.8.1_2 depends on shared library: 
> libgirepository-1.0.so - found (/usr/local/lib/libgirepository-1.0.so.1)
> ===>  Checking if py27-gobject3 already installed
> ===>   Registering installation for py27-gobject3-3.8.1_2
> pkg-static: 
> lstat(/usr/ports/devel/py-gobject3/work/stage/usr/local/lib/python2.7/site-packages/pygobject-3.8.1-py2.7-freebsd-10.1-BETA1-amd64.egg-info):
>  No such file or directory
> *** Error code 74
>
> Stop.
> make: stopped in /usr/ports/devel/py-gobject3
>
> In 
> /usr/ports/devel/py-gobject3/work/stage/usr/local/lib/python2.7/site-packages/
> I have:
>
> pygobject-3.8.1-pypython2.7-freebsd-10.1-BETA1-amd64.egg-info but not
> pygobject-3.8.1-py2.7-freebsd-10.1-BETA1-amd64.egg-info
>
> Seems like 'cp
> pygobject-3.8.1-pypython2.7-freebsd-10.1-BETA1-amd64.egg-info
> pygobject-3.8.1-py2.7-freebsd-10.1-BETA1-amd64.egg-info' fixes the
> problem.
>
> Just a typo?
>

I just experienced the same problem.  Any plans to fix it?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ports-mgmt/pkg

[Montgomery-Smith, Stephen]

On 08/05/2014 12:23 PM, Montgomery-Smith, Stephen wrote:
> I tried version pkg-1.3.4 yesterday.  When I used pkg install to install
> a preexisting package which had lots of dependencies, I would get lines
> like this:
> 
> package-y: 100%
> package-y: 100%
> package-y: 100%
> 
> This might be when installing package-x.  That is, a dependency might be
> listed up to three times, and in some cases even the base package would
> never get listed.  I was assuming that the code that printed which
> package was being installed was sometimes getting it wrong.  In one
> case, when I was installing texlive-full, the package t1lib was listed
> twice, but the second time it installed it went so slowly that it must
> have been installing texlive-texmf.
> 
> Obviously this is only a cosmetic problem.  But I am curious as to
> whether people are aware of this issue.

This bug is still present in pkg-1.3.5.1.  However it arises when I used
pkg add - not when using pkg install.  Sorry for my mistake.

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

ports-mgmt/pkg

[Montgomery-Smith, Stephen]

I tried version pkg-1.3.4 yesterday.  When I used pkg install to install
a preexisting package which had lots of dependencies, I would get lines
like this:

package-y: 100%
package-y: 100%
package-y: 100%

This might be when installing package-x.  That is, a dependency might be
listed up to three times, and in some cases even the base package would
never get listed.  I was assuming that the code that printed which
package was being installed was sometimes getting it wrong.  In one
case, when I was installing texlive-full, the package t1lib was listed
twice, but the second time it installed it went so slowly that it must
have been installing texlive-texmf.

Obviously this is only a cosmetic problem.  But I am curious as to
whether people are aware of this issue.

BTW - I really like the real-time counter that tells you what percentage
of a package is installed or deinstalled.

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

Re: Bugzilla issue

[Montgomery-Smith, Stephen]

On 07/24/2014 11:15 PM, Kurt Jaeger wrote:
> Hi!
> 
>> I can only see the patch to Makefile.  I don't see any patch that
>> creates files/patch-configure.
>>
>> And look at patch 144957.  It is completely empty.  But it should have
>> contained:
> 
> Ah, you use the bugzilla diff view. There's already a bug for that problem:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190724
> 
> So it's only a display issue if you use the diff view, the attachment
> itself is fine.
> 

Thank you.  I see that now.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Bugzilla issue

[Montgomery-Smith, Stephen]

On 07/24/2014 10:59 PM, Kurt Jaeger wrote:
> Hi!
> 
>> I am posting to freebsd-ports, but that probably isn't the right place.
>>
>> I was trying to post a patch to bug 192074.  I gave it the patch I
>> attached.  But for some reason, bugzilla couldn't handle the patch to
>> patch-configure.  This patch was created using "svn diff".  Bugzilla
>> didn't want to accept a patch that was against an empty or non-existent
>> file.
> 
> I checked attachment 144956 and it was fine ? What was your
> problem with it ?
> 


I can only see the patch to Makefile.  I don't see any patch that
creates files/patch-configure.

And look at patch 144957.  It is completely empty.  But it should have
contained:

Index: files/patch-configure
===
--- files/patch-configure   (revision 0)
+++ files/patch-configure   (working copy)
@@ -0,0 +1,14 @@
+--- configure-orig 2014-07-24 20:42:11.0 -0500
 configure  2014-07-24 20:43:21.0 -0500
+@@ -15361,9 +15361,9 @@
+ ffmpegon=false
+ # Check whether --enable-ffmpeg was given.
+ if test "${enable_ffmpeg+set}" = set; then :
+-  enableval=$enable_ffmpeg; FFMPEG_INCLUDES="-DFFMPEG
-D__STDC_CONSTANT_MACROS"
++  enableval=$enable_ffmpeg;
FFMPEG_INCLUDES="-I%%LOCALBASE%%/include/ffmpeg0 -DFFMPEG
-D__STDC_CONSTANT_MACROS"
+
+-FFMPEG_LIBS="-lavutil -lavformat -lavcodec -lavutil -lswscale
-lz -lbz2"
++FFMPEG_LIBS="-L%%LOCALBASE%%/lib/ffmpeg0 -lavutil0 -lavformat0
-lavcodec0 -lavutil0 -lswscale -lz -lbz2"
+
+ if test "$enableval" = yes; then ffmpegon=true; else
ffmpegon=false; fi
+
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Bugzilla issue

[Montgomery-Smith, Stephen]

I am posting to freebsd-ports, but that probably isn't the right place.

I was trying to post a patch to bug 192074.  I gave it the patch I
attached.  But for some reason, bugzilla couldn't handle the patch to
patch-configure.  This patch was created using "svn diff".  Bugzilla
didn't want to accept a patch that was against an empty or non-existent
file.

Index: Makefile
===
--- Makefile(revision 362293)
+++ Makefile(working copy)
@@ -41,7 +41,7 @@
 .endif
 
 .if ${PORT_OPTIONS:MFFMPEG}
-LIB_DEPENDS+=  libavcodec.so:${PORTSDIR}/multimedia/ffmpeg
+LIB_DEPENDS+=  libavcodec0.so:${PORTSDIR}/multimedia/ffmpeg0
 CONFIGURE_ARGS+=   --enable-ffmpeg
 .endif
 
@@ -58,6 +58,10 @@
${REINPLACE_CMD} -e "s|%%DATADIR%%|${DATADIR}|" \
${WRKSRC}/ng/ngappinit.cpp
 
+post-configure:
+   ${REINPLACE_CMD} -e "s|%%LOCALBASE%%|${LOCALBASE}|" \
+   ${WRKSRC}/configure
+
 post-install:
 #  copy some additional headers for build cad/salome-netgenplugin
${MKDIR} ${STAGEDIR}${DATADIR}/include
Index: files/patch-configure
===
--- files/patch-configure   (revision 0)
+++ files/patch-configure   (working copy)
@@ -0,0 +1,14 @@
+--- configure-orig 2014-07-24 20:42:11.0 -0500
 configure  2014-07-24 20:43:21.0 -0500
+@@ -15361,9 +15361,9 @@
+ ffmpegon=false
+ # Check whether --enable-ffmpeg was given.
+ if test "${enable_ffmpeg+set}" = set; then :
+-  enableval=$enable_ffmpeg; FFMPEG_INCLUDES="-DFFMPEG 
-D__STDC_CONSTANT_MACROS"
++  enableval=$enable_ffmpeg; FFMPEG_INCLUDES="-I%%LOCALBASE%%/include/ffmpeg0 
-DFFMPEG -D__STDC_CONSTANT_MACROS"
+ 
+-FFMPEG_LIBS="-lavutil -lavformat -lavcodec -lavutil -lswscale -lz 
-lbz2"
++FFMPEG_LIBS="-L%%LOCALBASE%%/lib/ffmpeg0 -lavutil0 -lavformat0 
-lavcodec0 -lavutil0 -lswscale -lz -lbz2"
+ 
+ if test "$enableval" = yes; then ffmpegon=true; else ffmpegon=false; 
fi
+ 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg 2 ng conversion

[Montgomery-Smith, Stephen]

On 06/08/2014 02:25 PM, Jim Pazarena wrote:
> On 2014-06-08 10:55 AM, Warren Block wrote:
>> On Sun, 8 Jun 2014, Jim Pazarena wrote:
>>
>>
>> No.  pkg is just a package manager.  It does not replace ports, it just
>> handles packages.  Like the old package manager, binary packages can be
>> downloaded and installed rather than ports, but the choice is yours.
> 
> Ahh.. therein lies the confusion. I have been compiling ports for many
> years. However the compilations began nagging about converting pkg2ng.
> So I investigated, and set the appropriate "WITH_PKGNG=yes" and ran
> pkg2ng. But I never use packages. I always compile from ports.
> 
> So the warning appearing in each and every compile was & is very
> misleading. Unless I am *still* confused !!

I still think you are confused.  pkg manages the database that stores
which ports/packages are installed on your system.  Whether that
particular piece of software came from building it using a port, or from
downloading a binary package is immaterial.

I think part of the confusion comes from the double use of the words
package and/or port.  When you have, say, xorg-7.7 installed on your
system, do you say you have the port xorg installed, or the package xorg
installed?  Once it is installed it doesn't matter where it came from -
port or package.  For whatever reason, people tend to call it a package
once it is installed, even if it came from a port.

For example, when you write "pkg info" in the new system, or "pkg_info"
in the old system, it reads the database to tell you the list of
packages/ports installed.  Now "pkg_info" and "pkg" assume a very
different structure for the database.  That is why, if you have
installed any ports or packages using the old system, you have to run
pkg2ng.  It converts the database from one form to the other.  And that
is why if you are using FreeBSD-9 or an older system, you have to add
"WITH_PKGNG=yes" to make.conf, so that when more ports/packages are
installed, it will update the new database and not the old.

Why did the change the database structure?  The old way had a separate
directory for each port/package built.  The new way is to use a modern
relational database.  So one advantage is the the new pkg database is
much faster.  Maybe there are other advantages too.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/29/2014 08:37 PM, Montgomery-Smith, Stephen wrote:
> I think I have some good news about the math/sage port.  On a whim,
> I tried replacing the python-2.7.5 source code that comes with sage
> to the python-2.7.6 source code that comes with the lang/python27
> port. And the build on FreeBSD-10 completed!!!
> 
> It will probably be rather hard to automate this process in
> math/sage port.  Before I do that, I'll see if I can persuade the
> sage people to make this change upstream.

It turned out much easier to automate than I thought.  I just
committed the changes in revision 355933.

Also, it is very likely that python-2.7.6 will be part of sage-6.3.
The sage people started working on this a few weeks ago.

Please report back to me if you find success or failure.

Stephen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTiWTJAAoJEC3xK9GaktgHvx8H/jwc6np5hDPTeoYBAAnaG+d5
4BXAuc7EtS5Z/qTHMeuXS6g67pJp2rkPiI4hQ0V+/VfSFFGGkDIaTTGlCnSjJ12G
U5GNPGhowYkvLiaA5eVw+t/Fqz1kDw9S+cI9WNEROawf3RkecP7h3M96OTmm0aH/
PEUTLbY9GkVNwLr4/6XsphSn2TO0xAIvX+Fgw+RWQKd2OEZEckLulHSixeeEC6vk
J1+1C9L6OQEMu1zwpjaJQfkEq4NyrdtmIkSIydS77LNeH29lKH4MFnSLFj5DgX4h
EWoplyaGk5fOZ1r3mT46wbtNdQlZnfqVf9bWyS08yKVRwJcEYDlXJ3irsPrUrrM=
=+10V
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I think I have some good news about the math/sage port.  On a whim, I
tried replacing the python-2.7.5 source code that comes with sage to
the python-2.7.6 source code that comes with the lang/python27 port.
And the build on FreeBSD-10 completed!!!

It will probably be rather hard to automate this process in math/sage
port.  Before I do that, I'll see if I can persuade the sage people to
make this change upstream.

But this is a very hopeful sign of things to come.

If anyone wants to build the math/sage port right away, I can probably
provide instructions on how to carry out the process.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTh+DmAAoJEC3xK9GaktgHY68H+wQy4/k0wEgaajo7VuRXcvG2
FOorzi4/oxDYd+NyrKDrkQVoBCq721kSaF2BoHTYcDtL6do8hsKwSljcuqqFdMTt
llWL4bGbmOiB3toG3ky96lqCewtcO+2kvxkXbWUilh7liaIVXQCXDVKAPZiq5UxJ
MkMdeJk8OIrVJE1VGDolF46Evp1SWYsWUTfqHgSiyIdvnVKKz1mGfxSDAUT2f99T
xYt1CW8jxHPe04OhYY5Ow6ujD3e9eQwHPFYrKEH3TAAKmRcAr9iM72ezUoRmQQZT
gTS6BRfe2sV6U2r9paQOUmzoFKatpRp77GJlh9jEMGbQHdlL0nJC8d3yLfHf6lM=
=C2rK
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: clang problems with math/octave-forge-miscellaneous

[Montgomery-Smith, Stephen]

On 05/17/2014 12:40 PM, Tijl Coosemans wrote:
> On Sat, 17 May 2014 17:13:51 +0000 Montgomery-Smith, Stephen wrote:
>> On 05/17/2014 12:00 PM, Montgomery-Smith, Stephen wrote:
>>> I am trying to make the port math/octave-forge-miscellaneous clang
>>> compliant.  In the file ${WRKSRC}/partarray.cc is are lines like this:
>>>
>>>   Array bidc [maxdims], eidc [maxdims];
>>>   ... stuff ...
>>>   eidc[i] = eidx;
>>>
>>> The compilation dies saying that eidc is not defined.
>>
>> I see the problem.  The compiler actually goes wrong with
>>
>>   Array bidc [maxdims];
>>
>> saying
>>
>> partarray.cc:42:31: error: variable length array of non-POD element type
>>   'Array'
>>
>> So the error is somewhere else.  Sorry for the noise.  But if I don't
>> figure out the latter error, I'll be back with more questions.
> 
> You'll have to declare it as "Array *bidc" and
> use new[] and delete[].

Thank you, thank you, thank you.  That fixed it!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: clang problems with math/octave-forge-miscellaneous

[Montgomery-Smith, Stephen]

On 05/17/2014 12:00 PM, Montgomery-Smith, Stephen wrote:
> I am trying to make the port math/octave-forge-miscellaneous clang
> compliant.  In the file ${WRKSRC}/partarray.cc is are lines like this:
> 
>   Array bidc [maxdims], eidc [maxdims];
>   ... stuff ...
>   eidc[i] = eidx;
> 
> The compilation dies saying that eidc is not defined.

I see the problem.  The compiler actually goes wrong with

  Array bidc [maxdims];

saying

partarray.cc:42:31: error: variable length array of non-POD element type
  'Array'

So the error is somewhere else.  Sorry for the noise.  But if I don't
figure out the latter error, I'll be back with more questions.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 05/17/2014 08:04 AM, Dimitry Andric wrote:
> On 17 May 2014, at 04:26, Montgomery-Smith, Stephen
>  wrote:
>> I have started to think about making sage compatible with
>> FreeBSD-10. The main problem thus far is that clang's c++
>> compiler is missing some stuff like the include file
>> ext/numeric.
> 
> That header is not missing, it became standardized, so use
>  instead.  The libstdc++ developers added a bunch of
> upcoming things into the ext/ and tr1/ subdirectories in the past,
> but there is really no need to use these anymore, these days.

Thank you.  In that case I'll work on getting sage to work with clang.
 I'll ask C++ questions as they arise.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTd5YQAAoJEC3xK9GaktgH3JUH/138LvkGfTBketWYBKbVSThv
sJ3tJQ7TZ2xQnq0WEZXylGCUIl6kgSERNQnvn1zBqxnHiYAFx/c1C6H4WiI6qyBl
rrrUcHwr23k9torEACIt/Se8QyZaquyDzqqQAlTrZXj0uRIeIAMepZo9wAQpCc6U
p/UvKUAQaXftctm+1LOmUiyyxiscbEfMcQzz3xN6mVeaso/fLoFoFly9rfwC4KcP
/7ZghXIWqwP8guT9ZAvg7uAQXYbrpLhzYfWLjwoB91JggcvBp/grTWHo0EvSj8eq
HZ5lcDPumJqZ3JjCQHp5BVC7fvb7p/ejvGb5psg+mBdY7xtLIjMUJsqEEc6wRws=
=3a5v
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

clang problems with math/octave-forge-miscellaneous

[Montgomery-Smith, Stephen]

I am trying to make the port math/octave-forge-miscellaneous clang
compliant.  In the file ${WRKSRC}/partarray.cc is are lines like this:

  Array bidc [maxdims], eidc [maxdims];
  ... stuff ...
  eidc[i] = eidx;

The compilation dies saying that eidc is not defined.  If I rewrite the
first line as

  Array bidc [maxdims];
  Array eidc [maxdims];

then it compiles just fine.

Is this a bug in the clang C++ compiler, or am I misunderstanding
something about C++?

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

Re: Sage update

[Montgomery-Smith, Stephen]

Hey people,

I have started to think about making sage compatible with FreeBSD-10.
The main problem thus far is that clang's c++ compiler is missing some
stuff like the include file ext/numeric.

I don't know if clang's c++ compiler is far behind gcc-4.7, or whether
it is a question of merely copying a few include files from gcc-4.7.

I just committed a change to the sage port (revision 354274) where if
you want to see if it compiles with clang, just comment out the
USE_GCC=yes line in the Makefile.

One subpackage that breaks fairly early on is ratpoints.  It has a
function defined inside of another function.  If anyone is interested I
can send them my patch to fix this.  But you will find other subpackages
that break as well because it is not able to find include files.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: math/sage error log message

[Montgomery-Smith, Stephen]

On 05/14/2014 02:36 PM, Bruce wrote:
> At this time I get the same error at the same place.  I have had sage on
> this computer before freebsd-9.2 and haven't been able to build it
> since.  Every time I notice a change in the sage port I try again.  I
> have tried about 4 times in the last week.  Before the last Makefile
> change in the port it got a lot farther and the error was during the
> building of the html documentation.
> I have tried MAKE_JOBS_UNSAFE and it gets farther.
> 
> I am using a Shuttle xpc with amd 64 and freebsd-9.2
> 
> uname -a FreeBSD 192.168.1.4 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898:
> Thu Sep 26 22:50:31 UTC 2013
> r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> Thanks for your help.

All the recent changes to the Makefile have been essentially cosmetic.
THe only change that might be at work is that I removed the
"NO_STAGE=yes" line.  That might have introduced some environment
variables that created the crash.  But it seems very unlikely.

Did you upgrade FreeBSD or other ports in the mean time?  Or maybe you
are using an old and buggy gcc47?

I should add that no-one has been able to get sage to build if the base
compiler is clang.  So updating to FreeBSD-10 will only make things
worse.  I am still using FreeBSD-8.

When you run it with MAKE_JOBS_UNSAFE, what error does it stop with?
Ironically it may not be getting as far.  When MAKE_JOBS_UNSAFE is not
set, it tries to build the subpackages in parallel.  So if it breaks on
more than one package, it is a bit random which package will cause the
break.

However, if you got as far as building the documentation, then the build
of the sage binaries is complete.  And then you can use sage to your
hearts content and get the docs using google.

In the meantime, I am looking into getting sage 6.2 working.  But that
is also giving me many problems.

Also, when replying, try to make sure that you send it to
step...@freebsd.org.  If you send it to step...@missouri.edu, it will
not get separated from all the other email I get from the FreeBSD
project, and I might not see it.  You are free to send it to both of
these email addresses, but make sure the step...@freebsd.org email
address is included.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: math/sage error log message

[Montgomery-Smith, Stephen]

On 05/13/2014 07:17 PM, Bruce wrote:

> -Wl,-rpath=/usr/local/lib/gcc47 -g -fPIC -c linbox-sage.C  -fPIC -DPIC
> -o .libs/linbox-sage.o
> {standard input}: Assembler messages:
> {standard input}:669830: Warning: end of file not at end of a line;
> newline inserted
> {standard input}:670930: Error: unknown pseudo-op: `.lvl719'
> {standard input}: Error: open CFI at the end of file; missing
> .cfi_endproc directive
> g++47: internal compiler error: Killed: 9 (program cc1plus)
> Please submit a full bug report,
> with preprocessed source if appropriate.
> .

What a horrible error!  Do you get the error in the same place every
time you try to compile sage?

It might be a hardware error, or maybe the compiler is running out of
memory.  Did you try building it with MAKE_JOBS_UNSAFE set?  How many
cores do you have on your processor?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: math/sage compile error

[Montgomery-Smith, Stephen]

On 05/13/2014 05:55 PM, Bruce wrote:
> Error on amd freebsd-9.2
> 
> Error building Sage.
> 
> The following package(s) may have failed to build:
> 
> package: linbox-1.3.2.p0
> log file:
> /usr/ports/math/sage/work/sage-6.1.1/logs/pkgs/linbox-1.3.2.p0.log
> build directory:
> /usr/ports/math/sage/work/sage-6.1.1/local/var/tmp/sage/build/linbox-1.3.2.p0
> 
> 
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
> 
> gmake: *** [build] Error 1
> *** [do-build] Error code 1
> 
> Stop in /usr/ports/math/sage.
> *** [stage] Error code 1
> 
> Stop in /usr/ports/math/sage.

Hi Bruce,

I am the maintainer of math/sage.  But I think I am missing all your
messages, because there are too many emails sent to freebsd-ports.  Can
you CC me as "step...@freebsd.org" on these emails?  Then we can start a
dialogue and figure out if I can solve your problem.

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

Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.

[Montgomery-Smith, Stephen]

On 05/11/2014 03:22 AM, John Marino wrote:
> On 5/11/2014 04:02, Montgomery-Smith, Stephen wrote:
>> On 05/10/2014 08:48 PM, Jonathan Chen wrote:
>>> On 11 May 2014 03:33, Bryan Drewery  wrote:
>>> [...]

>> I have noticed that "make all" now includes the staging as well as
>> building.  That is to say, it looks like there is a rather wholesale
>> reordering of how ports build and install.  From this I conclude it is
>> becoming harder to include the legacy NO_STAGE code, which presumably
>> must stick to the old way of doing things.
> 
> I don't understand this paragraph.  I never use "make all" at the ports
> level.  "make install" will do 2 steps: install into the staging area
> and then install onto the system.  If you just want to install in the
> staging area, you use "make stage" target.  By definition "all" is do
> everything, so that's not a surprise that's not a surprise.  Maybe stop
> using "all"?  A lone "make" is equivalent to "make build", so just use
> that perhaps?

When you type "make" by itself, you are implicitly meaning "make all".
(You can see this by looking at bsd.port.mk.)

It used to be that when you typed "make", it would build the sources.
Then "make install" would create a staging area, and then directly copy
the staged stuff it to ${PREFIX}.

But now, when you type "make", it builds the source, AND installs the
stuff into the staging area.  All "make install" does is copy the staged
stuff to ${PREFIX}.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.

[Montgomery-Smith, Stephen]

On 05/10/2014 08:48 PM, Jonathan Chen wrote:
> On 11 May 2014 03:33, Bryan Drewery  wrote:
> [...]
>> So we will be DEPRECATING and resetting maintainer on all unstaged ports
>> on June 31st.
>>
>> These ports will be set to EXPIRE on August 31st and will then be
>> removed from the tree. They will not be restored unless someone stages
>> them as well.
> 
> The problem I have with this decision is that there are some complex
> ports which have no single maintainer (case in point: eclipse-devel);
> and whose patch-submitters only occasionally dabble with the port.
> Staging support for these ports sometimes tend to be over-complex, and
> one that yield no immediate benefit to the submitter.
> 
> And then there are the ports which have their have their home-baked
> installer, where adding staging support could mean wholesale changes
> to the port.
> 
> It used to be the philosophy of FreeBSD to favour pragmatism over
> ideology. I must admit to some disappointment over this decision to
> force staging as the "one true way".

I have noticed that "make all" now includes the staging as well as
building.  That is to say, it looks like there is a rather wholesale
reordering of how ports build and install.  From this I conclude it is
becoming harder to include the legacy NO_STAGE code, which presumably
must stick to the old way of doing things.

Of course I might be wrong.  But if I am right, then it will become
increasingly difficult to allow unstaged ports.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Problems with libtool and graphics/opendx; was: To all port maintainers: libtool

[Montgomery-Smith, Stephen]

On 05/10/2014 03:22 PM, Montgomery-Smith, Stephen wrote:
> I am trying to get the libtool changes to work with the port
> graphics/opendx.

> ..

> When I do "find . -name "libDX.*"", I get
> ./work/dx-4.4.4/src/exec/.libs/libDX.lai
> ./work/dx-4.4.4/src/exec/.libs/libDX.a
> ./work/dx-4.4.4/src/exec/.libs/libDX.la
> ./work/dx-4.4.4/src/exec/libDX.la
> ./work/stage/usr/local/dx/lib_freebsd/libDX.a
> suggesting that the "*.so" files were never created.
> 
> Did I miss something?
> 
> The modifiers :keepla and :oldver don't seem to help.

I have decided I'm not going to worry about this, since it looks like no
other port uses these dynamic libraries.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Problems with libtool and graphics/opendx; was: To all port maintainers: libtool

[Montgomery-Smith, Stephen]

I am trying to get the libtool changes to work with the port
graphics/opendx.  I made the changes:

Index: Makefile
===
--- Makefile(revision 353598)
+++ Makefile(working copy)
@@ -16,10 +16,11 @@
cdf:${PORTSDIR}/science/cdf

 USE_XORG=  xinerama xext xpm xmu sm ice
-USES=  bison motif gmake
+USES=  bison motif gmake libtool
 USE_GCC=   any
 USE_GL=yes
-USE_AUTOTOOLS= libtool
+GNU_CONFIGURE= yes
+#USE_AUTOTOOLS=libtool
 USE_LDCONFIG=  yes
 CFLAGS+=   ${PTHREAD_CFLAGS}
 CONFIGURE_ENV= ARCH=freebsd

Then when I do "make install" I got
pkg-static:
lstat(/usr/ports/graphics/opendx/work/stage/usr/local/dx/lib_freebsd/libDX.la):
No such file or directory
pkg-static:
lstat(/usr/ports/graphics/opendx/work/stage/usr/local/dx/lib_freebsd/libDX.so):
No such file or directory
pkg-static:
lstat(/usr/ports/graphics/opendx/work/stage/usr/local/dx/lib_freebsd/libDX.so.4):
No such file or directory
etc.

When I do "find . -name "libDX.*"", I get
./work/dx-4.4.4/src/exec/.libs/libDX.lai
./work/dx-4.4.4/src/exec/.libs/libDX.a
./work/dx-4.4.4/src/exec/.libs/libDX.la
./work/dx-4.4.4/src/exec/libDX.la
./work/stage/usr/local/dx/lib_freebsd/libDX.a
suggesting that the "*.so" files were never created.

Did I miss something?

The modifiers :keepla and :oldver don't seem to help.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: replacing gcc with clang

[Montgomery-Smith, Stephen]

On 04/21/2014 04:58 AM, Mathieu Arnold wrote:
> +--On 20 avril 2014 20:10:39 -0400 Robert Huff  wrote:
> | Is there a authoritative list of those ports know to not build with
> | clang 3.2/3.4?
> 
> No, but you can grep for USE_GCC in the ports tree to find that out.
> 

Maybe you need to grep for "fortran" as well.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: fr-med-3.0.6_3

[Montgomery-Smith, Stephen]

On 03/16/2014 05:03 AM, Tuomo Latto wrote:
> Any chance of getting fr-med updated?
> It seems the newer stable version of aster contains
> med 3.0.7 package and the old aster version is no
> longer available.
> I'm asking because not only does the octave-forge
> optional package octave-forge-msh require fr-med but the
> non-optional octave-forge-bim requires it as well.
> So, as far as I can tell octave-forge is currently
> broken because of this.
> 

octave-forge-bim is brought in as a dependency on other packages - I
think they are octave-forge-sec1d and octave-forge-sec3d.  So switch off
those packages as well, and octave-forge should build just fine.

(Really, you need to go through a process of trial and error to see
which packages are brought in as dependencies of other packages.)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

french/med broken

[Montgomery-Smith, Stephen]

When I try to build french/med, I get the error message:

===>  fr-med-3.0.6_3 is marked as broken: Unfetchable.

But I don't see what code in the Makefile generates this message.  Is
there some code in /usr/ports/Mk/ that autogenerates this message?

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

Re: annoying pkg-fallout notices, how can I stop it?

[Montgomery-Smith, Stephen]

On 03/12/2014 08:27 AM, Koichiro IWAO wrote:
> On Wed, Mar 12, 2014 at 02:12:21PM +0100, John Marino wrote:
>> You get the idea.
>> You fixed head, you didn't fix the quarterly branches.
>> How you can stop it?
>> MFC your fix to quarterly branch.
> 
> OK, I was blind. Very similar question has been posted hours ago.
> Then, how do I request merge from head to the branch? May I ask you to
> do that via this e-mail or should I send-pr? or other way?
> 

I am just going to ignore emails from pkg-fallout that have "-quarterly"
in their subject line.  I don't really see the point of fixing the
stable branches, since I pressume they are just a snapshot of ports at
the time when the corresponding release of src came out.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: What's up with pkg-fallout?

[Montgomery-Smith, Stephen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/12/2014 06:43 AM, Baptiste Daroussin wrote:
> On Wed, Mar 12, 2014 at 01:49:39AM +0000, Montgomery-Smith, Stephen
> wrote:
>> I keep getting emails from pkg-fallout@ that some of my ports
>> are faulty.  But it is obvious that pkg-fallout sometimes uses a
>> really old ports trees.  And the errors it is reporting have been
>> fixed weeks ago. ___ 
>> freebsd-ports@freebsd.org mailing list 
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports To
>> unsubscribe, send any mail to
>> "freebsd-ports-unsubscr...@freebsd.org"
> 
> That is the stable branch, we now have a stable branch, I'm pretty
> sure the old ports from which you get a pkg-fallout mails are the
> -quarterly build.

That makes sense.  And now that I look at the email headers, it does
say "-quarterly" in them.  I'll have to remember to ignore the
"-quarterly" emails from pkg-fallout@.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTIFizAAoJEC3xK9GaktgHri4H/0ulAy6Ib26G0KdMA7ZsuPsw
jPK6fDXachPo7290fgh+/+upbdvUWuzywCzGtFpwq+LRJR1fPwo/d06DHG4FftRg
IzcL9rCPozFUyC/a+To+8zCX9Na9I5QYMUWg6G6mwavp9PAU84v7Cgv5WvTd/ALR
m+Irs4R8J41daC3i8c7OznpnExfhV8LdF51mGYOnj1dFukMNWaBt72lflhq+lNq1
MYvPpjdj1fPap9WuT/FbU5gumWOtq/bOiMAt3CqBxCgP/uYXVv7skIfAL/UQYMWX
Gd8eA0+XBss0ELEFu8IJjawh3fQ2f7H2MzhNHVXnn2UAlIEZHiHWdGVY5+zwR34=
=wuFT
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

What's up with pkg-fallout?

[Montgomery-Smith, Stephen]

I keep getting emails from pkg-fallout@ that some of my ports are
faulty.  But it is obvious that pkg-fallout sometimes uses a really old
ports trees.  And the errors it is reporting have been fixed weeks ago.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Concerning pkgng

[Montgomery-Smith, Stephen]

So I have started using pkgng.  It is extremely easy to convert, it runs
very fast, and I really like it.

However, it would be nice if the old pkg_install, pkg_info, etc programs
were somehow disabled on FreeBSD-8.  Maybe they could look inside
/etc/make.conf and see if /var/db/pkg/local.sqlite exists, and then
decide not to operate.

The reason for this is because I can easily see me accidentally doing
pkg_delete instead of pkg delete.  And especially since pkg convert
seems to leave all the old directories in /var/db/pkg, I can see this
creating quite a mess.

I know I can simply delete the pkg_delete, pkg_info binaries.  But I'll
have to remember to do that each time I remake world.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

On 02/05/2014 11:04 AM, Montgomery-Smith, Stephen wrote:
> On 02/05/2014 12:29 AM, Daniel Smith wrote:
>> I just tested it on my box. It gets a lot further, but crashes when
>> building scipy-0.12.0.p1. The only message in the log is a line
>> indicating that the spkg-install script failed on a line reading 
>>
>> python setup.py setup
>>
>> I'm currently working on digging through that file to see if I can
>> figure out more, but I won't be able to do much before tomorrow, I'm
>> afraid.
>>
>> I've attached the log file for details.
>>
> 
> I and one other person got the same error.
> 
> I did try the patch
> /usr/ports/devel/scons/files/patch-engine-SCons-compat-_scons_subprocess.py,
> but it didn't help at all.
> 
> If you type make again, I find that sage tries skipping the packages it
> failed to build in favor of other packages.  In this manner, you can
> find that matplotlib-1.2.1 fails to build in exactly the same way.

I built the science/py-scipy port.  Comparing the build logs, it seems
to me that sage completely builds the scipy subpackage.  And then python
crashes.  So somehow the problem is not with scipy as such.

You could just take out the error handling in the script spkg-install
inside build/pkgs/scipy.  That would be rather dangerous, but it might
provide for a temporary work around the problem.

To be honest, I am finding FreeBSD-10 to be quite a pain.  It is
something of a moving target.  One of my other ports now fails, where it
seems it used to build under FreeBSD-10 quite successfully.

If any of you have good insights, I would appreciate it.  But I may not
be able to spend a lot more time hunting down this bug until next
summer.  And I would prefer to wait until FreeBSD-10.1 is rolled out,
and things are more stable.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

On 02/05/2014 12:29 AM, Daniel Smith wrote:
> I just tested it on my box. It gets a lot further, but crashes when
> building scipy-0.12.0.p1. The only message in the log is a line
> indicating that the spkg-install script failed on a line reading 
> 
> python setup.py setup
> 
> I'm currently working on digging through that file to see if I can
> figure out more, but I won't be able to do much before tomorrow, I'm
> afraid.
> 
> I've attached the log file for details.
> 

I and one other person got the same error.

I did try the patch
/usr/ports/devel/scons/files/patch-engine-SCons-compat-_scons_subprocess.py,
but it didn't help at all.

If you type make again, I find that sage tries skipping the packages it
failed to build in favor of other packages.  In this manner, you can
find that matplotlib-1.2.1 fails to build in exactly the same way.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

On 02/02/2014 08:16 PM, Montgomery-Smith, Stephen wrote:
> On 01/29/2014 07:26 PM, Montgomery-Smith, Stephen wrote:
>> On 01/29/2014 07:00 PM, Montgomery-Smith, Stephen wrote:
>>> I have just updated sage to version 6.0.  I have also made some changes
>>> to help it work with FreeBSD-10, using ideas given to me by Daniel
>>> Smith.  Since I don't have a fast computer using FreeBSD-10, I would
>>> appreciate it if any of you guys could try it out and see if it works.
>>
>> I meant math/sage (for those who don't normally use it.)

I just committed a change to the math/sage port, which I am hoping will
fix the build on FreeBSD-10.  The new file is
files/patch-build_pkgs_readline_fbsd-patch-src_support_shlib-install

I am testing it now, but it would be helpful if others would test it as
well, because my computer is slow.

Stephen

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

Solved - was: Problems with linking on FreeBSD-10

[Montgomery-Smith, Stephen]

On 01/31/2014 11:31 AM, Stephen Montgomery-Smith wrote:
> On 01/31/14 07:25, Konstantin Belousov wrote:
>> On Fri, Jan 31, 2014 at 12:19:46AM +, Montgomery-Smith, Stephen
>> wrote:
>>> I maintain the port math/sage.  The port builds its own version of the
>>> libreadline library.  The port also uses lang/gcc instead of clang,
>>> because the port needs Fortran.
>>>
>>> The port is wanting to create a shared library called libR.so, which it
>>> wants to link with the libreadline library it created itself.  So it
>>> issues this kind of command:
>>>
>>> gcc46 -Wl,-rpath=path-of-newly-made-library -o libR.so -lreadline
>>>
>>> I have left out most of the command for brevity.
>> Not for brevity, but to make the diagnostic impossible.
>>
> 
> Here are more details.  I have the -L there as well.
> 
> It creates libR.so using a command
> like this:
> 
> cc -std=gnu99 -shared -fopenmp
> -L/usr/home/stephen/sage/work/sage-6.0/local/lib/
> -Wl,-rpath=/usr/home/stephen/sage/work/sage-6.0/local/lib
> -Wl,-rpath=/usr/local/lib/gcc46 -L/usr/local/lib/gcc46  -o libR.so
> CommandLineArgs.o Rdynload.o Renviron.o RNG.o agrep.o apply.o
> arithmetic.o array.o attrib.o bind.o builtin.o character.o coerce.o
> colors.o complex.o connections.o context.o cum.o dcf.o datetime.o
> debug.o deparse.o devices.o dotcode.o dounzip.o dstruct.o duplicate.o
> edit.o engine.o envir.o errors.o eval.o format.o gevents.o gram.o
> gram-ex.o graphics.o grep.o identical.o inlined.o inspect.o internet.o
> iosupport.o lapack.o list.o localecharset.o logic.o main.o mapply.o
> match.o memory.o names.o objects.o options.o paste.o platform.o plot.o
> plot3d.o plotmath.o print.o printarray.o printvector.o printutils.o
> qsort.o random.o raw.o registration.o relop.o rlocale.o saveload.o
> scan.o seq.o serialize.o sort.o source.o split.o sprintf.o startup.o
> subassign.o subscript.o subset.o summary.o sysutils.o unique.o util.o
> version.o vfonts.o xxxpr.o   `ls ../unix/*.o ../appl/*.o ../nmath/*.o`
> ../extra/zlib/libz.a ../extra/bzip2/libbz2.a ../extra/pcre/libpcre.a
> ../extra/tre/libtre.a
> -L/usr/home/stephen/sage/work/sage-6.0/local/lib -lf77blas -latlas
> -lgfortran -lm -lquadmath  -lintl -lreadline  -llzma -lrt -lm -liconv
> 
> Now -Wl,-rpath is set, so it should find libreadline in
> /usr/home/stephen/sage/work/sage-6.0/local/lib.  But instead it finds
> libreadline in /lib.  So later when it does the following compilation to
> build R.bin:
> 
> gcc -std=gnu99 -export-dynamic -fopenmp
> -L/usr/home/stephen/sage/work/sage-6.0/local/lib/
> -Wl,-rpath=/usr/home/stephen/sage/work/sage-6.0/local/lib
> -Wl,-rpath=/usr/local/lib/gcc46 -L/usr/local/lib/gcc46 -o R.bin Rmain.o
>  -L../../lib -lR
> 
> ...it comes up with an error saying that rl_sort_completion_matches
> isn't found.  And when I do an ldd or "readelf -d" on libR.so, I can see
> that it is trying to link to the wrong libreadline, and
> rl_sort_completion_matches is only defined in the other libreadline.
> 
> 
>>>
>>> Unfortunately the libR.so pulls in /lib/libreadline - the version that
>>> comes with the base FreeBSD.  I thought that -rpath flag was supposed to
>>> tell the linker where to find the library.  But it doesn't.
>> Show exact commands and exact error message.  It is not possible to
>> understand from you message is the failure at the static linking (ld(1))
>> or dynamic (at the program startup) stage.
>>
>> Just in case this might be useful:
>> - -rpath only affects runtime search path
>> - ld(1) search for libraries is directed with the -L  option.
>>
>>>
>>> The failure is when using FreeBSD-10.  With FreeBSD-8 it works great.  I
>>> also assume that gcc46 uses /usr/local/bin/ld instead of /usr/bin/ld,
>>> since devel/binutils is a dependency of lang/gcc.
>>>
>>> Can anyone help me?  Is this a bug with FreeBSD?  Or is there some extra
>>> flag I can set with the linker to make it work?  I have tried
>>> -rpath-link and -z origin, but these were random guesses. and I don't
>>> really know what I am doing.
>>>
>>> Thanks, Stephen

/usr/home/stephen/sage/work/sage-6.0/local/lib contained
libreadline.so.6.  But for ld to work, it also had to contain a link
libreadline.so->libreadline.so.6.

(Is this sort of behavior documented anywhere?)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

On 01/29/2014 07:26 PM, Montgomery-Smith, Stephen wrote:
> On 01/29/2014 07:00 PM, Montgomery-Smith, Stephen wrote:
>> I have just updated sage to version 6.0.  I have also made some changes
>> to help it work with FreeBSD-10, using ideas given to me by Daniel
>> Smith.  Since I don't have a fast computer using FreeBSD-10, I would
>> appreciate it if any of you guys could try it out and see if it works.
> 
> I meant math/sage (for those who don't normally use it.)

A few days ago I updated to sage-6.1.  But I don't expect it to work any
better on FreeBSD-10 than sage-6.0.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Problems with linking on FreeBSD-10

[Montgomery-Smith, Stephen]

I maintain the port math/sage.  The port builds its own version of the
libreadline library.  The port also uses lang/gcc instead of clang,
because the port needs Fortran.

The port is wanting to create a shared library called libR.so, which it
wants to link with the libreadline library it created itself.  So it
issues this kind of command:

gcc46 -Wl,-rpath=path-of-newly-made-library -o libR.so -lreadline

I have left out most of the command for brevity.

Unfortunately the libR.so pulls in /lib/libreadline - the version that
comes with the base FreeBSD.  I thought that -rpath flag was supposed to
tell the linker where to find the library.  But it doesn't.

The failure is when using FreeBSD-10.  With FreeBSD-8 it works great.  I
also assume that gcc46 uses /usr/local/bin/ld instead of /usr/bin/ld,
since devel/binutils is a dependency of lang/gcc.

Can anyone help me?  Is this a bug with FreeBSD?  Or is there some extra
flag I can set with the linker to make it work?  I have tried
-rpath-link and -z origin, but these were random guesses. and I don't
really know what I am doing.

Thanks, Stephen

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

Re: Sage update

[Montgomery-Smith, Stephen]

On 01/30/2014 05:32 PM, Ajtim wrote:

> I am not lucky:
> Now installing the Maxima library as 
> '/usr/ports/math/sage/work/sage-6.0/local/lib/ecl//maxima.fas'...
> New ASDF encountered
> 
> real6m29.758s
> user5m28.766s
> sys 0m28.508s
> Successfully installed maxima-5.29.1.p4
> Deleting temporary build directory
> /usr/ports/math/sage/work/sage-6.0/local/var/tmp/sage/build/maxima-5.29.1.p4
> Finished installing maxima-5.29.1.p4.spkg
> make[4]: Leaving directory `/usr/ports/math/sage/work/sage-6.0/build'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/usr/ports/math/sage/work/sage-6.0/build'
> 
> real18m28.872s
> user94m55.810s
> sys 7m31.317s
> ***
> Error building Sage.
> 
> The following package(s) may have failed to build:
> 
> package: r-3.0.2.p0
> log file: /usr/ports/math/sage/work/sage-6.0/logs/pkgs/r-3.0.2.p0.log
> build directory: 
> /usr/ports/math/sage/work/sage-6.0/local/var/tmp/sage/build/r-3.0.2.p0
> 
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
> 
> gmake[2]: *** [build] Error 1
> gmake[2]: Leaving directory `/usr/ports/math/sage/work/sage-6.0'
> ===> Compilation failed unexpectedly.
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
> the maintainer.
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /usr/ports/math/sage
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/ports/math/sage
> 
> 

Can you send me this file:
/usr/ports/math/sage/work/sage-6.0/logs/pkgs/r-3.0.2.p0.log

Because the build is multithreaded, the install.log gets different
builds mixed up, and the error that caused the problem isn't always in
the last few lines.

However, I am also getting a build error at r-3.0.2.p0, and it is
exactly the same error as I was getting before.  All I want to check is
whether you are getting the same error as me.

I am also getting a build error with scipy and matplotlib-1.2.1.  The
scipy error exactly matches an error message I received from one of you
earlier today (before I applied the fix).

This means that whatever the problem is, the fix didn't fix it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

On 01/30/2014 11:03 AM, Daniel Smith wrote:
> I also tried rebuilding it and got the same error that Mitja saw.
> 
> I think the issue may be that the patches (for dealing with the
> freebsd1* vs freebsd1.*) aren't getting properly applied. I set
> SAGE_KEEP_BUILT_SPKS=yes before trying to build, and when I looked at
> the build dir for the mpir-spkg, it looks like the configure.patch file
> had the patches reversed. That is, in the file
> 
> sage-6.0/build/pkgs/mpir/patches/configure.patch
> 
> There are lines that read
> 
> -freebsd1.*)
> +freebsd1*)
> 
> The result, I think, is that patch believes the freebsd1.* lines, which
> are the ones we want, are the "old" values, hence the mpir configure
> script continues to act as if it were building on FreeBSD-1.x
> 
> I'm not entirely sure how
> 
> math/sage/files/patch-build_pkgs_mpir_patches_configure.patch
> 
> was generated, but it looks to me like a couple of the diffs in there
> had newer files as their first argument, e.g.,
> 
> +diff -ur src/aclocal.m4 b/aclocal.m4
> +--- src/aclocal.m4 2014-01-29 21:06:09.0 +
>  b/aclocal.m4   2012-10-03 20:07:32.0 +
> +@@ -2421,7 +2421,7 @@
> +   shlibpath_var=LD_LIBRARY_PATH
> +   ;;
> + 
> +-freebsd1.*)
> ++freebsd1*)
> ...
> 
> So I think the situation could be fixed by just changing the command
> around (the above was generated by
> 
> diff -ur src/aclocal.m4 b/aclocal.m4
> 
> so instead just take the output of
> 
> diff -ur b/aclocal.m4 src/aclocal.m4
> 
> and put the patch-build_pkgs_mpir_patches_configure.patch back together
> with that output, instead of what the first command generated).
> 
> At least, that's what I'm guessing is going on. I hope my explanation
> was clear enough.
> 
> Thanks!
> 


It looks like Daniel found the error.  I have created a new patch, and
just committed it.

Let me explain where it comes from.  I have added some code to sage,
which is in patch-src_bin_sage-spkg, which modified the configure files
to make them FreeBSD-10 friendly.  I took this code from bsd.port.mk.

But in sages version of mpir, there is a patch in
work/sage-6.0/build/pkgs/mpir/patches called configure.patch, which
after applying the changes to configure, no longer applies cleanly.

So what I did is this.  I untarred two copies of
work/sage-6.0/upstream/mpir-2.6.0.tar.bz2.  I renamed one directory to
src, and the other to b.

I patched b with configure.patch.  I then applied the script from
patch-src_bin_sage-spkg to both these directories.  I erased the *.orig
files in b.  I then did "diff -ur src b" to create a new copy of
configure.patch.  I then did "diff -u" between the old copy of
configure.patch and the new copy, putting it into
patch-build_pkgs_mpir_patches_configure.patch.  I touched up the first
two lines of the patch-build_pkgs_mpir_patches_configure.patch to get
the path names right, and put this into files.

This is what I meant to do previously, but obviously I made an error
somewhere in the process.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Sage update

[Montgomery-Smith, Stephen]

On 01/29/2014 07:26 PM, Montgomery-Smith, Stephen wrote:
> On 01/29/2014 07:00 PM, Montgomery-Smith, Stephen wrote:
>> I have just updated sage to version 6.0.  I have also made some changes
>> to help it work with FreeBSD-10, using ideas given to me by Daniel
>> Smith.  Since I don't have a fast computer using FreeBSD-10, I would
>> appreciate it if any of you guys could try it out and see if it works.
> 
> I meant math/sage (for those who don't normally use it.)

So I tried it on my slow i386 computer.  It dies on the subpackage
r-3.0.2.p0.  I would be interested if other people are seeing the same
problem.

I think it is because in the build, it creates libR.so using a command
like this:

cc -std=gnu99 -shared -fopenmp
-L/usr/home/stephen/sage/work/sage-6.0/local/lib/
-Wl,-rpath=/usr/home/stephen/sage/work/sage-6.0/local/lib
-Wl,-rpath=/usr/local/lib/gcc46 -L/usr/local/lib/gcc46  -o libR.so
CommandLineArgs.o Rdynload.o Renviron.o RNG.o agrep.o apply.o
arithmetic.o array.o attrib.o bind.o builtin.o character.o coerce.o
colors.o complex.o connections.o context.o cum.o dcf.o datetime.o
debug.o deparse.o devices.o dotcode.o dounzip.o dstruct.o duplicate.o
edit.o engine.o envir.o errors.o eval.o format.o gevents.o gram.o
gram-ex.o graphics.o grep.o identical.o inlined.o inspect.o internet.o
iosupport.o lapack.o list.o localecharset.o logic.o main.o mapply.o
match.o memory.o names.o objects.o options.o paste.o platform.o plot.o
plot3d.o plotmath.o print.o printarray.o printvector.o printutils.o
qsort.o random.o raw.o registration.o relop.o rlocale.o saveload.o
scan.o seq.o serialize.o sort.o source.o split.o sprintf.o startup.o
subassign.o subscript.o subset.o summary.o sysutils.o unique.o util.o
version.o vfonts.o xxxpr.o   `ls ../unix/*.o ../appl/*.o ../nmath/*.o`
../extra/zlib/libz.a ../extra/bzip2/libbz2.a ../extra/pcre/libpcre.a
../extra/tre/libtre.a
-L/usr/home/stephen/sage/work/sage-6.0/local/lib -lf77blas -latlas
-lgfortran -lm -lquadmath  -lintl -lreadline  -llzma -lrt -lm -liconv

Now -Wl,-rpath is set, so it should find libreadline in
/usr/home/stephen/sage/work/sage-6.0/local/lib.  But instead it finds
libreadline in /lib.  So later when it does the following compilation to
build R.bin:

gcc -std=gnu99 -export-dynamic -fopenmp
-L/usr/home/stephen/sage/work/sage-6.0/local/lib/
-Wl,-rpath=/usr/home/stephen/sage/work/sage-6.0/local/lib
-Wl,-rpath=/usr/local/lib/gcc46 -L/usr/local/lib/gcc46 -o R.bin Rmain.o
 -L../../lib -lR

...it comes up with an error saying that rl_sort_completion_matches
isn't found.  And when I do an ldd or "readelf -d" on libR.so, I can see
that it is trying to link to the wrong libreadline, and
rl_sort_completion_matches is only defined in the other libreadline.

I tried googling to find a fix.  And it works fine with FreeBSD-8.  This
has me completely stumped.  One web page suggested I added -Wl,-z,origin
to the list of flags when building libR.so.  But I really don't know
what I am doing.  Anyway, it didn't work.

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

Re: Sage update

[Montgomery-Smith, Stephen]

On 01/29/2014 07:00 PM, Montgomery-Smith, Stephen wrote:
> I have just updated sage to version 6.0.  I have also made some changes
> to help it work with FreeBSD-10, using ideas given to me by Daniel
> Smith.  Since I don't have a fast computer using FreeBSD-10, I would
> appreciate it if any of you guys could try it out and see if it works.

I meant math/sage (for those who don't normally use it.)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Sage update

[Montgomery-Smith, Stephen]

I have just updated sage to version 6.0.  I have also made some changes
to help it work with FreeBSD-10, using ideas given to me by Daniel
Smith.  Since I don't have a fast computer using FreeBSD-10, I would
appreciate it if any of you guys could try it out and see if it works.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: configure scripts and FreeBSD-10

[Montgomery-Smith, Stephen]

On 01/29/2014 07:27 AM, Thierry Thomas wrote:
> Hello Stephen,
> 
> Le mer 29 jan 14 à 14:15:51 +0100, Montgomery-Smith, Stephen 
> 
>  écrivait :
>> I have ports with configure scripts that include lines like
>>
>> freebsd1*)
>>
>> Now obviously the script will choose this case when I am running
>> FreeBSD-10 as well as FreeBSD-1.
>>
>> What solutions have people used to deal with this?Does anyone have
>> good examples of ports I can look at where this was solved?  Somebody
>> sent me a patch that replaces freebsd1*) with freebsd1[!0]*), but that
>> will fail when FreeBSD-11 comes out.
> 
> Just suppress the corresponding lines: we don't support FreeBSD-1!
> And check that one of the other case is relevant.
> 
> Regards,

That means I have to read through these configure files (and I have a
huge number of them).  Maybe I'll replace it with freebsd-nada). :-)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

configure scripts and FreeBSD-10

[Montgomery-Smith, Stephen]

I have ports with configure scripts that include lines like

freebsd1*)

Now obviously the script will choose this case when I am running
FreeBSD-10 as well as FreeBSD-1.

What solutions have people used to deal with this?Does anyone have
good examples of ports I can look at where this was solved?  Somebody
sent me a patch that replaces freebsd1*) with freebsd1[!0]*), but that
will fail when FreeBSD-11 comes out.

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

Re: Questions about staging

[Montgomery-Smith, Stephen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/27/2014 01:07 AM, Matthew Seaman wrote:
> On 27/01/2014 00:38, Montgomery-Smith, Stephen wrote:
>> I am looking at this part of
>> https://wiki.freebsd.org/ports/StageDir
>> 
>> Replace commands like ${CHMOD} ... and ${INSTALL_PROGRAM} -m mode
>> -o user -g group with corresponding pkg-plist entries: @mode
>> mode, @owner user, @group group. /!\ These operators work until
>> being overridden, or until the end of pkg-plist, so do not forget
>> to reset them with @mode, @owner, @group keywords afterwards.
>> 
>> I have to admit that I don't understand what this is driving at.
>> Can someone explain it to me?
> 
> This is all about being able to create packages without needing 
> superuser powers.  The idea is to take privileged commands like
> chmod(1) (or the implied chmod from using the -o flag to
> install(1)) out of install: targets in the port Makefile (which
> nowadays install into the staging directory) and replace them with
> equivalent constructs in pkg-plist (which are extracted into the
> generated pkg as pre/post- install script actions) ie. so that
> pkg(8) set the ownership of files at the point the package is
> installed.
> 
> Sometimes it involves a bit more than just editing the port
> Makefile -- here's an example from one of my own ports, where I had
> to fold, spindle and mutilate the software's own Makefiles to
> achieve the desired result:
> 
> http://svnweb.freebsd.org/ports?view=revision&revision=339461
> 
> This includes some other changes to do with using options helpers
> etc. but it should be clear enough what was done to move changing
> file ownership away from the staging step and into package
> installation. Look at the chagnes to pkg-plist and
> patch-Makefile.in in particular.

So it would only be necessary to do this if you want to set ownership
to anything other than root:wheel, since the pkg install program
should automatically set things to root:wheel anyway?  (Because things
installed the usual "make install" way will be set similarly?)

And presumably the same for chmod - it would only be necessary when
setting things like setuid or setgid bits, since otherwise it will
merely copy permissions from whatever the file in the tarball has?

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS5nJ9AAoJEC3xK9GaktgHvNgH/jzU+krSXo3zY3nllQyPl3gN
h5jmqW8TqBO78l2+ZQ3fq7OR6IOHAbZBGOLQ/+pl+IPVJH66tPoRlFI985vT/eab
3/3FQDG9D8xu6WmLHKUPamCTm8NS8jEEnIoc2YMVHhu8MCNcgBcy4zmDiokodp9B
nb036XNZJ78r6sZFad3Fpxc+g28zkHYRwDdwDED6+QhfKCTi8g8+bg8+1zN1mUga
0gDg84BBgGcAK52iZTCP+TBHC5sNNENeAWaCkF0JweEOq/i6KerV3L9KjipC3+E1
nt1gpvWRGltK/H7MhcSDVF7ig25FQkixrE6d30MffgbpnKV0lMATGUGWiuMN2/E=
=4QAN
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Questions about staging

[Montgomery-Smith, Stephen]

I am looking at this part of https://wiki.freebsd.org/ports/StageDir

Replace commands like ${CHMOD} ... and ${INSTALL_PROGRAM} -m mode -o
user -g group with corresponding pkg-plist entries: @mode mode, @owner
user, @group group.
/!\ These operators work until being overridden, or until the end of
pkg-plist, so do not forget to reset them with @mode, @owner, @group
keywords afterwards.

I have to admit that I don't understand what this is driving at.  Can
someone explain it to me?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

STAGE and INFO

[Montgomery-Smith, Stephen]

I am trying to implement staging on the port graphics/plotutils.  Right
now it has the following line in Makefile:

INFO=   libxmi plotutils

When I do "make stage; make check-orphans" I get
info/dir

Is this something I need to worry about?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: What is the problem with ports PR reaction delays?

[Montgomery-Smith, Stephen]

On 01/24/2014 05:30 PM, Big Lebowski wrote:
> Hi everyone,
> 
> I wanted to ask about the growing time of reaction to ports PR's - what is
> the problem? It seems to me, as a ports contributor, that this time is only
> growing, not shrinking, and there's no formal/automated procedures that
> would help in managing the issue.
> 
> Today I found myself fighting with ezjail only to discover it has issues
> working on FreeBSD 10.0-R. Great, I thought, there must be something else,
> so I went to make the research. It appears there isnt much more, and the
> alternatives are qjail that seems to be quite dated and zjails, that's not
> in ports. Not long after looking into zjails, what seems to be a great
> tool, I found its port submission sits there since... September 2013. Now,
> given the fact the Docker is on mouth of everyone, and containers are
> getting a lot of attention, FreeBSD looks really bad with no tools to
> manage such great technology like Jails, especially when ezjail, unofficial
> industry standard to manage jails, is now broken and zjails waits to be
> accepted (or even rejected) for so much time.
> 
> What is the problem? Isnt there enought commiters? Isnt there a automated
> PR handling procedure reminding commiters with relevant access about such
> submissions? Can we help? I hope to spark some discussion.
> 
> Kind regards,
> B.

When I became a committer (about 2.5 years ago), I spent my first summer
going through PRs and committing them.  Prior to that I had submitted
many ports, and I had felt the same frustration as you.  And when I saw
that some PRs were rather old, I could feel their frustration.

However, since that summer of activity on my part, my work
responsibilities overtook me, and I simply didn't have the time to keep
committing other people's PRs.  I think I have done a pretty good job at
maintaining my ports, but I have been terrible at committing other
people's PRs.

So I have seen it from both sides, and I think both sides have an equal
right to feel frustrated.

I had noticed quite an influx of new committers at some point, and that
seemed like a great solution to me.  But each new committer also
requires mentoring for a while, and that is also an effort for someone.

I really don't know what to say.  Next summer, if I have time, I'll try
to get into doing another group of PRs.  When I did do PRs, I did try to
concentrate on the older ones, rather than picking up the newer ones.

The older ones probably require more effort.  Sometimes the PR has a
mistake in it, and that is why it was left alone.  Other times, it
requires a level of expertize that many committers simply don't have.
(For example, in my case, I have zero experience with jails, and it
would be a huge learning curve on my part to learn enough to responsibly
commit your port.)  Sometimes the port no longer works because of
changes to the system (e.g. staging or changes to the base system).

Anyway, I feel your pain, and I wish I had good answers.

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

Re: Qpopper Port

[Montgomery-Smith, Stephen]

On 01/15/2014 06:08 PM, Doug Hardie wrote:
> I am going to have to give up maintaining qpopper.  Not because I don't have 
> the interest or time, but because I simply cannot update any port.  The old 
> port system may have had issues, but it worked!!!  The new one does not.  I 
> am completely unable to upgrade or install any ports on a 9.1 or higher 
> system.  I have a number of those in production and will have to now resort 
> to obtaining ports from the original sources and making them work on my 
> systems.  Its a colossal pain in the *&^*&^.

Call me old fashioned.  But I am still using FreeBSD-8 with the old
ports system.  I also never got into the idea of using portmaster or any
of those fancy tools, and still use pkg_version and pkg_delete and "cd
/usr/ports/xxx/yyy && make install clean" to maintain my ports.

I did install FreeBSD-10 on one computer recently, but I am experiencing
the same problems with the ports I am maintaining - I cannot build many
of them because dependent ports are breaking.

Also, I get periodic emails from pkg-fall...@freebsd.org explaining how
one or other of my ports don't build properly.  Some of the error
messages are clearly problems with switching from gcc to clang, and are
easily fixed.  But some of the other problems seem to be problems with
FreeBSD-10 itself (especially /usr/bin/ld), or problems with pkgng.

I do hope EOL for FreeBSD-8 is still some length of time away.  If I had
to upgrade today, it would create difficulties for me.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: math/sage build error

[Montgomery-Smith, Stephen]

On 01/12/2014 02:26 PM, Greg Rivers wrote:
> On Sun, 12 Jan 2014, Montgomery-Smith, Stephen wrote:
> 
>> On 01/12/2014 01:19 PM, Greg Rivers wrote:
>>> math/sage does not compile successfully on
>>> FreeBSD 10.0-PRERELEASE #0 r260501: Fri Jan 10 11:39:36 CST 2014 amd64
>>>
>>
>> Other people have reported this error to me.  However I am unable to
>> reproduce it in RC5.  Do you know if you were using an earlier version
>> of FreeBSD-10?
>>
> 
> The host had never run any version of FreeBSD-10 before I updated it
> last Friday.  Prior to that, it had been tracking /stable/9, and was
> running 9.2-STABLE from ~September 29.
> 
> I updated to 10-STABLE from SVN /stable/10 sources using the standard
> procedure, including `make delete-old` and `make delete-old-libs`.  The
> update went perfectly and there were no errors.
> 
> I then deleted all ports and rebuilt them all from scratch.
> 
>> I do get an error building ecl with FreeBSD-10-RC5.  So there is still
>> work to go.
>>
> 
> Thank you very much for maintaining this port.  Let me know if I can
> provide any additional information that would help.
> 

Also, I only have FreeBSD-10 on a i386, so that might make a difference
as well.

The error message is:
/usr/local/bin/ld:
/usr/ports/math/sage/work/sage-5.13/local/lib/libgmp.a(sizeinbase.o):
relocation R_X86_64_32S against `__gmpn_bases' can not be used when
making a shared object; recompile with -fPIC

I don't see how this error could have crept into the build of sage
merely by using a different version of FreeBSD (because it builds just
fine with FreeBSD-8).  So either someone else can give me an idea, or it
will be a difficult problem to track down.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: math/sage build error

[Montgomery-Smith, Stephen]

On 01/12/2014 01:19 PM, Greg Rivers wrote:
> math/sage does not compile successfully on
> FreeBSD 10.0-PRERELEASE #0 r260501: Fri Jan 10 11:39:36 CST 2014 amd64
> 

Other people have reported this error to me.  However I am unable to
reproduce it in RC5.  Do you know if you were using an earlier version
of FreeBSD-10?

I do get an error building ecl with FreeBSD-10-RC5.  So there is still
work to go.


> ...
> libtool: link: gcc -shared  -fPIC -DPIC  .libs/exceptions.o
> .libs/extract.o .libs/uceil_exp2.o .libs/uceil_log2.o
> .libs/ufloor_log2.o .libs/add.o .libs/add1.o .libs/add_ui.o .libs/agm.o
> .libs/clear.o .libs/cmp.o .libs/cmp_abs.o .libs/cmp_si.o .libs/cmp_ui.o
> .libs/comparisons.o .libs/div_2exp.o .libs/div_2si.o .libs/div_2ui.o
> .libs/div.o .libs/div_ui.o .libs/dump.o .libs/eq.o .libs/exp10.o
> .libs/exp2.o .libs/exp3.o .libs/exp.o .libs/frac.o .libs/frexp.o
> .libs/get_d.o .libs/get_exp.o .libs/get_str.o .libs/init.o
> .libs/inp_str.o .libs/isinteger.o .libs/isinf.o .libs/isnan.o
> .libs/isnum.o .libs/const_log2.o .libs/log.o .libs/modf.o
> .libs/mul_2exp.o .libs/mul_2si.o .libs/mul_2ui.o .libs/mul.o
> .libs/mul_ui.o .libs/neg.o .libs/next.o .libs/out_str.o .libs/printf.o
> .libs/vasprintf.o .libs/const_pi.o .libs/pow.o .libs/pow_si.o
> .libs/pow_ui.o .libs/print_raw.o .libs/print_rnd_mode.o .libs/reldiff.o
> .libs/round_prec.o .libs/set.o .libs/setmax.o .libs/setmin.o
> .libs/set_d.o .libs/set_df!
> l_prec.o .libs/set_exp.o .libs/set_rnd.o .libs/set_f.o
> .libs/set_prc_raw.o .libs/set_prec.o .libs/set_q.o .libs/set_si.o
> .libs/set_str.o .libs/set_str_raw.o .libs/set_ui.o .libs/set_z.o
> .libs/sqrt.o .libs/sqrt_ui.o .libs/sub.o .libs/sub1.o .libs/sub_ui.o
> .libs/rint.o .libs/ui_div.o .libs/ui_sub.o .libs/urandom.o
> .libs/urandomb.o .libs/get_z_exp.o .libs/swap.o .libs/factorial.o
> .libs/cosh.o .libs/sinh.o .libs/tanh.o .libs/sinh_cosh.o .libs/acosh.o
> .libs/asinh.o .libs/atanh.o .libs/atan.o .libs/cmp2.o .libs/exp_2.o
> .libs/asin.o .libs/const_euler.o .libs/cos.o .libs/sin.o .libs/tan.o
> .libs/fma.o .libs/fms.o .libs/hypot.o .libs/log1p.o .libs/expm1.o
> .libs/log2.o .libs/log10.o .libs/ui_pow.o .libs/ui_pow_ui.o
> .libs/minmax.o .libs/dim.o .libs/signbit.o .libs/copysign.o
> .libs/setsign.o .libs/gmp_op.o .libs/init2.o .libs/acos.o
> .libs/sin_cos.o .libs/set_nan.o .libs/set_inf.o .libs/set_zero.o
> .libs/powerof2.o .libs/gamma.o .libs/set_ld.o .libs/get_ld.o
> .libs/cbrt.o .libs/volatile.o !
> .libs/fits_sshort.o .libs/fits_sint.o .libs/fits_slong.o
> .libs/fits_ushort.o .libs/fits_uint.o .libs/fits_ulong.o
> .libs/fits_uintmax.o .libs/fits_intmax.o .libs/get_si.o .libs/get_ui.o
> .libs/zeta.o .libs/cmp_d.o .libs/erf.o .libs/inits.o .libs/inits2.o
> .libs/clears.o .libs/sgn.o .libs/check.o .libs/sub1sp.o .libs/version.o
> .libs/mpn_exp.o .libs/mpfr-gmp.o .libs/mp_clz_tab.o .libs/sum.o
> .libs/add1sp.o .libs/free_cache.o .libs/si_op.o .libs/cmp_ld.o
> .libs/set_ui_2exp.o .libs/set_si_2exp.o .libs/set_uj.o .libs/set_sj.o
> .libs/get_sj.o .libs/get_uj.o .libs/get_z.o .libs/iszero.o .libs/cache.o
> .libs/sqr.o .libs/int_ceil_log2.o .libs/isqrt.o .libs/strtofr.o
> .libs/pow_z.o .libs/logging.o .libs/mulders.o .libs/get_f.o
> .libs/round_p.o .libs/erfc.o .libs/atan2.o .libs/subnormal.o
> .libs/const_catalan.o .libs/root.o .libs/sec.o .libs/csc.o .libs/cot.o
> .libs/eint.o .libs/sech.o .libs/csch.o .libs/coth.o .libs/round_near_x.o
> .libs/constant.o .libs/abort_prec_max.o .libs/stack_interface.o .libs/lng
> amma.o .libs/zeta_ui.o .libs/set_d64.o .libs/get_d64.o .libs/j!
> n.o .libs/yn.o .libs/rem1.o .libs/get_patches.o .libs/add_d.o
> .libs/sub_d.o .libs/d_sub.o .libs/mul_d.o .libs/div_d.o .libs/d_div.o
> .libs/li2.o .libs/rec_sqrt.o .libs/min_prec.o .libs/buildopt.o
> .libs/digamma.o .libs/bernoulli.o .libs/isregular.o .libs/set_flt.o
> .libs/get_flt.o .libs/scale2.o .libs/set_z_exp.o .libs/ai.o
> .libs/gammaonethird.o .libs/grandom.o   -L/usr/local/lib/gcc46
> -L/usr/ports/math/sage/work/sage-5.13/local/lib
> /usr/ports/math/sage/work/sage-5.13/local/lib/libgmp.a  -O3
> -Wl,-rpath=/usr/ports/math/sage/work/sage-5.13/local/lib
> -Wl,-rpath=/usr/local/lib/gcc46
> -Wl,-rpath=/usr/ports/math/sage/work/sage-5.13/local/lib
> -Wl,-rpath=/usr/local/lib/gcc46   -Wl,-soname -Wl,libmpfr.so.5 -o
> .libs/libmpfr.so.5
> /usr/local/bin/ld:
> /usr/ports/math/sage/work/sage-5.13/local/lib/libgmp.a(sizeinbase.o):
> relocation R_X86_64_32S against `__gmpn_bases' can not be used when
> making a shared object; recompile with -fPIC
> /usr/ports/math/sage/work/sage-5.13/local/lib/libgmp.a: error adding
> symbols: Bad value
> collect2: ld returned 1 exit status
> make[8]: *** [libmpfr.la] Error 1
> make[8]: Leaving directory
> `/usr/ports/math/sage/work/sage-5.13/spkg/build/mpfr-3.1.2.p0/src/src'
> make[7]: *** [all] Error 2
> make[7]: Leaving directory
> `/usr/ports/math/sage/work/sage-5.13/spkg/build/mpfr-3.1.2.p0/src/src'
> make[6]: *** [all-recursive] Error 1
> make[6]: Leaving directory
> `/usr/ports/math/s