Re: unexpected package dependency

2016-02-22 Thread Lowell Gilbert 
Andriy Gapon  writes:

> On 19/02/2016 03:55, Perry Hutchison wrote:
>> Andriy Gapon  wrote:
>>> On 17/02/2016 11:28, Perry Hutchison wrote:
 I had not expected to find gcc listed (in packagesite.yaml) as a
 dependency of the sysutils/cpuburn package.  I can understand a
 _port_ needing gcc (at build time), but does the cpuburn _package_
 actually require gcc at _runtime_?
>>>
>>> I don't believe so.  AFAIR, it builds static binaries.
>> 
>> So would the inclusion of gcc in the "deps" for sysutils/cpuburn (in
>> packagesite.yaml) be caused by a problem with the way the dependencies
>> are specified in the port, or with the way they are handled by the
>> package-generation mechanism?  (I'm trying to figure out which to file
>> a PR against -- and I'm not all that familiar with pkgng details.)
>> 
>
> My recollection is that the ports infrastructure does not allow to specify
> whether a non-base compiler (like GCC for FreeBSD 11) is required only as a
> compiler (that is, only during the build time) or if its run-time is required 
> as
> well.  The latter is always assumed.

USES_GCC doesn't support that, but using BUILD_DEPENDS with RUN_DEPENDS
does. The downside to that is you have to specify a particular version
when you otherwise would not have needed to do so. Adding a knob to
bsd.gcc.mk to allow a port to say it doesn't need the RUN_DEPENDS would
do the right thing.

> But I could be mistaken.

I've probably overlooked a lot of things, but I did *test* my
suggestion, so I'm probably not completely wrong.
___
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: unexpected package dependency

2016-02-22 Thread Andriy Gapon 
On 19/02/2016 03:55, Perry Hutchison wrote:
> Andriy Gapon  wrote:
>> On 17/02/2016 11:28, Perry Hutchison wrote:
>>> I had not expected to find gcc listed (in packagesite.yaml) as a
>>> dependency of the sysutils/cpuburn package.  I can understand a
>>> _port_ needing gcc (at build time), but does the cpuburn _package_
>>> actually require gcc at _runtime_?
>>
>> I don't believe so.  AFAIR, it builds static binaries.
> 
> So would the inclusion of gcc in the "deps" for sysutils/cpuburn (in
> packagesite.yaml) be caused by a problem with the way the dependencies
> are specified in the port, or with the way they are handled by the
> package-generation mechanism?  (I'm trying to figure out which to file
> a PR against -- and I'm not all that familiar with pkgng details.)
> 

My recollection is that the ports infrastructure does not allow to specify
whether a non-base compiler (like GCC for FreeBSD 11) is required only as a
compiler (that is, only during the build time) or if its run-time is required as
well.  The latter is always assumed.

But I could be mistaken.

-- 
Andriy Gapon
___
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: Pulling from github as a vendorized dependency in poudriere

2016-02-22 Thread Derek (freebsd lists) 

On 16-02-19 08:42 PM, Derek (freebsd lists) wrote:

On 16-02-19 02:16 PM, Brooks Davis wrote:

On Fri, Feb 19, 2016 at 07:13:04AM -0500, Derek (freebsd lists)
wrote:

I can provide more detail, but would like to know if I'm doing
something horribly wrong first (i.e. trying to access the network
with gb as a make target, versus some other way to do this).


When you run "gb vendor", what stage does that happen in?  IIRC
poudriere only configures network access during the fetch stage
so you
must find a way to run it as part of the fetch process or
capture and
emulate its result.


Indeed, I was doing it in the post-extract stage, as there is
some patching that happens to the pulled-in sources from there,
and the vendor information is extracted from the tarball.

I see now, poudriere wants "no network", as you mention:

https://fossil.etoilebsd.net/poudriere/doc/trunk/doc/design.mkd



I've submitted a patch to doc:

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

Additionally, I was able to pull in my depends via:

5.4.3.1. Fetching Multiple Files from GitHub
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html#idp63641808

So it wasn't so bad.

Dunno what it would look like if my depends were in a few 
different places though.


Thanks all!
Derek

___
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 make port for opencoarrays

2016-02-22 Thread Tijl Coosemans 
On Mon, 22 Feb 2016 09:50:01 + David Chisnall  wrote:
> On 22 Feb 2016, at 09:01, Tijl Coosemans  wrote:
>> I think Fortran is fine.  It's C++ that's in a bad shape.  I think the
>> lang/gcc* ports need to be modified so libstdc++ sits on top of libcxxrt
>> instead of libsupc++.  Maybe David can say more about that (CCed).  
> 
> Ideally, they should be modified to just use libc++.  I thought that bapt
> had done this, but I might have misremembered.

Now I remember he created USES=compiler:gcc-c++11-lib which modifies
CXXFLAGS and LDFLAGS so g++ uses libc++ headers and library.  That works
inside the ports tree but it still leaves g++ cumbersome to use on the
command line.

What about libcompiler_rt, should the gcc ports use that library too
(for its personality function for instance)?

The base system still seems to be using the unwind implementation from
gcc.  Will that change at some point?
___
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: https://svnweb.freebsd.org/ports/head/graphics/ 83 ports missing.

2016-02-22 Thread Christoph Moench-Tegeder 
## Julian H. Stacey (j...@berklix.com):

> There seems to be loss of 83 ports in graphics/ on freebsd.org http server ?
>   https://svnweb.freebsd.org/ports/head/graphics/
> All beyond telak missing.
> eg tesseract & others missing

https://svnweb.freebsd.org/ports/head/graphics/?dir_pagestart=1000

Regards,
Christoph

-- 
Spare Space
___
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"

https://svnweb.freebsd.org/ports/head/graphics/ 83 ports missing.

2016-02-22 Thread Julian H. Stacey 
Hi po...@freebsd.org
cc'd ports-...@freebsd.org 

There seems to be loss of 83 ports in graphics/ on freebsd.org http server ?
https://svnweb.freebsd.org/ports/head/graphics/
All beyond telak missing.
eg tesseract & others missing
in my local ls of graphics/ telak is 1005 of 1089

I looked both with firefox through a proxy, & direct with lynx.

Cheers,
Julian
-- 
Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich http://berklix.eu/jhs/
 Mail plain text,  No quoted-printable, HTML, base64, MS.doc.
 Prefix old lines '> '  Reply below old, like play script.  Break lines by 80.
___
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: pkg upgrade issue

2016-02-22 Thread Doug Hardie 

> On 22 February 2016, at 02:13, Baptiste Daroussin  wrote:
> 
> On Sun, Feb 21, 2016 at 10:03:14PM -0800, Doug Hardie wrote:
>> On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages:
>> 
>> sermons# pkg upgrade
>> Updating repository catalogue
>> pkg: 
>> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz:
>>  File unavailable (e.g., file not found, no access)
>> 
> Can you show the output of pkg -vv please?
> 
> I'm more interested in the lines below "Repositories:"


I copied /usr/local/etc/pkg.conf from another 9.3 system that works:

sermons# pkg -vv
pkg: Invalid configuration format, ignoring the configuration file
version: 1.0.11
abi: freebsd:9:x86:64
db dir: /var/db/pkg
cache dir: /var/cache/pkg
ports dir: /usr/ports
Log into syslog: yes
Assume always yes: no
Repository: none


Removing /usr/local/etc/pkg.conf (original status):
sermons# pkg -vv
version: 1.0.11
abi: freebsd:9:x86:64
db dir: /var/db/pkg
cache dir: /var/cache/pkg
ports dir: /usr/ports
Log into syslog: yes
Assume always yes: no
Repository: none

sermons# pkg update
Updating repository catalogue
pkg: PACKAGESITE is not defined.


PACKAGESITE was defined in ~/.cshrc as:
setenv PACKAGESITE 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/

That was removed for the above test.  It was present for the previously report 
pkg output.

As I remember this system was updated to 9.x when there were issues with the 
package system being rebuilt and a workaround was needed.  I no longer recall 
where all the pieces of that were.

___
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: pkg upgrade issue

2016-02-22 Thread Baptiste Daroussin 
On Sun, Feb 21, 2016 at 10:03:14PM -0800, Doug Hardie wrote:
> On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages:
> 
> sermons# pkg upgrade
> Updating repository catalogue
> pkg: 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz:
>  File unavailable (e.g., file not found, no access)
> 
Can you show the output of pkg -vv please?

I'm more interested in the lines below "Repositories:"

Best regards,
Bapt


signature.asc
Description: PGP signature

Re: pkg upgrade issue

2016-02-22 Thread Lars Engels 
On Mon, Feb 22, 2016 at 01:44:53AM -0800, Doug Hardie wrote:
> /etc/pkg/FreeBSD.conf contains (comments removed):
> 
> FreeBSD: {
>   url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
>   mirror_type: "srv",
>   signature_type: "fingerprints",
>   fingerprints: "/usr/share/keys/pkg",
>   enabled: yes
> }
> ~
> That appears to match with your entry below.
> 

But it doesn't match 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz

Do you have some other repository config in /usr/local/etc/pkg/repos?


pgpxUNzhmq5ja.pgp
Description: PGP signature

Re: help make port for opencoarrays

2016-02-22 Thread David Chisnall 
On 22 Feb 2016, at 09:01, Tijl Coosemans  wrote:
> 
> I think Fortran is fine.  It's C++ that's in a bad shape.  I think the
> lang/gcc* ports need to be modified so libstdc++ sits on top of libcxxrt
> instead of libsupc++.  Maybe David can say more about that (CCed).

Ideally, they should be modified to just use libc++.  I thought that bapt had 
done this, but I might have misremembered.  Mixing libstdc++ and libc++ is fine 
if both sit on top of libcxxrt and no standard library types cross library 
boundaries, but is problematic otherwise (the good news is that you’ll get 
linker failures if they do try to cross library boundaries, unless they’re 
thrown as exceptions).

David

___
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: pkg upgrade issue

2016-02-22 Thread Doug Hardie 
/etc/pkg/FreeBSD.conf contains (comments removed):

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest;,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}
~
That appears to match with your entry below.


> On 22 February 2016, at 00:56, Lars Engels  wrote:
> 
> On Sun, Feb 21, 2016 at 10:03:14PM -0800, Doug Hardie wrote:
>> On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages:
>> 
>> sermons# pkg upgrade
>> Updating repository catalogue
>> pkg: 
>> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz:
>>  File unavailable (e.g., file not found, no access)
>> 
> 
> Most probably your repository config is wrong.
> Try pkg+http://pkg.FreeBSD.org/${ABI}/latest 

— Doug

___
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 make port for opencoarrays

2016-02-22 Thread Tijl Coosemans 
On Sun, 21 Feb 2016 13:51:28 -0800 (PST) Anton Shterenlikht  
wrote:
> From thie...@pompo.net Sun Feb 21 17:36:47 2016
>> Le mer 17 f_v 16 _ 23:50:37 +0100, Anton Shterenlikht 
>> _crivait_:  
>>> Please help/advise
>>> 
>>> https://github.com/sourceryinstitute/opencoarrays
>>> 
>>> It requires mpich built with at least gcc5.3,
>>> more specifically mpif90 built with gcc5.3 or gcc6.
>>> net/mpich has FORTRAN_USES=fortran, which I understand
>>> triggers lang/gcc.
>>> 
>>> Is it a good idea (or at all possible) to add
>>> an option to net/mpich to choose a particular
>>> gcc version?
>>> 
>>> Any other advice?  
>>
>> ATM Fortran in FreeBSD is in a very bad shape, and, as you know, we
>> encounter difficulties with several ports (french/aster, cad/salome,
>> etc.) caused by a mix between clang and Gcc, and thus libstdc++ /
>> libc++.  

I think Fortran is fine.  It's C++ that's in a bad shape.  I think the
lang/gcc* ports need to be modified so libstdc++ sits on top of libcxxrt
instead of libsupc++.  Maybe David can say more about that (CCed).

>> If building mpich with a newer Gcc could solve the problem with
>> opencoarrays, I'm afraid it would cause uncompatibilities in other
>> dependencies - but unfortunately I cannot suggest a better alternative!  
> 
> Well, I'm only asking for an option in the port.
> The default will not change.
> 
> I'll have a go locally and see what happens.
> But I'm not sure what option to use to build
> with e.g. GCC6. Is it this line?
> 
> FORTRAN_USES=   fortran
> 
> Or are you saying that building mpich with
> non-default gcc is problematic because all
> its dependencies should be built with the
> same gcc version?

Users can change ports tree default versions by setting DEFAULT_VERSIONS
in /etc/make.conf:

DEFAULT_VERSIONS=   gcc=5

DEFAULT_VERSIONS is handled in /usr/ports/Mk/bsd.default-versions.mk and
/usr/ports/Mk/Uses/fortran.mk uses it to select the Fortran compiler.
So with the line above the Fortran part of net/mpich will be built with
lang/gcc5.

In your opencoarray port I think you can do something like this:

...
USES=   fortran
...
.include 

.if ${GCC_DEFAULT:R} < 5
IGNORE= This port requires that the default GCC version is 5 or higher
.endif
...
.include 
___
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: pkg upgrade issue

2016-02-22 Thread Lars Engels 
On Sun, Feb 21, 2016 at 10:03:14PM -0800, Doug Hardie wrote:
> On a FreeBSD 9.3 P33 system, I don't seem to be able to upgrade packages:
> 
> sermons# pkg upgrade
> Updating repository catalogue
> pkg: 
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest//repo.txz:
>  File unavailable (e.g., file not found, no access)
> 

Most probably your repository config is wrong.
Try pkg+http://pkg.FreeBSD.org/${ABI}/latest 


pgpt29eTUYdNl.pgp
Description: PGP signature

FreeBSD ports you maintain which are out of date

2016-02-22 Thread portscout 
Dear port maintainer,

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

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

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


Port| Current version | New version
+-+
math/glm| 0.9.7.1 | 0.9.7.3
+-+


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

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

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