FreeBSD Port: geomWatch-1.3.0_2

[Robert William Vesterman]

Hello,

I just found the geomWatch port which you maintain.  I have a question 
about it, but haven't been able to find the answer yet, so I hope you 
don't mind me asking you:


I intentionally do not have a full blown MTA on my box, so I don't have 
anything listening at localhost:25.  Instead, I use the ssmtp 
 
port, as suggested in the FreeBSD handbook section "Setting Up to Send 
Only" .  ssmtp 
is then configured to talk to an external SMTP server whenever a local 
account tries to send an email.


I tried setting up geomWatch, but it seems like it requires speaking 
directly to an SMTP server.  Is this correct? Or is there a way to set 
it up so that it perhaps just uses something like the built-in "mail" 
command to send, which would (on my box) then use ssmtp behind the scenes?


Or must I either set up an SMTP server on my box or else configure 
geomWatch to use an external SMTP server?


Thanks,

Bob Vesterman

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

audio/logitechmediaserver fails apparently due to perl mismatch

[Robert William Vesterman]

I have had audio/squeezeboxserver installed on FreeBSD 10.1 RELEASE i386 
for a long time.  It has now been replaced by audio/logitechmediaserver, 
and I'm trying (and failing) to upgrade. It gets seemingly pretty far 
into the install:


===>  Installing for logitechmediaserver-7.9.0.g2016.09.30
===>   logitechmediaserver-7.9.0.g2016.09.30 depends on executable: mac 
- found
===>   logitechmediaserver-7.9.0.g2016.09.30 depends on executable: faad 
- found
===>   logitechmediaserver-7.9.0.g2016.09.30 depends on executable: flac 
- found
===>   logitechmediaserver-7.9.0.g2016.09.30 depends on executable: sox 
- found
===>   logitechmediaserver-7.9.0.g2016.09.30 depends on package: 
perl5>=5.20<5.21 - found
===>   logitechmediaserver-7.9.0.g2016.09.30 depends on shared library: 
libgd.so - found (/usr/local/lib/libgd.so)
===>   logitechmediaserver-7.9.0.g2016.09.30 depends on shared library: 
libintl.so - found (/usr/local/lib/libintl.so)

===>  Checking if logitechmediaserver already installed
===>   Registering installation for logitechmediaserver-7.9.0.g2016.09.30

But immediately after that, things go wrong.  It first gives this error:

pkg-static: Unable to access file 
/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN/arch/5.20/Audio/Cuefile/Parser.pm: 
No such file or directory


The problem there is that there is no "Audio" file within that "5.20" 
directory.


It then gives many, many errors like this:

pkg-static: 
lstat(/usr/ports/audio/logitechmediaserver/work/stage/usr/local/share/logitechmediaserver/CPAN/arch/5.20/i386-freebsd-thread-multi/auto/Sub/Uplevel/): 
No such file or directory


The problem there is that there's no "i386-freebsd-thread-multi" within 
"5.2.0".  There is, however, "i386-freebsd-thread-multi-64int".


After a whole bunch of errors trying to access files in that nonexistent 
"i386-freebsd-thread-multi" directory, it then fails.


I assume this has something to do with the fact that I'm not using a 64 
bit version of FreeBSD? But I have no idea what option to set where to 
tell that to logitechmediaserver's compilation process, if it's even 
possible in the first place.


Any help would be appreciated.  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"

firefox crash

[William A. Mahaffey III]

When I navigate to www.tdameritrade.com/home.page, it reliably crashes 
firefox-49.0_3,1, newly upgraded about 2 min. ago (from 49.0_2,1, 
upgraded Saturday, which also crashed), complete w/ firefox.core in my 
home directory:


[wam@kabini1, ~, 8:37:25am] 309 % uname -a
FreeBSD kabini1.local 9.3-RELEASE-p43 FreeBSD 9.3-RELEASE-p43 #0: Sat 
May 28 00:19:32 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64

[wam@kabini1, ~, 8:37:30am] 310 % lltr10; date
drwx--   20 wam   users   6656 Sep 12 22:39 Desktop/
-rw---1 wam   users174 Sep 17 16:16 .serverauth.88546
-rw---1 wam   users   1024 Sep 17 16:16 .rnd
-rw---1 wam   users   4782 Sep 17 16:16 .ICEauthority
-rw---1 wam   users  14334 Sep 17 16:25 .history
drwx--2 wam   users   3584 Sep 17 16:52 fontconfig/
drwx--3 wam   users 291840 Sep 18 09:25 Recipes/
-rw---1 wam   users   1019 Sep 19 04:38 LIST.cron
-rw---1 wam   users1276759 Sep 19 08:27 mbox
-rw---1 wam   users  363171840 Sep 19 08:34 firefox.core
Mon Sep 19 08:37:39 MCDT 2016
[wam@kabini1, ~, 8:37:39am] 311 %

Any other info needed, don't hesitate. Have a good one.

--

    William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: Firefox 47.0 hangs when accessing cnn.com

[William A. Mahaffey III]

On 06/09/16 00:10, Kevin Oberman wrote:

On Wed, Jun 8, 2016 at 4:04 PM, Bob Willcox < 
b...@immure.com> wrote:


Ok, I finally figured out how to get portdowngrade to give me a 46.0.1,1
version of firefox and built & installed it. Unfortunately, that didn't
solve
my hanging firefox scripts problem so apparently it's likely to be caused
by
something else that got updated when I did the portupgrade on June 4th. Not
sure where to go from here...

Bob


No easy answers. I, also have no issues with 47.0 on my system and there
are no other reports of the problem you are having. So where to look?

What version of FreeBSD are you running? On what platform? i386 or amd64 or
something else. Most people are running amd64. If ir is another platform,
issues are less likely to have been seen. Is it 10.3 or something else.

Unless someone else has a better suggestion, I'd re-install all
dependencies. Older versions are more likely to have issues.I use
portmaster, but I know portupgrade can also do this. Or use packages. It's
a lot faster when you don't need any options on the ports.

Other than that, I have no good ideas other than to re-install everything.
And that may not fix it as it is possible that it's a memory or other
hardware issue.

I hope someone else has a better idea than I.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: kob6...@gmail.com
___
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"



+1 on packages, *much* faster & same end result if you have no special 
compile options 



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: Firefox 47.0 hangs when accessing cnn.com

[William A. Mahaffey III]

On 06/07/16 07:54, Bob Willcox wrote:

Hi Grzegorz,

I altered my configuration to match what you list below and rebuilt/installed
firefox. I no longer get the dialog box about the script not working but
cnn.com still doesn't load as expected. It now will eventually complete but it
takes several minutes (I didn't precisely time it, but it's about 4 or 5
minutes) during which time firefox doesn't respond to any input at all. It
does seem to eventually complete transferring data and updating but then
firefox becomes very slow and unresponsive.

So, what is the best way to revert back to version 46? I really can't use
47 with the way it is behaving now.

Thanks,
Bob

On Mon, Jun 06, 2016 at 07:03:49PM +, Grzegorz Junka wrote:

I have upgrade to Firefox 47.0_1,1 earlier today and just tried cnn.com
- works without issues. I have compiled with poudriere using options:

# This file is auto-generated by 'make config'.
# Options for firefox-45.0.1_3,1
_OPTIONS_READ=firefox-45.0.1_3,1
_FILE_COMPLETE_OPTIONS_LIST=BUNDLED_CAIRO CANBERRA DBUS DEBUG DTRACE
FFMPEG GCONF GIO GNOMEUI INTEGER_SAMPLES LIBPROXY OPTIMIZED_CFLAGS PGO
PROFILE RUST TEST GTK2 GTK3 ALSA PULSEAUDIO
OPTIONS_FILE_UNSET+=BUNDLED_CAIRO
OPTIONS_FILE_UNSET+=CANBERRA
OPTIONS_FILE_SET+=DBUS
OPTIONS_FILE_UNSET+=DEBUG
OPTIONS_FILE_UNSET+=DTRACE
OPTIONS_FILE_SET+=FFMPEG
OPTIONS_FILE_UNSET+=GCONF
OPTIONS_FILE_SET+=GIO
OPTIONS_FILE_UNSET+=GNOMEUI
OPTIONS_FILE_UNSET+=INTEGER_SAMPLES
OPTIONS_FILE_SET+=LIBPROXY
OPTIONS_FILE_SET+=OPTIMIZED_CFLAGS
OPTIONS_FILE_UNSET+=PGO
OPTIONS_FILE_UNSET+=PROFILE
OPTIONS_FILE_SET+=RUST
OPTIONS_FILE_UNSET+=TEST
OPTIONS_FILE_UNSET+=GTK2
OPTIONS_FILE_SET+=GTK3
OPTIONS_FILE_SET+=ALSA
OPTIONS_FILE_UNSET+=PULSEAUDIO

Not sure why the file contains 45.0.1_3,1, probably because it hasn't
changed since then:

g@crayon2:~ % pkg info | grep firefox
firefox-47.0_1,1   Web browser based on the browser portion
of Mozilla

Grzegorz


On 06/06/2016 18:21, Bob Willcox wrote:

I updated my firefox 46.0.1 to 47.0_1.1 yesterday (Sunday) and now when I go
out to cnn.com it hangs, eventually putting up a dialog box telling me that a
script has stop working (or something similar). Nothing I've tried so far
seems to help and I wind up having to kill firefox.

Anyone else experiencing this? Not that other sites (besides cnn.com) have
hung on me as well, but cnn.com seems to be the worst (fails the quickest,
within seconds of going there).


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



FWIW, I just checked available pkg's using 'pkg version -vRL=' & nothing 
showed up for firefox: You might be a bit closer to the *bleeding* edge 
than you think w/ the ports version. I'm using firefox-46.0.1,1 from 
pkg's w/ no issues. $0.02, no more, no less.



[wam@kabini1, ~, 7:07:35am] 368 % uname -a
FreeBSD kabini1.local 9.3-RELEASE-p33 FreeBSD 9.3-RELEASE-p33 #0: Wed 
Jan 13 17:55:39 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64

[wam@kabini1, ~, 8:03:07am] 369 %


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: old ports/packages

[William A. Mahaffey III]

On 06/04/16 09:24, Matthew Seaman wrote:

On 04/06/2016 14:50, Grzegorz Junka wrote:

On 04/06/2016 13:45, Matthew Seaman wrote:

On 03/06/2016 17:23, Bob Eager wrote:

Why not just use odd numbered releases? That's what I do. They have a
longer support cycle.

Remember though that this model is changing with 11.0 release.  With the
new model, it's the 11.x family as a whole that has the long term
support and individual releases such as 11.0 or 11.1 will cease to be
supported very shortly after the next release in that series comes out.
The last release in that series will then have a long support life so
that 11.x as a whole has something like a 5 year lifecycle[*].  The
transitions from 11.0 -> 11.1 -> 11.2 -> ... are meant to be something
you could apply pretty much routinely; much as you'ld apply a new
patch-level today.

 Cheers,

 Matthew

[*] which is pretty much the same length as the the lifecycle of
previous major branches has been up to now.


Is there somewhere any more information available about this change?


https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html

https://news.ycombinator.com/item?id=8991960

Cheers,

Matthew





One point of order if I may: It was stated earlier in the thread that 
binary compatibility throughout a major release cycle (X.n-R, as 'n' 
varies) is a specification. That is not explicitly addressed in the 
above URL's, as far as I can see. Is that indeed considered a 
specification ? If so, it would seem to satisfy the LTS desire 
implicitly. TIA & have a good one.



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/14/16 01:54, Andriy Gapon wrote:

On 14/04/2016 05:38, William A. Mahaffey III wrote:

All seems OK w/ the system headers (I know, shocking ), the required files
defining a '__uintptr_t' are in fact unconditionally included, so it must be
something else (bad defines somewhere, or ). I am still chasing 

Apologies, but are you serious?..

$ fgrep -r __uintptr_t /usr/include/
...
/usr/include/x86/_types.h:typedef   __uint64_t  __uintptr_t;
/usr/include/x86/_types.h:typedef   __uint32_t  __uintptr_t;
...

This is on an amd64 head system.



Yeah, but the includes are several layers down, took me a bit to figure 
them out. Did I mention that I am *NOT* a kernel hacker ? Most of this 
system-type stuff is greek to me, organizationally (which is obviously 
on me, nobody else). I am still getting compile errors, looks like 
config.h has a bad line in it, which '#define's uintptr_t as 'unsigned 
long', which would give a compile error when used in a typedef line. I 
am going to just comment the offending lines out of the config.h file & 
see if I get farther. If so (or not, actually), I'll post back for 
either closure or hints.


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/13/16 02:51, Mehmet Erol Sanliturk wrote:

On Wed, Apr 13, 2016 at 12:02 AM, William A. Mahaffey III 
wrote:


On 04/12/16 21:05, Kevin P. Neal wrote:


On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote:


A bit of poking around yields a 'typedef  __uintptr_t uintptr_t;'

statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t
isn't defined anywhere  Any clues ? TIA & have a good one.




*C'mon*  Someone throw me a bone :-). Whassup here, this can't be
the 1st time this has happened  where is __uintptr_t
defined/typedef'ed ?


% find /usr/include/ -type f -print | xargs grep __uintptr_t

You'll need to follow the includes backwards until you get to an include
that looks like it is meant to be directly included. That particular
command
is left as an exercise to the reader.



*Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks
again.

--

 William A. Mahaffey III

  --

 "The M1 Garand is without doubt the finest implement of war
  ever devised by man."
-- Gen. George S. Patton Jr.

___




There are differences between FreeBSD and Linux include directory places .

Assume , it it is possible to build Open64 in Linux , but it is failing in
FreeBSD due to unfound files :

There is a need to specify include directories ( -I ) in make files
correctly for the FreeBSD being equivalent to Linux include directories .


For example , some files are specified in Linux as   #include  ,
but in FreeBSD as #include  .


Mehmet Erol Sanliturk .
___
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"




All seems OK w/ the system headers (I know, shocking ), the required 
files defining a '__uintptr_t' are in fact unconditionally included, so 
it must be something else (bad defines somewhere, or ). I am still 
chasing 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: tcc-0.9.26_3

[William A. Mahaffey III]

On 04/13/16 19:27, Ben Wiederhake wrote:

Hello,

"#include " seems to be impossible with tcc on FreeBSD.

Steps to reproduce:
Try to compile the following program:
"""
#include 
#include 
int main(void){printf("Hello world\n");}
"""

Excepted results:
Compilation finishes with no errors.

Actual results:
"""
In file included from foo.c:1:
In file included from /usr/include/stdint.h:33:
In file included from /usr/include/sys/_types.h:33:
In file included from /usr/include/machine/_types.h:6:
/usr/include/x86/_types.h:161: error: too many basic types
"""
And compilation fails.
In a real life project, it fails at exactly the same spot [2]

Diagnostics from the meatbag (hello!):
- Using gcc and clang instead works fine.  This must be tcc's fault, 
not system-headers'.
- On Ubuntu and Debian, tcc 0.9.26 works fine, too.  This must be some 
fault in the compilation, environment, or libraries of tcc, not tcc's 
code itself.
- The error message stems from line 2510 in tccgen.c [1]. However, I 
don't understand how it got there and where it "counts".
- This might also be due to a forgotten semicolon [3], which I deem 
inlikely for a system header.
- Note that tcc is one-pass, so it doesn't even know anything except 
the first line of foo.c.  Thus, tcc is currently unusable for me.


Versions, as far as I can tell:
- 'tcc -dumpversion' says '0.9.26'.
- `pkg upgrade` says 'Your packages are up to date.'
- `uname -a` says 'FreeBSD  10.3-RELEASE FreeBSD 10.3-RELEASE #0 
r297264: Fri Mar 25 02:10:02 UTC 2016'


Regards,
Ben Wiederhake

[1] 
https://github.com/search?utf8=%E2%9C%93&q=%22too+many+basic+types%22&type=Code&ref=searchresults

[2] https://gitlab.com/BenWiederhake/endian-ci/builds/1077867
[3] https://lists.gnu.org/archive/html/tinycc-devel/2008-09/msg00033.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"




Interesting. I am seeing (almost) the same error in another thread 
('porting' open64 compiler), same issue, some problem w/ getting some 
basic system types defined, same type of error, same system header 
files. I am on 9.3R, not 10.3, but interesting coincidence 



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/12/16 21:05, Kevin P. Neal wrote:

On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote:

A bit of poking around yields a 'typedef  __uintptr_t uintptr_t;'
statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t
isn't defined anywhere  Any clues ? TIA & have a good one.




*C'mon*  Someone throw me a bone :-). Whassup here, this can't be
the 1st time this has happened  where is __uintptr_t
defined/typedef'ed ?

% find /usr/include/ -type f -print | xargs grep __uintptr_t

You'll need to follow the includes backwards until you get to an include
that looks like it is meant to be directly included. That particular command
is left as an exercise to the reader.



*Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks 
again.


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/11/16 08:58, William A. Mahaffey III wrote:

On 04/10/16 18:57, William A. Mahaffey III wrote:

On 04/10/16 18:09, Peter Jeremy wrote:
On 2016-Apr-10 17:09:04 -0453, "William A. Mahaffey III" 
 wrote:
configure process completed OK, but created a Makefile w/ what 
seems to

be a bunch of linuxisms in conditionals to allow compilation for
different architectures, see attached orig-Makefile.

Have you tried using gmake, rather than the base make?




OK, I tried gmake & got the attached, lotta '#include malloc.h' all 
over the place, I'll have to handle that file-by-file :-/ 




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



OK fixed the above w/ find & sed, now I have:


.
.
.
.

In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/objects.c:59:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function
C 
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c
In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c:69:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c: In function 
'run_ar':
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c:3144: warning: 
implicit declaration of function 'get_executable_dir_from_path'
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c:3144: warning: 
initialization makes pointer from integer without a cast
C 
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/run.c
In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/run.c:86:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function
C 
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/special_options.c
In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/special_options.c:63:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function

GENversion_hg.c
C  /usr/src/contrib/obj/osprey/targdir/driver/version_hg.c
LD /usr/src/contrib/obj/osprey/targdir/driver/driver
file_names.o: In function `get_object_file':
file_names.c:(.text+0xe57): warning: warning: tempnam() possibly used 
unsafely; consider using mkstemp()

gmake[3]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
gmake last
gmake[3]: Entering directory '/usr/src/contrib/obj/osprey/targdir/driver'
hg: not found
rm -f opencc openCC openf90
ln -s driver opencc
ln -s driver openCC
ln -s driver openf90
gmake[3]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
gmake[2]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
gmake -C osprey/targdir/libiberty
gmake[2]: Entering directory 
'/usr/src/contrib/obj/osprey/targdir/libiberty'
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/alloca.c
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/argv.c
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/choose-temp.c
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/concat.c

In file included from /usr/include/sys/types.h:63,
 from 
../../../../x86_open64-4.5.2.1-1/osprey/libiberty/concat.c:52:
/usr/include/sys/_stdint.h:78: error: two or more data types in 
declaration specifiers
/usr/include/sys/_stdint.h:78: error: two or more data types in 
declaration specifiers
/usr/src/contrib/obj/osprey/../../x86_open64-4.5.2.1-1/osprey/linux/make/gcommonrules:148: 
recipe for target 'concat.o' failed

gmake[2]: *** [concat.o] Error 1
gmake[2]: Leaving directory 
'/usr/src/contrib/obj/osprey/targdir/libiberty'

Makefile:205: recipe for target 'libiberty' failed
gmake[1]: *** [libiberty] Error 2
gmake[1]: Leaving directory '/usr/src/contrib/obj'
Makefile:340: recipe for target 'build' failed
gmake: *** [build] Error 2
8.01 real 6.34 user 0.57 sys



A bit of poking around yields a 'typedef  __uintptr_t uintptr_t;' 
statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t 
isn't defined anywhere  Any clues ? TIA & have a good one.






*C'mon*  Someone throw me a bone :-). Whassup here, this can't be 
the 1st time this has happened  where is __uintptr_t 
defined/typedef'ed ?



--

William A. Mahaffey III

 --

  

Re: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/10/16 18:57, William A. Mahaffey III wrote:

On 04/10/16 18:09, Peter Jeremy wrote:
On 2016-Apr-10 17:09:04 -0453, "William A. Mahaffey III" 
 wrote:

configure process completed OK, but created a Makefile w/ what seems to
be a bunch of linuxisms in conditionals to allow compilation for
different architectures, see attached orig-Makefile.

Have you tried using gmake, rather than the base make?




OK, I tried gmake & got the attached, lotta '#include malloc.h' all 
over the place, I'll have to handle that file-by-file :-/ 




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



OK fixed the above w/ find & sed, now I have:


.
.
.
.

In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/objects.c:59:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function
C 
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c
In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c:69:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c: In function 
'run_ar':
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c:3144: warning: 
implicit declaration of function 'get_executable_dir_from_path'
../../../../x86_open64-4.5.2.1-1/osprey/driver/phases.c:3144: warning: 
initialization makes pointer from integer without a cast
C 
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/run.c
In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/run.c:86:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function
C 
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/special_options.c
In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/special_options.c:63:
./option_names.h:944: warning: built-in function 'fma' declared as 
non-function

GENversion_hg.c
C  /usr/src/contrib/obj/osprey/targdir/driver/version_hg.c
LD /usr/src/contrib/obj/osprey/targdir/driver/driver
file_names.o: In function `get_object_file':
file_names.c:(.text+0xe57): warning: warning: tempnam() possibly used 
unsafely; consider using mkstemp()

gmake[3]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
gmake last
gmake[3]: Entering directory '/usr/src/contrib/obj/osprey/targdir/driver'
hg: not found
rm -f opencc openCC openf90
ln -s driver opencc
ln -s driver openCC
ln -s driver openf90
gmake[3]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
gmake[2]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
gmake -C osprey/targdir/libiberty
gmake[2]: Entering directory '/usr/src/contrib/obj/osprey/targdir/libiberty'
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/alloca.c
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/argv.c
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/choose-temp.c
C 
/usr/src/contrib/obj/osprey/targdir/libiberty/../../../../x86_open64-4.5.2.1-1/osprey/libiberty/concat.c

In file included from /usr/include/sys/types.h:63,
 from 
../../../../x86_open64-4.5.2.1-1/osprey/libiberty/concat.c:52:
/usr/include/sys/_stdint.h:78: error: two or more data types in 
declaration specifiers
/usr/include/sys/_stdint.h:78: error: two or more data types in 
declaration specifiers
/usr/src/contrib/obj/osprey/../../x86_open64-4.5.2.1-1/osprey/linux/make/gcommonrules:148: 
recipe for target 'concat.o' failed

gmake[2]: *** [concat.o] Error 1
gmake[2]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/libiberty'
Makefile:205: recipe for target 'libiberty' failed
gmake[1]: *** [libiberty] Error 2
gmake[1]: Leaving directory '/usr/src/contrib/obj'
Makefile:340: recipe for target 'build' failed
gmake: *** [build] Error 2
8.01 real 6.34 user 0.57 sys



A bit of poking around yields a 'typedef  __uintptr_t uintptr_t;' 
statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t 
isn't defined anywhere  Any clues ? TIA & have a good one.



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/11/16 07:04, Torsten Zuehlsdorff wrote:

On 11.04.2016 03:32, William A. Mahaffey III wrote:

On 04/10/16 20:22, Warren Block wrote:

On Sun, 10 Apr 2016, William A. Mahaffey III wrote:


Or set the (g)make variable 'MAKE' to gmake & let it propogate 


What you are doing is, in effect, creating a port.  If you create a
real port, there are numerous tools to deal with just this sort of
problem, like USES=gmake.

The Porter's Handbook describes the whole process of creating a port:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
___
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"





I wasn't planning to go that far to start with, but that could change. I
am having to edit a largish # of the source files to comment out
'#include ' lines, is there a way to automate that for
port/pkg maintenance ? I haven't reviewed the porters-handbook (yet),
but I have hit that snag to start with 


If everything is the same: try sed. :)

Greetings,
Torsten




That's what I did, I was asking if there is some infrastructure in the 
ports system to automate that sort of stuff for port-maintenance 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/10/16 20:22, Warren Block wrote:

On Sun, 10 Apr 2016, William A. Mahaffey III wrote:


Or set the (g)make variable 'MAKE' to gmake & let it propogate 


What you are doing is, in effect, creating a port.  If you create a 
real port, there are numerous tools to deal with just this sort of 
problem, like USES=gmake.


The Porter's Handbook describes the whole process of creating a port: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/

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




I wasn't planning to go that far to start with, but that could change. I 
am having to edit a largish # of the source files to comment out 
'#include ' lines, is there a way to automate that for 
port/pkg maintenance ? I haven't reviewed the porters-handbook (yet), 
but I have hit that snag to start with 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/10/16 19:05, Mehmet Erol Sanliturk wrote:

On Sun, Apr 10, 2016 at 4:10 PM, William A. Mahaffey III 
wrote:


On 04/10/16 18:09, Peter Jeremy wrote:


On 2016-Apr-10 17:09:04 -0453, "William A. Mahaffey III" 
wrote:


configure process completed OK, but created a Makefile w/ what seems to
be a bunch of linuxisms in conditionals to allow compilation for
different architectures, see attached orig-Makefile.


Have you tried using gmake, rather than the base make?



H  No, I didn't :-/  Did I mention pilot error ? I thought the
system make was a version of gmake, but apparently not, right ? Thanks,
I'll try that & see how it goes ....

--

 William A. Mahaffey III

  --

 "The M1 Garand is without doubt the finest implement of war
  ever devised by man."
-- Gen. George S. Patton Jr.

___



FreeBSD make and GNU make are different species ( means not compatible ) .


If you compare building of GCC in FreeBSD and Linux , you may model
building of Open64 in FreeBSD with respect to building in Linux .


If I were you , I would not work on Open64 because GCC is much better than
Open64 with respect to my opinion . In Linux , I have checked Open64 for
using it , but I have abandoned that idea , because at least it does not
have 128 bit floating point numbers ( if it is not included yet ) .


I have tried GCC & found it wanting, that's why I am looking for an 
alternative 





It may be said that it is abandoned :


https://en.wikipedia.org/wiki/Open64
http://developer.amd.com/tools-and-sdks/cpu-development/x86-open64-compiler-suite/


https://sourceforge.net/projects/open64/

https://sourceforge.net/projects/open64/files/open64/
https://sourceforge.net/projects/open64/files/open64/Open64-5.0/


http://www.open64.net/

Mehmet Erol Sanliturk
___
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"




I *think* AMD is still plodding along w/ their version, not certain of 
that 



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/10/16 19:09, Mehmet Erol Sanliturk wrote:

On Sun, Apr 10, 2016 at 4:50 PM, William A. Mahaffey III 
wrote:


On 04/10/16 18:09, Peter Jeremy wrote:


On 2016-Apr-10 17:09:04 -0453, "William A. Mahaffey III" 
wrote:


configure process completed OK, but created a Makefile w/ what seems to
be a bunch of linuxisms in conditionals to allow compilation for
different architectures, see attached orig-Makefile.


Have you tried using gmake, rather than the base make?



OK, I tried gmake & got the attached, lotta '#include malloc.h' all over
the place, I'll have to handle that file-by-file :-/ 

--

 William A. Mahaffey III

  --

 "The M1 Garand is without doubt the finest implement of war
  ever devised by man."
-- Gen. George S. Patton Jr.


___




Important problem here is the following :


In make files , there are other references to "make" commands , means ,
even you started from gmake , at the next make invocation , it will invoke
the FreeBSD make .

Therefore , you need to use a jail and replace the FreeBSD make with gmake
, or , by traversing all of the make files , replace "make" invocations by
"gmake" .


Mehmet Erol Sanliturk
___
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"




Or set the (g)make variable 'MAKE' to gmake & let it propogate 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/10/16 18:09, Peter Jeremy wrote:

On 2016-Apr-10 17:09:04 -0453, "William A. Mahaffey III"  
wrote:

configure process completed OK, but created a Makefile w/ what seems to
be a bunch of linuxisms in conditionals to allow compilation for
different architectures, see attached orig-Makefile.

Have you tried using gmake, rather than the base make?




OK, I tried gmake & got the attached, lotta '#include malloc.h' all over 
the place, I'll have to handle that file-by-file :-/ 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

 
Beginning background gmake all
Initiated at 06:19:22 PM MCDT on Sunday, April 10, 2016
 
gmake first
gmake[1]: Entering directory '/usr/src/contrib/obj'
gmake[1]: Nothing to be done for 'first'.
gmake[1]: Leaving directory '/usr/src/contrib/obj'
gmake phony_targets 
gmake[1]: Entering directory '/usr/src/contrib/obj'
gmake -C osprey/targdir/include
gmake[2]: Entering directory '/usr/src/contrib/obj/osprey/targdir/include'
echo '#ifndef __pathscale_defs_h' > pathscale_defs.h
echo '#define __pathscale_defs_h' >> pathscale_defs.h
echo '#define OPEN64_NAME_PREFIX "open"' >> pathscale_defs.h
echo '#define OPEN64_MAJOR_VERSION_NUM 4' >> pathscale_defs.h
echo '#define OPEN64_MINOR_VERSION_NUM 5' >> pathscale_defs.h
echo '#define OPEN64_MAJOR_VERSION "4"' >> pathscale_defs.h
echo '#define OPEN64_MINOR_VERSION "5"' >> pathscale_defs.h
echo '#define OPEN64_FULL_VERSION "4.5.2.1"' >> pathscale_defs.h
echo '#define OPEN64_GCC_VERSION "3.3.1"' >> pathscale_defs.h
echo '#define OPEN64_GCC40_VERSION "4.0.2"' >> pathscale_defs.h
echo '#define OPEN64_GCC42_VERSION "4.2.0"' >> pathscale_defs.h
echo '#define OPEN64_INSTALL_PREFIX "/usr"' >> pathscale_defs.h
echo '#define OPEN64_TARGET ""' >> pathscale_defs.h
echo '#define OPEN64_PATCH_LEVEL "2.1"' >> pathscale_defs.h 
echo "#endif" >> pathscale_defs.h
Making sys
Making cmplrs
Making libelf
test: -a: unexpected operator
test: -a: unexpected operator
test: -a: unexpected operator
test: -a: unexpected operator
gmake[2]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/include'
gmake -C osprey/targdir/driver
gmake[2]: Entering directory '/usr/src/contrib/obj/osprey/targdir/driver'
hg: not found
gmake first
gmake[3]: Entering directory '/usr/src/contrib/obj/osprey/targdir/driver'
hg: not found
gmake[3]: Nothing to be done for 'first'.
gmake[3]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
gmake driver
gmake[3]: Entering directory '/usr/src/contrib/obj/osprey/targdir/driver'
hg: not found
C  
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/errors.c
C  
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/file_utils.c
C  
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/lang_defs.c
C  
/usr/src/contrib/obj/osprey/targdir/driver/../../../../x86_open64-4.5.2.1-1/osprey/driver/string_utils.c
In file included from 
../../../../x86_open64-4.5.2.1-1/osprey/driver/string_utils.c:43:
/usr/include/malloc.h:3:2: error: #error " has been replaced by 
"
/usr/src/contrib/obj/osprey/../../x86_open64-4.5.2.1-1/osprey/linux/make/gcommonrules:148:
 recipe for target 'string_utils.o' failed
gmake[3]: *** [string_utils.o] Error 1
gmake[3]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
../../../../x86_open64-4.5.2.1-1/osprey/driver/Makefile.gbase:225: recipe for 
target 'default' failed
gmake[2]: *** [default] Error 2
gmake[2]: Leaving directory '/usr/src/contrib/obj/osprey/targdir/driver'
Makefile:229: recipe for target 'driver' failed
gmake[1]: *** [driver] Error 2
gmake[1]: Leaving directory '/usr/src/contrib/obj'
Makefile:340: recipe for target 'build' failed
gmake: *** [build] Error 2
0.52 real 0.29 user 0.23 sys
 
Completed at 06:19:23 PM MCDT on Sunday, April 10, 2016
___
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: 'porting' AMD compiler suite

[William A. Mahaffey III]

On 04/10/16 18:09, Peter Jeremy wrote:

On 2016-Apr-10 17:09:04 -0453, "William A. Mahaffey III"  
wrote:

configure process completed OK, but created a Makefile w/ what seems to
be a bunch of linuxisms in conditionals to allow compilation for
different architectures, see attached orig-Makefile.

Have you tried using gmake, rather than the base make?




H  No, I didn't :-/  Did I mention pilot error ? I thought 
the system make was a version of gmake, but apparently not, right ? 
Thanks, I'll try that & see how it goes ....


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

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

'porting' AMD compiler suite

[William A. Mahaffey III]

I downloaded the AMD Open64 compiler suite & am attempting to build it 
to compile some in-house code under FreeBSD. I unpacked the tarball & 
began following directions in the INSTALL file, which I attach. The 
configure process completed OK, but created a Makefile w/ what seems to 
be a bunch of linuxisms in conditionals to allow compilation for 
different architectures, see attached orig-Makefile. I read the man page 
for make & attempted to convert these to FreeBSD legal text & tried my 
'make all' again. It failed w/ different & somewhat obscure error 
message, so I tried again w/ 'make -vvv -d all' & got the attached 
output in 'LIST', see attached. The compiler is not necessarily known to 
compile under FreeBSD, so I may be whiffing here, but I think this may 
just be a bit of pilot error using the GNU utilities. I am stumped for 
now, any clues appreciated. I also attach my 'fixed' Makefile. The LIST 
file has info on make version & other stuff.



[root@devbox, obj, 5:02:37pm] 937 % uname -a
FreeBSD devbox 9.3-RELEASE-p33 FreeBSD 9.3-RELEASE-p33 #0: Wed Jan 13 
17:55:39 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64

[root@devbox, obj, 5:06:26pm] 938 % which make
/usr/bin/make
[root@devbox, obj, 5:06:31pm] 939 %


Again, I am stumped for now, any help appreciated. TIA * have a good one.


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

Installing Open64
=

Introduction


This document explains how to compile and install x86 Open64 compiler from 
source on an x86-64 based system.For simplicity, we describe the steps 
that we used to build the x86 Open64 4.5.2.1 binary packages available 
on http://developer.amd.com/cpu/open64.



Open64 and external package dependency 
--

Minimal external packages/tools dependency for using open64 compiler 
  glibc   - release and devel packages supporting 64 bit and 32 bit ISA 
 
  libgcc  - 32 bit, 64 bit packages 
  libstdc++   - 32 bit, 64 bit packages 
   
Minimal external packages/tools dependency for building open64 compiler from 
source 
  gcc,g++,gfortran
  bison
  flex
  glibc-devel.x86_64
  glibc-devel.i686
  libgcc.i686

To fully leverage the AMD Opteron Family 15h processor("Piledriver"core)
features use binutils-2.21.51.0.6 or above.Newer OS versions like 
SLES 11 SP2 and RHEL 6.3 come with GLIBC and Binutils which have support 
for AMD Opteron Family 15h processor("Piledriver"core).

We used 64-bit SUSE Linux Enterprise Server 11 with SP1 and with required 
binutils to build the compiler for AMD Opteron Family 15h processor 
("Piledriver" core).Besides, we used 64-bit SUSE Linux Enterprise Server 10
with SP2 to build the compiler for systems that does not comply to the above
mentioned Binutils version. 

Note: 
If a open64 build from source attempted without the above recommended 
binutils on a machine with AMD Opteron Family 15h processor
("Piledriver"core) then the compiler build may not get completed 
as expected.
  

Build open64 from source 


Although the x86 Open64 compiler suite can be built on 32-bit or 64-bit
Linux systems, we always build on a 64-bit Linux system where both 32-bit
and 64-bit code generation can be tested. 

By default, on x86_64 machines, the compiler will be built in 64 bit
mode and libraries will be built in 32 and 64 bit modes to support
compilation in either mode

By default, the build process will use GCC to build most compiler
components. We used GCC 4.1.2 as provided with SLES 10 SP2 and GCC 4.3.4 as 
provided with SLES 11 SP1. 

  
Following the below simple steps helps in building open64 for AMD x86_64

 - Unpack the source (assume that the source package has been extracted as
   x86_open64-4.5.2.1-1)
tar xjvf x86_open64-4.5.2.1-1.src.tar.bz2

 - Create object directory at the same level where src has been extracted
mkdir obj 
cd obj 


 - Configure stage
   A compiler built on either x86-64 or x86 machine will target both
   architectures.  

   By default the compiler will get built for x86_64-unknown-linux-gnu, it can 
also 
   be forced using the below option 

--build=x86_64-unknown-linux-gnu
   
   To build a compiler on an x86-64 machine that is compiled with the x86 ISA
   (that is, compiled with the -m32 option), specify the following configuration
   option:

--build=i686-unknown-linux-gnu

   Select one of the below step based on your need/environment for building a
   x84_64 compiler
* For all binutils
..

Re: Removing documentation

[William A. Mahaffey III]

On 02/12/16 09:42, Matthew Seaman wrote:

On 12/02/2016 14:56, Jim Ohlstein wrote:

This is a good point. I still don't understand why pkg(8) is not in the
base (though I imagine there's a reason and it takes less than a minute
to install). There can't be many users who install a base system and use
it without a single additional piece of software. However, for my $0.02,
that is the only change I'd make to base at this point with respect to
package management, aside from my pkg(8) wishlist. As an aside, and
fwiw, unless there is a non-GPL'd Ada compiler out there, we won't see
Ada or any Ada-based binaries in base, even if Synth turns out to be the
best thing since sliced bread.

The primary reason pkg(8) is not in base is to decouple it from the
FreeBSD release timescale.  Given the promises about API/ABI stability
over a major release branch, development of pkg(8) would be forced to
slow to a crawl.

pkg(8) still has a lot of changes yet to be realized, both in its own
code, and in the code of both the ports and the base system, and in
adjunct software like poudriere or indeed, synth, so it is likely to
remain a 'port' for some time to come.  It is not completely
inconceivable though that at some future point, pkg(8) will have matured
into stability and require little further development, in which case,
importing it to base would be a natural next move.

Cheers,

Matthew



There was a thread a month or 2 back that mentioned adopting the pkg 
'package format' for binary base packages. This would at least unify 
base & userland binaries under 1 package management system (& I *love* 
freebsd-update, BTW, *NO* aspersions being cast here). As I understand 
things, there would be separate repo's for base (obviously) & userland, 
but 1 unified format/package-manager. For those wanting to compile 
either base or userland themselves, they still could, since pkg is 
reasonably 'port' aware (& hopefuly could be made /usr/src aware as 
well), & they could use whatever src-base/port management tools they 
wanted. I definitely agree that a well integrated ability to possibly 
mix locally compiled stuff w/ repo-binaries is quite desirable in many 
scenarios & a nice advantage for FreeBSD. $0.02 from the (*very*) cheap 
seats, no more, no less 



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: Removing documentation

[William A. Mahaffey III]

On 02/11/16 14:15, Royce Williams wrote:

On Thu, Feb 11, 2016 at 10:33 AM, John Marino  wrote:

On 2/11/2016 8:25 PM, Lev Serebryakov wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 07.02.2016 17:28, John Marino wrote:


ports-mgmt/synth.  I would love to hear what signficant thing
portmaster can do that Synth can't.  (honestly)

  Be installed FROM PORTS without all this build-one-more-gcc stuff.
Ada? For *port*management* tool? Are you joking?

Let me guess.  You've spent actually 0.0 nanoseconds preparing on the
subject before providing this enlightened take for the list.


Having read the entire thread, separate from the relative merits of
Synth, the core of Lev's incredulity isn't that off the mark.

On the face of it, Synth requiring ncurses seems reasonable ... but
its Ada dependency is a bit of a mild POLA violation.

Don't get me wrong -- I actually think Ada is pretty cool, and Lev
could have been nicer about it ;), but he's essentially right.

People's instincts are that software management is core functionality,
and should have few unusual dependencies.

My earlier side-thread point stands.  FreeBSD software management is
fragmented.  Until that is resolved, a lot of time and effort will be
wasted treating the symptoms.

Royce



Preach it *LOUD*, brother :-)  (fragmented package management)


For my , that is about *all* RH & Debian have going for them, but 
yum/RPM et al cover up a multitude of other sins 



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: Removing documentation

[William A. Mahaffey III]

On 02/09/16 09:56, Royce Williams wrote:

IMO, this entire thread is masking a deeper symptom: FreeBSD
ports/packages management is fragmented.

Each unofficial tool treats some symptoms well, and others poorly.
The fact that I have to use the phrase "ports/packages" is indicative
of a deep schizophrenia.

Don't get me wrong -- I love the flexibility of choosing a package or
a port.  And I'm all for having choices.  But people should not be
choosing ways to manage core software management functions.

Ideally, users could choose among different UIs/wrappers around the
core of a port/package management system.  The things that each tool
has to do -- the database of current installs, dependency management,
etc. -- should not be reinvented by each tool.  They should be shared
infrastructure that is part of the OS (like Debian's dpkg/apt system).

A unified framework:

* would make it easy for small-scale admins to install basic packages
with sane defaults

* would resolve dependencies sanely

* would allow software maintainers to capture the manual steps
currently stored in /usr/ports/UPDATING, and apply them in an
automated/guided fashion

* would support building and distributing your own packages

* would be part of the base OS and documented accordingly


Until this fragmentation is resolved , we'll be having this discussion
every few months, users will keep shooting themselves in the foot ...
and keep being incented to go elsewhere.

We need to capture users' reasons for preferring specific frameworks,
and build a roadmap to how they could be unified.

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



*Huzzah*  I hereby 2nd that motion (from the cheap seats) :-) 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: tor logging

[William A. Mahaffey III]

On 02/08/16 23:51, Kevin Oberman wrote:
On Mon, Feb 8, 2016 at 9:16 PM, William A. Mahaffey III 
mailto:w...@hiwaay.net>> wrote:


On 02/08/16 15:52, Polytropon wrote:

On Mon, 8 Feb 2016 15:36:58 -0553.75, William A. Mahaffey III
wrote:

My torrc
files seems to indicate logging to /usr/local/var/log/tor,
but no such
file or directory.

Create this directory subtree and an empty log file. Then check
if it will actually be used for logging - if that is what the
torrc file indicates. Otherwise, set a different logging file,
but make sure it does actually exist.




Further review seems to indicate use of the built-in syslog system:

[root@kabini1, /etc, 11:17:03pm] 477 % grep log
/usr/local/etc/tor/torrc
## may provide sensitive information to an attacker who obtains
the logs.
## Send all messages of level 'notice' or higher to
/usr/local/var/log/tor/notices.log
#Log notice file /usr/local/var/log/tor/notices.log
## Send every possible message to /usr/local/var/log/tor/debug.log
#Log debug file /usr/local/var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
[root@kabini1, /etc, 11:17:08pm] 478 % grep log
/usr/local/etc/tor/torrc.default
## may provide sensitive information to an attacker who obtains
the logs.
## Send all messages of level 'notice' or higher to
/usr/local/var/log/tor/notices.log
#Log notice file /usr/local/var/log/tor/notices.log
## Send every possible message to /usr/local/var/log/tor/debug.log
#Log debug file /usr/local/var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
Log notice syslog
[root@kabini1, /etc, 11:17:10pm] 479 % lltr /var/log/tor*
-rw-r-  1 _tor  _tor  230140 Jan 21  2015 /var/log/tor.4.bz2
-rw-r-  1 _tor  _tor  122109 Feb 23  2015 /var/log/tor.3.bz2
-rw-r-  1 _tor  _tor  126723 Mar 30  2015 /var/log/tor.2.bz2
-rw-r-  1 _tor  _tor  147674 May 28  2015 /var/log/tor.1.bz2
-rw-r-  1 _tor  _tor  166094 Dec  3 00:06 /var/log/tor.0.bz2
[root@kabini1, /etc, 11:17:19pm] 480 %

In the past (before last upgrade) tor logged to a file in
/var/log, see above. Afterward,  There was a directory named
/var/log/tor, owned _tor:_tor, but it was empty & I removed it
after a week or so & re-created it & restarted tor. It restarts OK
& seems to be working OK, just no logging. Has the amount of
logging changed from a couple of months ago ?

-- 


William A. Mahaffey III


See UPDATING 20160119: AFFECTS: users of security/tor, security/tor-devel
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com <mailto:rkober...@gmail.com>
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683



Thanks, I *always* forget to look @ that file :-/  Back up & running 
& logging :-) 



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: tor logging

[William A. Mahaffey III]

On 02/08/16 15:52, Polytropon wrote:

On Mon, 8 Feb 2016 15:36:58 -0553.75, William A. Mahaffey III wrote:

My torrc
files seems to indicate logging to /usr/local/var/log/tor, but no such
file or directory.

Create this directory subtree and an empty log file. Then check
if it will actually be used for logging - if that is what the
torrc file indicates. Otherwise, set a different logging file,
but make sure it does actually exist.





Further review seems to indicate use of the built-in syslog system:

[root@kabini1, /etc, 11:17:03pm] 477 % grep log /usr/local/etc/tor/torrc
## may provide sensitive information to an attacker who obtains the logs.
## Send all messages of level 'notice' or higher to 
/usr/local/var/log/tor/notices.log

#Log notice file /usr/local/var/log/tor/notices.log
## Send every possible message to /usr/local/var/log/tor/debug.log
#Log debug file /usr/local/var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
[root@kabini1, /etc, 11:17:08pm] 478 % grep log 
/usr/local/etc/tor/torrc.default

## may provide sensitive information to an attacker who obtains the logs.
## Send all messages of level 'notice' or higher to 
/usr/local/var/log/tor/notices.log

#Log notice file /usr/local/var/log/tor/notices.log
## Send every possible message to /usr/local/var/log/tor/debug.log
#Log debug file /usr/local/var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
Log notice syslog
[root@kabini1, /etc, 11:17:10pm] 479 % lltr /var/log/tor*
-rw-r-  1 _tor  _tor  230140 Jan 21  2015 /var/log/tor.4.bz2
-rw-r-  1 _tor  _tor  122109 Feb 23  2015 /var/log/tor.3.bz2
-rw-r-  1 _tor  _tor  126723 Mar 30  2015 /var/log/tor.2.bz2
-rw-r-  1 _tor  _tor  147674 May 28  2015 /var/log/tor.1.bz2
-rw-r-  1 _tor  _tor  166094 Dec  3 00:06 /var/log/tor.0.bz2
[root@kabini1, /etc, 11:17:19pm] 480 %

In the past (before last upgrade) tor logged to a file in /var/log, see 
above. Afterward,  There was a directory named /var/log/tor, owned 
_tor:_tor, but it was empty & I removed it after a week or so & 
re-created it & restarted tor. It restarts OK & seems to be working OK, 
just no logging. Has the amount of logging changed from a couple of 
months ago ?


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

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

tor logging

[William A. Mahaffey III]

I updated my FreeBSD 9.3R desktop last week (pkg upgrade -y), which 
included upgrading tor. Since then, I have *NO* messages that I can 
locate for tor. It used to log to /var/log/tor, but no more. My torrc 
files seems to indicate logging to /usr/local/var/log/tor, but no such 
file or directory. Where is tor logging itself these days ? TIA & have a 
good one.


BTW:

[root@kabini1, /etc, 3:30:31pm] 467 % uname -a
FreeBSD kabini1.local 9.3-RELEASE-p33 FreeBSD 9.3-RELEASE-p33 #0: Wed 
Jan 13 17:55:39 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64

[root@kabini1, /etc, 3:36:08pm] 468 %


tor-0.2.7.6_1 (upgraded last week), torsocks-2.1.0 (didn't upgrade)


--

    William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: rxvt question

[William A. Mahaffey III]

On 02/04/16 17:13, William A. Mahaffey III wrote:

On 02/04/16 15:42, A.J. "Fonz" van Werven wrote:

William A. Mahaffey III wrote:


( rxvt -sl 5000 -fn
-*-lucidatypewriter-bold-r-normal-sans-17-*-100-100-*-100-*-* & )
[wam@kabini1, ~, 10:18:43am] 303 % rxvt: No match.

Try escaping the asterisks in the font string.

HTH,

Fonz




*DING DING DING DING*  We have a winner  Thanks :-)


P.S. Damn I hate it when I do stuff like that 





& to close this off properly, the '-maximized' argument is no longer 
recognized by rxvt (used to work AOK :-/ ), which was messing up my 
invocation from the XFCE menu. *Whew* 



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: rxvt question

[William A. Mahaffey III]

On 02/04/16 15:42, A.J. "Fonz" van Werven wrote:

William A. Mahaffey III wrote:


( rxvt -sl 5000 -fn
-*-lucidatypewriter-bold-r-normal-sans-17-*-100-100-*-100-*-* & )
[wam@kabini1, ~, 10:18:43am] 303 % rxvt: No match.

Try escaping the asterisks in the font string.

HTH,

Fonz




*DING DING DING DING*  We have a winner  Thanks :-)


P.S. Damn I hate it when I do stuff like that 

--

    William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

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

rxvt question

[William A. Mahaffey III]

I have been using rxvt w/ XFCE under FreeBSD 9.3R for CLI tasks on my 
daily-driver desktop for about 18 mos. now, love it. Since I use this 
box for web access as well as LAN access to other boxen on my LAN, it 
doesn't get refreshed very often, since I like the continuity of being 
able to return to tasks by just clicking back to the window I was 
working in earlier. I always have 4 desktops, with about a dozen RXVT 
shells each open in 2 of the desktops, sometimes a few more, usually a 
few xterms as well. The other 2 desktops are used for GUI stuff, 
browsers, e-mail client, etc.


I did a full system upgrade this A.M. (freebsd-update + 'pkg upgrade 
-y') & rebooted & logged back in. I have noticed over the last few 
months that whenever I log out & back in, most of the RXVT windows are 
re-opened as they were when I logged out, fonts OK, text rendered OK, 
etc., but some are recreated in an oddball state such that when I open 
them up to full screen size, they still render text in only about 70 
columns, rather than full 132-ish. I usually just shut those windows & 
open new ones, since I always use them 'full screen'. This A.M., when I 
clicked on the 'RXVT shell' button on my desktop lower menu, nothing 
happened. I tried from the CLI of another open shell & same story:



[wam@kabini1, ~, 10:17:07am] 301 % hrxvt
   107  9:00( rxvt -sl 5000 -fn 
-*-lucidatypewriter-bold-r-normal-sans-17-*-100-100-*-100-*-* & )

   108  9:00( rxvt -rv & )
   109  9:00rxvt -sl 5000 -title "System Terminal" -fg red -bg 
darkred -e su -l root
   110  9:00rxvt -sl 5000 -title "System Terminal" -fg red -bg 
black -e su -l root

   301  10:18   hrxvt
[wam@kabini1, ~, 10:18:35am] 302 % !107
( rxvt -sl 5000 -fn 
-*-lucidatypewriter-bold-r-normal-sans-17-*-100-100-*-100-*-* & )

[wam@kabini1, ~, 10:18:43am] 303 % rxvt: No match.

[wam@kabini1, ~, 10:18:46am] 303 %
[wam@kabini1, ~, 10:18:46am] 303 %
[wam@kabini1, ~, 10:18:46am] 303 % which rxvt
/usr/local/bin/rxvt
[wam@kabini1, ~, 10:18:51am] 304 % ( /usr/local/bin/rxvt -sl 5000 -fn 
-*-lucidatypewriter-bold-r-normal-sans-17-*-100-100-*-100-*-* & )

[wam@kabini1, ~, 10:19:06am] 305 % /usr/local/bin/rxvt: No match.

[wam@kabini1, ~, 10:19:07am] 305 %
[wam@kabini1, ~, 10:19:07am] 305 %
[wam@kabini1, ~, 10:19:08am] 305 %


These lines were typed in *after* I tried the menu button on my XFCE 
desktop. I only log out & back in as needed, often many weeks or months 
between logins, so I am not sure exactly when this might have started :-/.



[wam@kabini1, ~, 10:19:08am] 305 % uname -a
FreeBSD kabini1.local 9.3-RELEASE-p33 FreeBSD 9.3-RELEASE-p33 #0: Wed 
Jan 13 17:55:39 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64

[wam@kabini1, ~, 2:50:46pm] 306 %


rxvt-2.6.4_6, xfce-4.12_1, everything fresh as of this A.M. Is rxvt 
still actively maintained ? Known/thought to work OK w/ XFCE ? Any other 
issues/gotchas ? Pilot error ? Any clues appreciated, any info needed 
just ask. TIA & have a good one.



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: [moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

On 02/04/16 02:23, Torsten Zuehlsdorff wrote:

On 03.02.2016 22:03, William A. Mahaffey III wrote:


*Eek* (RTFM), I use pkg by default, ports only when necessary
(graphite for gcc5, flash for firefox/opera, etc.), so I am not as
familiar w/ ports ai I should be :-/ 


If you need individual options for ports more often for more than one 
pc have a look at poudriere.


I have a poudriere server building all my pkg-packages with the 
different options my different servers need. This allows me to stay 
with pkg at the single server and have full flexibility in management 
of my ports.


Greetings,
Torsten




Roger that, for now I will stay where I am, all I need on that box 
(dev-box) is gcc5+graphite. I need flash (only) on this box (daily 
driver), might need some other stuff in the future, I'll look @ 
poudriere then. Thanks.



--

    William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: [moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

On 02/03/16 10:40, Freddie Cash wrote:
On Wed, Feb 3, 2016 at 6:59 AM, William A. Mahaffey III 
mailto:w...@hiwaay.net>>wrote:


On 02/03/16 08:49, Torsten Zuehlsdorff wrote:


On 03.02.2016 15:18, William A. Mahaffey III wrote:

When I checked the port w/ make showconfig. it shows
graphite enabled.


make showconfig shows the configuration at your *local*
portstree. It does not affect or display the settings of pkg.

To check the configuration of "pkg-ports" perform a:
$ pkg info gcc5

Greetings,
Torsten
___
freebsd-ports@freebsd.org <mailto: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
<mailto:freebsd-ports-unsubscr...@freebsd.org>"



Thanks. Where is the local portstree info stored ? My local (newly
updated) ports gcc5-devel shows graphite enabled (see previous
response), I thought a 'portsnap fetch update' would overwrite
that, no ? Thanks (again) & TIA & have a good one 


​/var/db/ports​//options

That's the file that is read when you run "make showconfig" in a port 
directory.  If the file doesn't exist, then it shows the default 
options from the Makefile.


"make rmconfig" will remove that saved options file.  Then a "make 
showconfig" will show you the default options for the port.


This is all detailed in "man ports".  :)


--
Freddie Cash
fjwc...@gmail.com <mailto:fjwc...@gmail.com>



*Eek* (RTFM), I use pkg by default, ports only when necessary 
(graphite for gcc5, flash for firefox/opera, etc.), so I am not as 
familiar w/ ports ai I should be :-/ 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: [moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

On 02/03/16 09:45, Torsten Zuehlsdorff wrote:

On 03.02.2016 15:59, William A. Mahaffey III wrote:

On 02/03/16 08:49, Torsten Zuehlsdorff wrote:


On 03.02.2016 15:18, William A. Mahaffey III wrote:

When I checked the port w/ make showconfig. it shows graphite enabled.


make showconfig shows the configuration at your *local* portstree. It
does not affect or display the settings of pkg.

To check the configuration of "pkg-ports" perform a:
$ pkg info gcc5



Thanks. Where is the local portstree info stored ? My local (newly
updated) ports gcc5-devel shows graphite enabled (see previous
response), I thought a 'portsnap fetch update' would overwrite that, no
? Thanks (again) & TIA & have a good one 


It is in: /var/db/ports

This isn't affected by portsnap.

Greetings,
Torsten
___
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"




Thanks that clarifies all :-).


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: [moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

On 02/03/16 09:18, Chris H wrote:

Hello, William. On a side note; I can't help but notice
that your mail always reports it was written on:
Date:   Wed, 31 Dec 1969 16:00:00 -0800(Unknown)
Is your clock working as intended?

--Chris



Yes, I have my local LAN timezones set to make my LAN time coincide w/ 
my wall clocks, which are about 6 min. fast (375 sec. actually), keeps 
me punctual :-) 



--

    William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: [moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

On 02/03/16 08:49, Torsten Zuehlsdorff wrote:


On 03.02.2016 15:18, William A. Mahaffey III wrote:

When I checked the port w/ make showconfig. it shows graphite enabled.


make showconfig shows the configuration at your *local* portstree. It 
does not affect or display the settings of pkg.


To check the configuration of "pkg-ports" perform a:
$ pkg info gcc5

Greetings,
Torsten
___
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"




Thanks. Where is the local portstree info stored ? My local (newly 
updated) ports gcc5-devel shows graphite enabled (see previous 
response), I thought a 'portsnap fetch update' would overwrite that, no 
? Thanks (again) & TIA & have a good one 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: [moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

On 02/03/16 08:49, Torsten Zuehlsdorff wrote:


On 03.02.2016 15:18, William A. Mahaffey III wrote:

When I checked the port w/ make showconfig. it shows graphite enabled.


make showconfig shows the configuration at your *local* portstree. It 
does not affect or display the settings of pkg.


To check the configuration of "pkg-ports" perform a:
$ pkg info gcc5

Greetings,
Torsten
___
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"



Thanks, I replied elsewhere that it was gcc5-devel, pilot error. However:


[root@devbox, f2c, 8:56:22am] 358 % pkg info gcc5
pkg: No package(s) matching gcc5
[root@devbox, f2c, 8:57:12am] 359 % pkg info gcc5-devel
gcc5-devel-5.3.1.s20160119
Name   : gcc5-devel
Version: 5.3.1.s20160119
Installed on   : Mon Feb  1 08:29:51 2016 MCST
Origin : lang/gcc5-devel
Architecture   : freebsd:9:x86:64
Prefix : /usr/local
Categories : lang java
Licenses   : GPLv3 and GPLv3RLE
Maintainer : ger...@freebsd.org
WWW: http://gcc.gnu.org/
Comment: GNU Compiler Collection 5
Options:
BOOTSTRAP  : on
GRAPHITE   : off
JAVA   : on
Shared Libs required:
libgmp.so.10
libmpfr.so.4
libmpc.so.3
libiconv.so.2
Shared Libs provided:
libgcj-tools.so.16
libssp.so.0
libcc1.so.0
libatomic.so.1
libgomp-plugin-host_nonshm.so.1
libcilkrts.so.5
libgij.so.16
libstdc++.so.6
libjvm.so
libitm.so.1
libgcj.so.16
libcc1plugin.so.0
libgcc_s.so.1
libquadmath.so.0
libjavamath.so
liblto_plugin.so.0
libgomp.so.1
libgfortran.so.3
libobjc.so.4
Annotations:
cpe: cpe:2.3:a:gnu:gcc:5.3.1:freebsd9:x64
repo_type  : binary
repository : FreeBSD
Flat size  : 423MiB
Description:
GCC, the GNU Compiler Collection, supports a number of languages. This
port installs the C, C++, Fortran and Java front ends as gcc5, g++5,
gfortran5, and gcj5, respectively.

WWW: http://gcc.gnu.org/

Gerald Pfeifer 
[root@devbox, f2c, 8:57:19am] 360 % which gcc5
/usr/local/bin/gcc5
[root@devbox, f2c, 8:59:56am] 361 %


i.e. pkg doesn't have anything on gcc5 (which is installed), does for 
gcc5-devel. May be nothing, I got the gcc5-devel port recompiled & 
referenced by my Makefiles, so all is back to working. My newly 
downloaded gcc5-devel port *does* show graphite enabled:



[root@devbox, gcc5-devel, 8:49:12am] 415 % pwd
/usr/ports/lang/gcc5-devel
[root@devbox, gcc5-devel, 8:49:16am] 416 % make showconfig
===> The following configuration options are available for 
gcc5-devel-5.3.1.s20160126:

 BOOTSTRAP=on: Build using a full bootstrap
 GRAPHITE=on: Support for Graphite loop optimizations
 JAVA=on: Java platform support
===> Use 'make config' to modify these settings
[root@devbox, gcc5-devel, 8:49:18am] 417 % uname -a
FreeBSD devbox 9.3-RELEASE-p33 FreeBSD 9.3-RELEASE-p33 #0: Wed Jan 13 
17:55:39 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64

[root@devbox, gcc5-devel, 8:49:20am] 418 % lltr
total 1044
-rw-r--r--  1 root  wheel   239 Aug 23  2014 pkg-descr
-rw-r--r--  1 root  wheel  2869 Sep 26 06:09 pkg-plist
-rw-r--r--  1 root  wheel   140 Jan 31 17:00 distinfo
-rw-r--r--  1 root  wheel  5342 Jan 31 17:00 Makefile
drwxr-xr-x  2 root  wheel 6 Feb  1 08:07 files/
drwxr-xr-x  5 root  wheel17 Feb  1 10:33 work/
-rw-r--r--  1 root  wheel  12158032 Feb  1 10:33 LIST
[root@devbox, gcc5-devel, 8:49:21am] 419 %



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
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: [moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

On 02/03/16 08:40, Guido Falsi wrote:

On 02/03/16 15:18, William A. Mahaffey III wrote:


I just did a full 'pkg upgrade' on my FBSD 9.3R box, which installed the
newest GCC5. I also updated ports. When I used the pkg-provided GCC5, it
doesn't have graphite support enabled, so no auto-parallelization. When
I checked the port w/ make showconfig. it shows graphite enabled. I am
recompiling it as I write this, but I thought the pkg was/is configured
from the port & would have graphite enabled by default, w/ no recompile
needed on my part, no ? I have the various other pkg's req'd for
graphite support pkg-installed (& just updated this A.M.), so I thought
I was ready to go. Not a huge issue, but recompiling the compiler shoots
about an hour on my box, would be sweet to avoid that. TIA for any clues
& have a good one.

A quick check in the ports tree shows that the GRAPHITE option isn't in
the default options for the gcc5 port. You must have enabled it in the
past on your system.

So the official package will not have that option at present.

You can try asking the maintainer for the defaults to be changed, but
the he has the last word about that.



*Aaaack*, that was gcc5-devel, sorry :-/ 


--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

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

[moved from toolchain] GCC5: pkg vs. ports

[William A. Mahaffey III]

I just did a full 'pkg upgrade' on my FBSD 9.3R box, which installed the 
newest GCC5. I also updated ports. When I used the pkg-provided GCC5, it 
doesn't have graphite support enabled, so no auto-parallelization. When 
I checked the port w/ make showconfig. it shows graphite enabled. I am 
recompiling it as I write this, but I thought the pkg was/is configured 
from the port & would have graphite enabled by default, w/ no recompile 
needed on my part, no ? I have the various other pkg's req'd for 
graphite support pkg-installed (& just updated this A.M.), so I thought 
I was ready to go. Not a huge issue, but recompiling the compiler shoots 
about an hour on my box, would be sweet to avoid that. TIA for any clues 
& have a good one.



--

William A. Mahaffey III

 --

"The M1 Garand is without doubt the finest implement of war
 ever devised by man."
   -- Gen. George S. Patton Jr.

___
freebsd-toolch...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-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"

print/cups fails to build on 9.3-STABLE i386

[William Bulley]

After running this command: "# svn update /usr/ports" I tried to
upgrade the print/cups port.

As root I then ran this command:

   # portmaster -K -B -D print/cups

Below is the output leading up to the failure and the failure itself.

BTW - I did retry the build in /usr/ports/print/cups using this:

   # make MAKE_JOBS_UNSAFE=yes install

and got the same results.

 =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

...
...
Making all in test...
gmake[1]: Entering directory '/usr/ports/print/cups-base/work/cups-1.7.3/test'
echo Linking ippserver...
Linking ippserver...
cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler -L/usr/local/lib 
-Wl,-rpath,/usr/local/lib -Wl,-R/usr/local/lib  -fPIE -pie -Wall 
-Wno-format-y2k -Wunused -fPIC -Os -g -fstack-protector -o ippserver 
ippserver.o  ../cups/libcups.a \
 -lssl -lcrypto  -pthread -lm -lcrypt -lssp_nonshared -liconv  -lz -lz
../cups/libcups.a(http-support.o): In function `_httpResolveURI':
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1617: 
undefined reference to `DNSServiceCreateConnection'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1626: 
undefined reference to `DNSServiceResolve'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1736: 
undefined reference to `DNSServiceRefDeallocate'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1656: 
undefined reference to `DNSServiceRefSockFD'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1700: 
undefined reference to `DNSServiceResolve'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1722: 
undefined reference to `DNSServiceProcessResult'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1731: 
undefined reference to `DNSServiceRefDeallocate'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:1733: 
undefined reference to `DNSServiceRefDeallocate'
../cups/libcups.a(http-support.o): In function `http_resolve_cb':
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:2071: 
undefined reference to `TXTRecordGetValuePtr'
/usr/ports/print/cups-client/work/cups-1.7.3/cups/http-support.c:2058: 
undefined reference to `TXTRecordGetValuePtr'
Makefile:192: recipe for target 'ippserver' failed
gmake[1]: *** [ippserver] Error 1
gmake[1]: Leaving directory '/usr/ports/print/cups-base/work/cups-1.7.3/test'
Makefile:31: recipe for target 'all' failed
gmake: *** [all] Error 1
*** [do-build] Error code 1

Stop in /usr/ports/print/cups-base.
*** [install] Error code 1

Stop in /usr/ports/print/cups-base.



Regards,

web...

-- 

 /"\   ASCII RIBBON  / William Bulley
 \ /   CAMPAIGN AGAINST / 
  XHTML E-MAIL AND / E-MAIL: w...@umich.edu
 / \   LISTSERV POSTINGS  /

72 characters width template ->|
___
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: py-imaging vs. py-pillow

[William Grzybowski]

On Sat, Oct 11, 2014 at 6:02 PM, Kevin Oberman  wrote:
> print/hplip is still building with py-imaging and I had to delete it to get
> py-opengl to update. I suspect that just changing "py-imaging" to
> "py-pillow" in Makefile would do the trick.

Yes, it is part of a non-default option so thats why it was not caught.
Should be fixed now, thanks.



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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: py-imaging vs. py-pillow

[William Grzybowski]

Should be fixed now, small typo in the option depends.

Thanks.

On Sat, Oct 11, 2014 at 9:59 AM, Beeblebrox  wrote:
> Build fails if tiff is enabled (py27-pillow-2.6.0)
>
> OPTIONS_FILE_SET+=TIFF
> Gives: "ValueError: --enable-tiff requested but tiff not found, aborting"
>
> Just advising in case you have not been made aware.
> Regards.
>
>
>
>
> -
> FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
> --
> View this message in context: 
> http://freebsd.1045724.n5.nabble.com/py-imaging-vs-py-pillow-tp5954043p5955962.html
> Sent from the freebsd-ports mailing list archive at Nabble.com.
> ___
> 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"



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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: graphics/graphviz conflicts with science/ghmm

[William Grzybowski]

On Mon, Oct 6, 2014 at 12:56 PM, Beeblebrox  wrote:
> This has been around for a while. Reporting now, in consideration of the
> (somewhat) related "py-imaging vs. py-pillow" problem.
>

There isn't absolutely anything point it to be a py-imaging/pillow issue.

> # pkg install ghmm >
> pkg: ghmm-0.7.0b_1 conflicts with graphviz-2.38.0_2 (installs files into the
> same place). Problematic file: /usr/local/bin/cluster
>
> Related ports reset to default and following full poudriere run.



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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: py-imaging vs. py-pillow

[William Grzybowski]

The worked is not nearly done. There are several ports still to be changed.

On Mon, Oct 6, 2014 at 11:56 AM, Beeblebrox  wrote:
> The patch does not solve the problem for me.
>
> graphics/gegl and graphics/graphviz appear to be the cause:
> Reinstalling graphviz-2.38.0_2: 100%
> Reinstalling gegl-0.2.0_10: 100%
> pkg: py27-pillow-2.6.0 conflicts with py27-imaging-1.1.7_3 (installs files
> into the same place).  Problematic file: /usr/local/bin/pilconvert.py
>
> All related ports were reset to default configurations and this problem is
> following a full (all installed ports) poudriere run.
>
> I also think the problem involves several overlooked downstream ports, for
> example print/hplip
>
>
>
> -
> FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
> --
> View this message in context: 
> http://freebsd.1045724.n5.nabble.com/py-imaging-vs-py-pillow-tp5954043p5954805.html
> Sent from the freebsd-ports mailing list archive at Nabble.com.
> ___
> 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"



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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: py-imaging vs. py-pillow

[William Grzybowski]

Coexist how? They are essentially the same package. I don't see how
thats possible.

py-imaging is deprecated, they should be switched to py-pillow and thats it.

On Fri, Oct 3, 2014 at 6:08 AM, Stefan Ehmann  wrote:
> According to freshports there are about 10 ports that depend on py-pilllow
> and 50 that depend on py-imaging.
>
> py-imaging conflicts with py-pilllow. E.g., calibre and xmbc cannot be
> installed at the same time.
>
>
> I noticed the problem because calibre switched to py-pilllow recently.
> There really should be a way that these packages can coexist.
>
> (py-imaging/py-pilllow maintainers CCed)
> ___
> 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"



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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: x11-servers/xorg-server

[William A. Mahaffey III]

On 09/23/14 22:46, Patrick Powell wrote:

On 09/22/14 23:50, Kevin Oberman wrote:
On Mon, Sep 22, 2014 at 9:19 PM, William A. Mahaffey III 


wrote:


On 09/22/14 16:38, Patrick Powell wrote:


On 09/21/14 16:52, William A. Mahaffey III wrote:


On 09/21/14 18:12, Robert_Burmeister wrote:


William A. Mahaffey III wrote


On 09/21/14 11:41, Robert_Burmeister wrote:


On 13.09.2014 22:10, Robert Burmeister wrote:

FreeBSD 10.1 i386
xorg-server 1.12.4_9,1 and 1.12.4_1,1
Still don't have mouse support after upgrade from 1.12.4_8,1

[  1786.822] (EE) Failed to load module "mouse" (module does 
not

exist,
0)


Have you installed x11-drivers/xf86-input-mouse?


[  1786.825] (EE) Failed to load module "kbd" (module does not
exist,
0)


And x11-drivers/xf86-input-keyboard?
___


Installing x11-drivers/xf86-input-mouse and
x11-drivers/xf86-input-keyboard
fixed the problem, however, I don't understand why upgrading
from xorg-server 1.12.4_8,1 to xorg-server 1.12.4_9,1
would require new drivers, or lose the ones it had.

I would think these drivers would/should be a dependency for
xorg-server
in the Ports system...
___

I have had that same problem verbatim the last 2 x-server 
upgrades I

did, & that was the fix, (re?)install the kbd & mouse drivers. I
(pkg-)upgraded this A.M., no such issues 
-- 




Even more interesting...
x11-drivers/xf86-input-mouse and x11-drivers/xf86-input-keyboard
have xorg-server as a dependency, and so cannot be a circular
dependency.

I'm guessing that the mouse and keyboard drivers got deleted as
dependents
of
xorg-server during the upgrade, but there are no dependencies in my
desktop
build
process that require that they be put back, even through a complete
system
recompile.

I'm thinking 'x11-drivers/xorg-drivers' and 'x11/xorg-minimal' 
should be

bumped
when xorg-server is upgraded.

(When my current recompile is done, I will check that my 
xorg-drivers

didn't
get removed as well.)



I am using pkg, no ports, no recompiling  FBSD 9.3, BTW 


  Just a thought - check to make sure that the 
x11-drivers/xf86-input-keyboard
port on the PKGng server you are using  was actually rebuilt for 
the new
version of  xorg-server. I had this problem a couple of weeks ago 
and the X

log file hinted that the keyboard driver was not compatible with the
version of xorg-server.  At the time I thought that this was due to 
a lag
in the PKGng server building the new drivers so I compiled and 
installed

the x11-drivers/xf86-input-keyboard.  The problem went away.

This appears to be the same sort of issue. Perhaps the driver(s) 
are not
getting rebuilt for the new version of xorg-server?  Or perhaps 
this is
related to packages on the 'with_new_xorg' PKGng server versus 
packages on

the standard PKGng server?
___
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org"


Would that (drivers not getting rebuilt right) be a pkg problem or 
an X11

problem (or something else) ? Just checking 


--

 William A. Mahaffey III


It's a ports issue. The ports system (which is used by pkg) depends on
incrementing version numbers to tell when a port has been updated and 
needs
to be rebuilt or when a port needs updating because a dependency has 
been
updated in a way that affects the port.  The former is typically the 
result
of a change to a port that changes hte version number. The later is a 
bump
of the PORT_REVISION to indicate to the ports system that some change 
that
did not come from a change upstream, but local to FreeBSD requires a 
port

rebuild.

In this case, it does not work. The actual version number has not 
changed
as the upstream version has not changed. PORT_REVISION would result 
in the

ports being rebuilt, but that does not play with the definition of
WITH_NEW_XORG. I somehow needs to be bumped when any system sets
WITH_NEW_XORG and I don't see any way in hte current structure to do 
this.

It is the result of having two parallel ports trees.

One possible fix is to have code in the Makefile to check WITH_NEW_XORG
and, if it is defined, use a different PORT_REVISION. If the old Xorg
driver gets a bump of PORT_REVESION, the new one would, as well, but I
don't see any reason this could not be done as both numbers are in 
the same

Makefile and should be only a few lines apart. something like:
. if defined(WITH_NEW_XORG)
PORT_REVISION=2
. else
PORT_REVISION=1
. endif

This may break the index, so I'm not sure it would work as simply as 
this,

but I bet it could be made to work,
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.

Re: Heads up audio/video/graphics/multimedia/net/streaming port maintainers - ACTION REQUIRED

[William Grzybowski]

On Tue, Sep 16, 2014 at 4:05 PM, Michelle Sullivan  wrote:
> Thomas Zander wrote:
>> I have prepared a drop-in replacement for the ffmpeg port which uses
>> the recent 2.4 release. You can download it from:
>> http://people.freebsd.org/~riggs/ffmpeg-2.4.tar.xz
>>
>> Please check whether the ports maintained by you build and link with
>> this version and prepare a suitable fix if necessary.
>>
>
> Any reason why you can't create an 'ffmpeg24' port so it can go live
> then people can create a a port option to turn on using the later
> version - then when the ports are all updated you can just 'switch it to
> the default'... that seems to be the way the ports tree has been handled
> over the last year.

Or create a ffmpeg23 port and switch all ports that cant handle ffmpeg
2.4 to that before it happens.
Thats how I handled the ffmpeg 0.x -> ffmpeg 2.x transition. It was
very smooth, all things considered :).



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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/lapack broken

[William Grzybowski]

On Sat, Aug 2, 2014 at 1:21 PM, Steve Kargl
 wrote:
> On Sat, Aug 02, 2014 at 12:49:03PM -0300, William Grzybowski wrote:
>> On Sat, Aug 2, 2014 at 1:54 AM, Steve Kargl
>>  wrote:
>> > On Fri, Aug 01, 2014 at 10:14:43PM -0300, William Grzybowski wrote:
>> >> I can't help but notice how unrespectful you have been.
>> >> Its not the first message ranting about something broken.
>> >>
>> >
>> > I can't help but notice how poorly some decisions are made
>> > within the ports community, and no, this isn't the nearly
>> > the first poor decision.
>> >
>> > If the port has an option to build the profiled libraries
>> > and that option is selected, then I expect the port to
>> > build the profiled library.
>>
>> You're welcome to help the ports committers to maintain over 20k ports
>> and raise the quality.
>> Are you looking for mentors for your ports@ commit bit?
>>
>
> Check your history.  I was a port maintainer many years
> ago.  Dropped maintainership of all my ports after several
> unreviewed changes by others to those ports were made.
> These unreviewed changes broke those ports and I was
> forced to clean up the mess.

So, you gave up?

> This of course has little to do with the issue that I have
> raised here.  A port, namely math/lapack, has an option to
> build profiled libraries and the port does not honor that
> option when selected.  It's simple Q&A.  Either remove the
> option or fix it.

Like I said, fill out a PR and mail the maintainer.
"Its broken, fix it." Doesn't work.


-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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/lapack broken

[William Grzybowski]

On Sat, Aug 2, 2014 at 1:54 AM, Steve Kargl
 wrote:
> On Fri, Aug 01, 2014 at 10:14:43PM -0300, William Grzybowski wrote:
>> I can't help but notice how unrespectful you have been.
>> Its not the first message ranting about something broken.
>>
>
> I can't help but notice how poorly some decisions are made
> within the ports community, and no, this isn't the nearly
> the first poor decision.
>
> If the port has an option to build the profiled libraries
> and that option is selected, then I expect the port to
> build the profiled library.

You're welcome to help the ports committers to maintain over 20k ports
and raise the quality.
Are you looking for mentors for your ports@ commit bit?



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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/lapack broken

[William Grzybowski]

I can't help but notice how unrespectful you have been.
Its not the first message ranting about something broken.

This is a open source project, people work on it in their spare times.
I think you should know that as a src@ committer.

If you do not want to provide a patch for the problem please fill out
a PR (bugs.freebsd.org) and/or contact the maintainer.

Thank you!

On Fri, Aug 1, 2014 at 9:47 PM, Steve Kargl
 wrote:
> % portmaster --force-config math/lapack
>
> (Select to build/install profiled libraries)
>
> ===>>> Port directory: /usr/ports/math/lapack
>
> ===>>> This port is marked IGNORE
> ===>>> you have chosen WITH_PROFILE, but have not installed
>the base system profiling libraries
>
> WTF!.  I know the base system doesn't have the profiled
> libraries installed.  I don't need nor want profiled
> versions of the base system libraries.  I want profiled
> versions of the math/lapack and math/blas libraries.
>
> ===>>> If you are sure you can build it, remove the
>IGNORE line in the Makefile and try again.
>
> This is just unbelievably stupid.  Please fix the port.
>
> --
> Steve
> ___
> 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"



-- 
William Grzybowski / wg
FreeBSD Ports Committer
___
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: minidlna: kevent polling failure: Interrupted system call

[William Grzybowski]

On Mon, Jun 23, 2014 at 10:28 AM, Bob Willcox  wrote:
> I periodically get these warning messages in my minidlna.log file when running
> clients from the server:
>
> inotify.c:857: warn: kevent polling failure: Interrupted system call
>
> Should I be concerned?
>
> This is minidlna 1.1.3 from ports.

Its a bug in kqueue patch, you can disable it if you're experiencing problems.
___
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: Maintainer requesting committer action for staging cleanup

[William Grzybowski]

Hi,

I've grabbed the PR, sit tight.

On Fri, Jun 20, 2014 at 11:53 AM, Jim Trigg  wrote:
> This is the second request, and as it is less than two weeks to the
> deadline I'm getting concerned.  I am the maintainer of mail/ecartis.  A
> user has graciously done the conversion to staging for me and submitted
> it as PR 190753; could someone please commit it?  I have annotated the
> PR with my approval.
>
> Thanks,
> Jim Trigg
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> 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"



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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"

Content contribution proposal

[William Hanson]

Hello,


My name is William Hanson and I run a business selling home and property 
security systems. Writing is as much a passion of mine as my business is and 
the two often cross paths. I have ghost written a number of articles and have 
been published in reputed journals. 


I am keen to feature a guest post on you blog as it would do wonders for my 
portfolio as a writer. I realized it was time I stopped ghost-writing for 
others and built an online reputation for myself. Here are a few ideas that I 
feel you will like:


1.  10 Reasons Why A Home Alarm System Is Imperative for Every House
2.  The Best Home Security Systems You Can Avail of in the Market Today
3.  A Look At the Various Uses of Security Technology
4.  Things About Home Automation You Possibly Didn’t Know
5.  A Few Safety Tips That Can Safeguard Your Home and Your Family
6.  Looking at the Advantages of Installing Home Security Cameras
7.  12 Tips to Protect Yourself Against Home Burglary
8.  A Look at How Home Automation Can Be Beneficial for the Elderly
9.  An in-depth Look at the Different Types of  Child Security
10. Security Tips for First Time Home Buyers
11. Important Fire Safety  Measures to take for your Home
12. Home Safety Tips for New Parents


I am also open to any ideas or suggestions that you might have. Lastly, I am 
willing to part with $50 for your efforts in publishing my article, as I know 
it would be a sound investment.
 
I hope your reply is in the positive, so your readers get the opportunity to 
benefit from what I have to say. 


Regards 
Will


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

Content Ideas You'd like

[William Hanson]

Hello,


My name is William Hanson and I run a business selling home and property 
security systems. Writing is as much a passion of mine as my business is and 
the two often cross paths. I have ghost written a number of articles and have 
been published in reputed journals. 


I am keen to feature a guest post on you blog as it would do wonders for my 
portfolio as a writer. I realized it was time I stopped ghost-writing for 
others and built an online reputation for myself. Here are a few ideas that I 
feel you will like:


1.  10 Reasons Why A Home Alarm System Is Imperative for Every House
2.  The Best Home Security Systems You Can Avail of in the Market Today
3.  A Look At the Various Uses of Security Technology
4.  Things About Home Automation You Possibly Didn’t Know
5.  A Few Safety Tips That Can Safeguard Your Home and Your Family
6.  Looking at the Advantages of Installing Home Security Cameras
7.  12 Tips to Protect Yourself Against Home Burglary
8.  A Look at How Home Automation Can Be Beneficial for the Elderly
9.  An in-depth Look at the Different Types of  Child Security
10. Security Tips for First Time Home Buyers
11. Important Fire Safety  Measures to take for your Home
12. Home Safety Tips for New Parents


I am also open to any ideas or suggestions that you might have. Lastly, I am 
willing to part with $50 for your efforts in publishing my article, as I know 
it would be a sound investment.
 
I hope your reply is in the positive, so your readers get the opportunity to 
benefit from what I have to say. 


Regards 
Will


___
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: samba36 on 10-RELEASE can't join AD

[William Marcelo Piovezan]

Hi, 

 

I'm getting exactly the same problem as described in this message.

I was using FreeBSD 9.2 with samba36 working in a Windows environment, the
DC is Windows 2012.

I´ve just updated to FreeBSD 10  and could not join AD anymore. Kinit works
perfectly buy net ads join returns the following error:

 

Failed to join domain: failed to connect to AD: Looping detected inside
krb5_get_in_tkt

 

After several retries, the computer account at Windows DC has been locked
(maybe due to domain policy). I´ve deleted the account and tried to join
again but the same problem happened. But for some reason the computer
account is added to the Windows DC even with the Samba error. Trying wbinfo
-u returns nothing so I suspect the machine has not been added at all.

Is there anyone that could solve or workaround this problem? I have the
latest samba36.22 with heimdal installed.

 

> I can't seem to join AD with samba36 on 10-RELEASE:
> 
>   pacija at
server:/usr/local/etc % sudo net ads join -U pacija
> Enter pacija's password:
> kerberos_kinit_password
 pacija at
EXAMPLE.ORG  failed: Looping
> detected
> inside krb5_get_in_tkt Failed to join domain: failed to connect to AD:
> Looping detected inside krb5_get_in_tkt
> 
> Kerberos seem to work OK, i can get tickets with kinit. Same krb5.conf
> and smb.conf on another 9.2-RELEASE machine are joining AD without
> problem.
> 
> Any suggestions?
> --
> Marko Cupać < 
marko.cupac at mimar.rs >
> ___
>   freebsd-ports
at freebsd.org  mailing list
>  
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "

freebsd-ports-unsubscribe at freebsd.org
> "
 

 

___
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: Can someone please commit ports/183905

[William Grzybowski]

Hi,

Committed.


On Fri, Dec 20, 2013 at 1:54 PM, Michael Gmelin  wrote:

> It's super trivial.
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183905
>
> --
> Michael Gmelin
> ___
> 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"
>



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing

[William Grzybowski]

On Wed, Dec 18, 2013 at 3:45 PM, Eitan Adler  wrote:

> On Wed, Dec 18, 2013 at 11:20 AM, Lars Engels 
> wrote:
> > Am 2013-12-17 23:33, schrieb John Marino:
> >
> >> Over the months I've seen several ports users copy a failure log and
> >> mail it to ports@, usually without even saying "hello".  I've tried to
> >> discourage that behavior but other members of this mail list encourage
> >> this method of bypassing writing PRs.  One user even proudly boasted
> >> that sending email to ports@ is faster than writing a PR so of course
> he
> >> was going to do that instead.
> >>
> >
> > That only shows how badly GNATS sucks and that it's much more
> uncomfortable
> > to
> > use than writing a mail.
> > I totally agree that error need to be tracked in an error tracker where
> > reports
> > don't get lost, you have a proper history etc. pp. but GNATS is just
> ancient
> > and
> > should have died in a fire a long time ago.
>
> Agreed.  There is active work on moving to bugzilla instead of GNATS.
> I can't give a definite timeline but it should be 'soon'.


You're going on vacation. Who will be taking the lead of this change so we
can refer to?

Thanks.

-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: [REL - 10i386-quarterly][devel/generate] Failed for generate-2.6 in build

[William Grzybowski]

On Tue, Dec 17, 2013 at 10:08 AM, D'Arcy J.M. Cain  wrote:

> On Tue, 17 Dec 2013 04:26:08 GMT
> pkg-fall...@freebsd.org wrote:
> > You are receiving this mail as a port that you maintain
> > is failing to build on the FreeBSD package build server.
> > Please investigate the failure and submit a PR to fix
> > build.
> >
> > Maintainer: da...@druid.net
> > Last committer: b...@freebsd.org
> > Ident:  $FreeBSD: branches/2014Q1/devel/generate/Makefile
> > 327723 2013-09-20 17:04:43Z bapt $ Log URL:
> >
> http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2013-12-16_15h18m40s/logs/generate-2.6.log
> > Build URL:
> > http://beefy1.isc.freebsd.org/bulk/10i386-quarterly/2013-12-16_15h18m40s
> > Log:
>
> I have replied to this message a number of times and copied the last
> committer once.  I am not a FreeBSD developer.  I am the developer of
> the software in your ports tree.  I did put out an update that allows
> it to build under FreeBSD and all that is required is to update to
> version 2.8.  Can someone please remove me as maintainer of this code
> and do the update to 2.8.
>

i'll take care of it, thanks.



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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/py-numpy: make: line 60: Need an operator

[William Grzybowski]

Hi,

Update your ports tree.


On Sun, Dec 15, 2013 at 2:41 PM, Anton Shterenlikht wrote:

>
> On ia64 r256683, ports at r336504,
>
> # make -C /usr/ports/math/py-numpy/ showconfig
> make: "/usr/ports/math/py-numpy/Makefile" line 60: Need an operator
> make: "/usr/ports/math/py-numpy/Makefile" line 61: Need an operator
> make: "/usr/ports/math/py-numpy/Makefile" line 62: Need an operator
> make: "/usr/ports/math/py-numpy/Makefile" line 63: Need an operator
> make: "/usr/ports/math/py-numpy/Makefile" line 64: Need an operator
> make: "/usr/ports/math/py-numpy/Makefile" line 65: Need an operator
> make: "/usr/ports/math/py-numpy/Makefile" line 66: Need an operator
> make: Fatal errors encountered -- cannot continue
> make: stopped in /usr/ports/math/py-numpy
> #
>
> Anton
> ___
> 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"
>



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Trouble building some perl ports

[William Grzybowski]

Did you follow:

20130612:
  AFFECTS: users of lang/perl* and any port that depends on it
  AUTHOR: a...@freebsd.org

  lang/perl5.12 has been upgraded from version 5.12.4 to 5.12.5
  lang/perl5.14 has been upgraded from version 5.14.2 to 5.14.4
  lang/perl5.16 has been upgraded from version 5.16.2 to 5.16.3

  The directory structure where Perl is installed has also been modified:
  "major.minor" is now used instead of "major.minor.patchlevel".

  The "perl-after-upgrade" script has been removed.

  Please rebuild all Perl ports and all ports that depend on it:

  # portmaster -r perl
or
  # portupgrade -rf perl
or
  # pkg install -fR perl


On Thu, Dec 5, 2013 at 1:41 PM, Steve McCoy  wrote:

> Hello,
>
> I'm having some trouble creating packages for some perl ports. They seem to
> be confused about where to place files. For example, p5-libwww:
>
> ===>   Generating temporary packing list
> Installing
>
> /var/ports/usr/ports/www/p5-libwww/work/stage/usr/local/lib/perl5/site_perl/5.12.4/LWP.pm
>
> ...
>
> ===>  Building package for p5-libwww-6.05
> Creating package
> /var/ports/usr/ports/www/p5-libwww/work/p5-libwww-6.05.tbz
> Registering depends: ...
> tar: lib/perl5/site_perl/5.12/mach/auto/LWP/.packlist: Cannot stat: No
> such file or directory
> tar: lib/perl5/site_perl/5.12/LWP.pm: Cannot stat: No such file or
> directory
>
> @INC contains /usr/local/lib/perl/site_perl/5.12.4 and that's where all of
> the other perl packages had been installed, so the staging step seems
> correct to me. I don't know why the packaging step is expecting anything to
> be staged in a 5.12 path instead of 5.12.4. Does anybody have an idea how
> it could get into this situation? Could the be because my installed perl is
> older than these packages? (It's from before threads became a default
> option.)
>
>
> Any help would be appreciated!
> ___
> 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"
>



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: ENDLESS LOOP: Revision: 335170: ===>>> The devel/py-distribute port moved to devel/py-setuptools

[William Grzybowski]

Nevermind what I said, did you read 20131127 in UPDATING?

On Fri, Nov 29, 2013 at 10:15 AM, William Grzybowski
 wrote:
> Have you tried after r335167?
>
> On Fri, Nov 29, 2013 at 10:10 AM, O. Hartmann  wrote:
>> Funny, portmaster -da is looping with the below shown message ;-)
>>
>>===>>> The devel/py-setuptools port moved to devel/py-distribute
>> ===>>> Reason: Replaced with distribute
>>
>>
>> ===>>> The devel/py-distribute port moved to devel/py-setuptools
>> ===>>> Reason: Replaced with setuptools
>>
>>
>> ===>>> The devel/py-setuptools port moved to devel/py-distribute
>> ===>>> Reason: Replaced with distribute
>>
>>
>> ===>>> The devel/py-distribute port moved to devel/py-setuptools
>> ===>>> Reason: Replaced with setuptools
>>
>>
>> ===>>> The devel/py-setuptools port moved to devel/py-distribute
>> ===>>> Reason: Replaced with distribute
>
>
>
> --
> William Grzybowski
> --
> Curitiba/PR - Brasil



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: ENDLESS LOOP: Revision: 335170: ===>>> The devel/py-distribute port moved to devel/py-setuptools

[William Grzybowski]

Have you tried after r335167?

On Fri, Nov 29, 2013 at 10:10 AM, O. Hartmann  wrote:
> Funny, portmaster -da is looping with the below shown message ;-)
>
>===>>> The devel/py-setuptools port moved to devel/py-distribute
> ===>>> Reason: Replaced with distribute
>
>
> ===>>> The devel/py-distribute port moved to devel/py-setuptools
> ===>>> Reason: Replaced with setuptools
>
>
> ===>>> The devel/py-setuptools port moved to devel/py-distribute
> ===>>> Reason: Replaced with distribute
>
>
> ===>>> The devel/py-distribute port moved to devel/py-setuptools
> ===>>> Reason: Replaced with setuptools
>
>
>     ===>>> The devel/py-setuptools port moved to devel/py-distribute
> ===>>> Reason: Replaced with distribute



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: net/grive update to 0.2.0_1 on 10-beta3

[William Grzybowski]

I don't know how to fix this, builds fine on 9.x:

http://beefy2.isc.freebsd.org/bulk/91amd64-default/2013-11-13_01h35m11s/logs/grive-0.2.0_1.log

On Wed, Nov 13, 2013 at 11:10 AM, Alex V. Petrov  wrote:
> [ 95%] Building CXX object
> libgrive/CMakeFiles/unittest.dir/test/util/FunctionTest.cc.o
>
> [ 97%] Building CXX object
> libgrive/CMakeFiles/unittest.dir/test/util/SignalHandlerTest.cc.o
>
> [100%] Building CXX object
> libgrive/CMakeFiles/unittest.dir/test/xml/NodeTest.cc.o
>
> 4 warnings generated.
>
> Linking CXX executable grive
>
> ../libgrive/libgrive.a(Json.cc.o): In function
> `gr::Json::Json >
>>(std::__1::vector > const&)':
>
> /usr/ports/net/grive/work/Grive-grive-93d696a/libgrive/src/protocol/Json.cc:(.text+0xb1e):
> warning: Warning: please link against libjson-c instead of libjson
>
> Linking CXX executable unittest
>
> /usr/bin/ld: c: invalid DSO for symbol `json_object_array_get_idx'
> definition
>
> /usr/local/lib/libjson-c.so.2: could not read symbols: Bad value
>
> c++: error: linker command failed with exit code 1 (use -v to see
> invocation)
>
> --- grive/grive ---
>
> *** [grive/grive] Error code 1
>
>
>
> make[3]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> 1 error
>
>
>
> make[3]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> --- grive/CMakeFiles/grive_executable.dir/all ---
>
> *** [grive/CMakeFiles/grive_executable.dir/all] Error code 2
>
>
>
> make[2]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> A failure has been detected in another branch of the parallel make
>
>
>
> make[3]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> --- libgrive/CMakeFiles/unittest.dir/all ---
>
> *** [libgrive/CMakeFiles/unittest.dir/all] Error code 2
>
>
>
> make[2]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> 2 errors
>
>
>
> make[2]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> --- all ---
>
> *** [all] Error code 2
>
>
>
> make[1]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> 1 error
>
>
>
> make[1]: stopped in /usr/ports/net/grive/work/Grive-grive-93d696a
>
> ===> Compilation failed unexpectedly.
>
> Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
>
> the maintainer.
>
> *** Error code 1
>
>
>
> Stop.
>
> make: stopped in /usr/ports/net/grive
>
>
>
> ===>>> make failed for net/grive
>
> ===>>> Aborting update
>
>
>
> ===>>> Killing background jobs
>
> Terminated
>
>
>
> ===>>> You can restart from the point of failure with this command line:
>
> portmaster  net/grive
>
>
>
> ===>>> Exiting
>
> --
>
> -
>
> Alex V. Petrov
>
>



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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"

[patch] shells/fish compiler error fix, version update

[William MacKay]

The shells/fish port has failed to build on FreeBSD 10 for several 
weeks.  It fails with errors like:


./io.h:12:12: error: no member named 'tr1' in namespace 'std'
./io.h:183:39: error: no template named 'shared_ptr'; did you mean 
'std::shared_ptr'?


This patch fixes the error by telling the compiler to use C++11.  It 
also updates fish from version 2.0.0 to version 2.1.0.


The patch is pasted below, or you can find it at 
.


Will MacKay

diff -u fish-old/Makefile fish-new/Makefile
--- fish-old/Makefile   2013-11-06 23:03:53.690089207 -0800
+++ fish-new/Makefile   2013-11-06 23:28:30.750988987 -0800
@@ -2,7 +2,7 @@
 # $FreeBSD: shells/fish/Makefile 328855 2013-09-30 19:58:20Z bsam $

 PORTNAME=  fish
-PORTVERSION=   2.0.0
+PORTVERSION=   2.1.0
 CATEGORIES=shells
 MASTER_SITES=  http://fishshell.com/files/%SUBDIR%/
 MASTER_SITE_SUBDIR=${PORTVERSION}
@@ -19,7 +19,7 @@
 USE_AUTOTOOLS= autoconf
 CONFIGURE_ARGS=--docdir=${WRKDIR}/tmproot

-CPPFLAGS+= -I${LOCALBASE}/include
+CPPFLAGS+= -I${LOCALBASE}/include -std=c++11
 LDFLAGS+=  -L${LOCALBASE}/lib -pthread ${ICONV_LIB}

 MAN1=  fish.1 fish_indent.1 fish_pager.1 fishd.1 mimedb.1
diff -u fish-old/distinfo fish-new/distinfo
--- fish-old/distinfo   2013-11-06 23:03:53.691088871 -0800
+++ fish-new/distinfo   2013-11-06 23:26:33.274022156 -0800
@@ -1,2 +1,2 @@
-SHA256 (fish-2.0.0.tar.gz) = 
7e4c4a0b3c518769a3d31b235e743de7a8d52f851ad19d2df9d53534e6238303

-SIZE (fish-2.0.0.tar.gz) = 1540652
+SHA256 (fish-2.1.0.tar.gz) = 
af527af9d145df5675ca3031c1a87007d4f4753a1cde49da88f4eb883a1cf044

+SIZE (fish-2.1.0.tar.gz) = 1707921

___
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: Update devel/zmq (once more, this time Cc ports@)

[William Grzybowski]

On Wed, Nov 6, 2013 at 8:05 PM, Michael Gmelin  wrote:
> Hi,
>
> any chance you'll update zmq to the latest version in the near future,
> or at to least 3.2.4? sysutils/py-salt depends on it and has keep-alive
> issues with the old/outdated version.

You should open a PR, that way it will timeout and then someone can
take care of it regardless of the maintainer availability.

-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)

[William Grzybowski]

On Tue, Nov 5, 2013 at 2:09 PM, Dominic Fandrey  wrote:
> On 05/11/2013 14:55, Chad J. Milios wrote:
>> TLDR; check lines prefixed with ? in the transcript below.
>>
>> Ran into this over a couple weeks ago. Checked again with last night's 
>> portsnap, same problem, same ports. Figured I ought to pipe up about it. 
>> Seems like a good ol' classic mystery.
>>
>> I don't know if it's just one instance of a general problem in the way 
>> dependencies get detected and dispatched to be installed, maybe just in the 
>> python infrastructure, a bug in the net/py-kombu port (which my eyes 
>> couldn't find a problem with), or what. I looked into it for an hour before 
>> punting with a trivial workaround and moving on, didn't think much of it at 
>> the time, figuring it was just one of those temporary problems smarter minds 
>> are already hard at work fixing. Apparently they weren't or didn't. This 
>> time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty 
>> /usr/local then installing all ports from the same snapshot of /usr/ports).
>>
>> ***How to reproduce:
>>
>> Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0) 
>> or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since 
>> cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from 
>> ports with BOTO and/or ZMQ options. (In my case I have all its options on.)
>> ...
>> ===>  Checking if devel/py-boto already installed
>> ?===>   py27-boto-2.14.0 is already installed
>>   You may wish to ``make deinstall'' and install this port again
>>   by ``make reinstall'' to upgrade it properly.
>>   If you really wish to overwrite the old port of devel/py-boto
>>   without deleting it first, set the variable "FORCE_PKG_REGISTER"
>>   in your environment or the "make install" command line.
>> *** [check-already-installed] Error code 1
>>
>> Stop in /usr/ports/devel/py-boto.
>> *** [run-depends] Error code 1
>>
>> Stop in /usr/ports/net/py-kombu.
>> root@shikamaru:/usr/ports/net/py-kombu #
>> ...
>>     Stop in /usr/ports/net/py-kombu.
>> root@shikamaru:/usr/ports/net/py-kombu #
>
> That looks like the dependencies in net/py-kombu are broken. I.e. they
> refer to files that are not/no longer installed by the dependencies.

Did you get my email asking to try again after the last port update
fixing the dependencies?

-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Is it or isn't it installed? (It is, but ports tries to again, doomed to fail.)

[William Grzybowski]

Try again.

On Tue, Nov 5, 2013 at 11:55 AM, Chad J. Milios  wrote:
> TLDR; check lines prefixed with ? in the transcript below.
>
> Ran into this over a couple weeks ago. Checked again with last night's
> portsnap, same problem, same ports. Figured I ought to pipe up about it.
> Seems like a good ol' classic mystery.
>
> I don't know if it's just one instance of a general problem in the way
> dependencies get detected and dispatched to be installed, maybe just in the
> python infrastructure, a bug in the net/py-kombu port (which my eyes
> couldn't find a problem with), or what. I looked into it for an hour before
> punting with a trivial workaround and moving on, didn't think much of it at
> the time, figuring it was just one of those temporary problems smarter minds
> are already hard at work fixing. Apparently they weren't or didn't. This
> time I'm using a squeaky clean new amd64 9.2-RELEASE-p1 system (empty
> /usr/local then installing all ports from the same snapshot of /usr/ports).
>
> ***How to reproduce:
>
> Just happen to already have the dependency devel/py-boto (py27-boto-2.14.0)
> or devel/py-pyzmq (py27-pyzmq-2.2.0) installed (and their port dirs since
> cleaned up) when you try to install net/py-kombu (py27-kombu-3.0.1) from
> ports with BOTO and/or ZMQ options. (In my case I have all its options on.)
>
> ***Transcripts: (attention to lines prefixed with ? and !)
>
> ===>  Installing for py27-kombu-3.0.1
> ===>   py27-kombu-3.0.1 depends on package: py27-amqp>=1.3.1 - found
> ===>   py27-kombu-3.0.1 depends on package: py27-anyjson>=0.3.3 - found
> ===>   py27-kombu-3.0.1 depends on package: py27-beanstalkc>0 - found
> ?===>   py27-kombu-3.0.1 depends on package: py27-boto=>2.6.0 - not
> found
> ===>Verifying install for py27-boto=>2.6.0 in
> /usr/ports/devel/py-boto
> ===>  Installing for py27-boto-2.14.0
> ===>   py27-boto-2.14.0 depends on file: /usr/local/bin/easy_install-2.7
> - found
> ===>   py27-boto-2.14.0 depends on file: /usr/local/bin/python2.7 -
> found
> ===>   py27-boto-2.14.0 depends on executable: python - found
> ===>   py27-boto-2.14.0 depends on executable: python2 - found
> ===>   Generating temporary packing list
> ===>  Checking if devel/py-boto already installed
> ?===>   py27-boto-2.14.0 is already installed
>   You may wish to ``make deinstall'' and install this port again
>   by ``make reinstall'' to upgrade it properly.
>   If you really wish to overwrite the old port of devel/py-boto
>   without deleting it first, set the variable "FORCE_PKG_REGISTER"
>   in your environment or the "make install" command line.
> *** [check-already-installed] Error code 1
>
> Stop in /usr/ports/devel/py-boto.
> *** [run-depends] Error code 1
>
> Stop in /usr/ports/net/py-kombu.
> root@shikamaru:/usr/ports/net/py-kombu #
>
>
> ===>  Installing for py27-kombu-3.0.1
> ===>   py27-kombu-3.0.1 depends on package: py27-amqp>=1.3.1 - found
> ===>   py27-kombu-3.0.1 depends on package: py27-anyjson>=0.3.3 - found
> ===>   py27-kombu-3.0.1 depends on package: py27-beanstalkc>0 - found
> !===>   py27-kombu-3.0.1 depends on package: py27-boto=>2.6.0 - not
> found
> !===>Verifying install for py27-boto=>2.6.0 in
> /usr/ports/devel/py-boto
> !===>   Returning to build of py27-kombu-3.0.1
> ===>   py27-kombu-3.0.1 depends on package: pymongo>0 - found
> ===>   py27-kombu-3.0.1 depends on package: py27-sqlalchemy>0 - found
> ?===>   py27-kombu-3.0.1 depends on package: py27-pyzmq=>2.2.0 - not
> found
> ===>Verifying install for py27-pyzmq=>2.2.0 in
> /usr/ports/devel/py-pyzmq
> ===>  Installing for py27-pyzmq-2.2.0
> ===>   py27-pyzmq-2.2.0 depends on file: /usr/local/bin/python2.7 -
> found
> ===>   py27-pyzmq-2.2.0 depends on executable: python - found
> ===>   py27-pyzmq-2.2.0 depends on shared library: zmq.1 - found
> ===>   Generating temporary packing list
> ===>  Checking if devel/py-pyzmq already installed
> ?===>   py27-pyzmq-2.2.0 is already installed
>   You may wish to ``make deinstall'' and install this port again
>   by ``make reinstall'' to upgrade it properly.
>   If you really wish to overwrite the old port of devel/py-pyzmq
>   without deleting it first, set the variable "FORCE_PKG_REGISTER"
>   in your environment or the "make inst

[RFC] devel/py-setuptools

[William Grzybowski]

Hi,

As some of you are aware, py-setuptools is back in action, replacing 
py-distribute.

Attached is the proposed patch to make the move once again.

From what I could gather we dont need to handle easy-install.pth anymore, it is 
not created by setuptools on install and is created automatically in 
easy_install build.

Let me know if you run into any troubles.


Cheers,
Index: UPDATING
===
--- UPDATING(revision 332532)
+++ UPDATING(working copy)
@@ -5,6 +5,21 @@
 You should get into the habit of checking this file for changes each time
 you update your ports collection, before attempting any port upgrades.
 
+20131102:
+  AFFECTS: users of devel/py-distribute (i.e you)
+  AUTHOR: w...@freebsd.org
+
+  devel/py-distribute was replaced with devel/py-setuptools. Please do
+  the following according to package manager used. py-distribute port
+  will be removed shortly.
+
+  # portmaster -o devel/py-setuptools devel/py-distribute
+or
+  # portupgrade -fo devel/py-setuptools devel/py-distribute
+or
+  # pkg set -o devel/py-distribute:devel/py-setuptools
+  # pkg install -f devel/py-setuptools
+
 20131031:
   AFFECTS: users of multimedia/rtmpdump
   AUTHOR: h...@freebsd.org
Index: MOVED
===
--- MOVED   (revision 332532)
+++ MOVED   (working copy)
@@ -5158,3 +5158,4 @@
 net-im/pymsn||2013-10-31|Has expired: Primary MSN Messenger service terminated 
30 APR 2013
 net-im/tmsnc||2013-10-31|Has expired: Primary MSN Messenger service terminated 
30 APR 2013
 mail/squirrelmail-postfixadmin-plugin|mail/postfixadmin|2013-11-01|Has 
expired: Now distributed with postfixadmin
+devel/py-distribute|devel/py-setuptools|2013-11-02|Replaced with setuptools
Index: devel/Makefile
===
--- devel/Makefile  (revision 332532)
+++ devel/Makefile  (working copy)
@@ -3726,6 +3726,7 @@
 SUBDIR += py-sdl2
 SUBDIR += py-serpent
 SUBDIR += py-setproctitle
+SUBDIR += py-setuptools
 SUBDIR += py-setuptools-git
 SUBDIR += py-setuptools_darcs
 SUBDIR += py-setuptools_hg
Index: devel/py-setuptools/Makefile
===
--- devel/py-setuptools/Makefile(revision 0)
+++ devel/py-setuptools/Makefile(working copy)
@@ -0,0 +1,37 @@
+# $FreeBSD$
+
+PORTNAME=  setuptools
+PORTVERSION=   1.1.7
+CATEGORIES=devel python
+MASTER_SITES=  CHEESESHOP
+PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
+DIST_SUBDIR=   python
+
+MAINTAINER=pyt...@freebsd.org
+COMMENT=   Python packages installer
+
+LICENSE=   PSFL
+
+CONFLICTS_INSTALL= ${PYTHON_PKGNAMEPREFIX}distribute-[0-9]*
+
+PLIST_SUB= PYVER=${PYTHON_VER} VERSION=${PORTVERSION}
+
+PYDISTUTILS_NOEGGINFO= yes
+USE_PYTHON=yes
+USE_PYDISTUTILS=yes
+
+SUB_LIST=  IF_DEFAULT=${IF_DEFAULT}
+
+.include 
+
+.if ${PYTHON_VERSION} == ${PYTHON_DEFAULT_VERSION} && 
!exists(${LOCALBASE}/bin/easy_install)
+PLIST_SUB+=IF_DEFAULT=""
+.else
+PLIST_SUB+=IF_DEFAULT="@comment "
+SUB_FILES+=pkg-message
+.endif
+
+regression-test: build
+   @cd ${WRKSRC} && ${PYTHON_CMD} ${PYSETUP} test
+
+.include 

Property changes on: devel/py-setuptools/Makefile
___
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Added: svn:mime-type
## -0,0 +1 ##
+text/plain
\ No newline at end of property
Added: svn:keywords
## -0,0 +1 ##
+FreeBSD=%H
\ No newline at end of property
Index: devel/py-setuptools/distinfo
===
--- devel/py-setuptools/distinfo(revision 0)
+++ devel/py-setuptools/distinfo(working copy)
@@ -0,0 +1,2 @@
+SHA256 (python/setuptools-1.1.7.tar.gz) = 
b35e3d7c79cfdb5b38cfc71f4b0deab4350c1176fc4bb05bfa8945504ecfb028
+SIZE (python/setuptools-1.1.7.tar.gz) = 682308

Property changes on: devel/py-setuptools/distinfo
___
Added: svn:mime-type
## -0,0 +1 ##
+text/plain
\ No newline at end of property
Added: fbsd:nokeywords
## -0,0 +1 ##
+yes
\ No newline at end of property
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Index: devel/py-setuptools/files/pkg-message.in
===
--- devel/py-setuptools/files/pkg-message.in(revision 0)
+++ devel/py-setuptools/files/pkg-message.in(working copy)
@@ -0,0 +1,7 @@
+*
+
+The script %%PREFIX%%/bin/easy_install was already installed
+on your system, so the only script %%PREFIX%%/bin/easy_install-%%PYVER%%
+has been added.
+
+*

Property changes on: devel/py-setuptools/files/pkg-messag

Re: [REL - 83i386-default][textproc/multimarkdown] Failed for multimarkdown-4.3.2 in extract

[William Grzybowski]

 for multimarkdown-4.3.2
> ===
> ===
> ===
> ===>   multimarkdown-4.3.2 depends on file: /usr/local/sbin/pkg - not found
> ===>Verifying install for /usr/local/sbin/pkg in /usr/ports/ports-mgmt/pkg
> ===>   Installing existing package /packages/All/pkg-1.1.4_8.txz
> Installing pkg-1.1.4_8... done
> If you are upgrading from the old package format, first run:
>
>   # pkg2ng
> ===>   Returning to build of multimarkdown-4.3.2
> ===
> ===
> ===
> ===
> ===>  License MIT accepted by the user
> ===> Fetching all distfiles required by multimarkdown-4.3.2 for building
> ===
> ===
> ===>  License MIT accepted by the user
> ===> Fetching all distfiles required by multimarkdown-4.3.2 for building
> ===
> ===
> ===>   multimarkdown-4.3.2 depends on executable: git - not found
> ===>Verifying install for git in /usr/ports/devel/git
> ===>   Installing existing package /packages/All/git-1.8.4.1.txz
> Installing git-1.8.4.1...Installing expat-2.1.0... done
> Installing ca_root_nss-3.15.2_1... done
> Installing p5-Net-SMTP-SSL-1.01_1...Installing perl5-5.16.3_2...Removing 
> /usr/local/etc/perl5_version... Done.
> Creating /usr/local/etc/perl5_version... Done.
> Removing stale symlinks from /usr/bin...
> Skipping /usr/bin/perl
> Skipping /usr/bin/perl5
> Done.
> Creating various symlinks in /usr/bin...
> Symlinking /usr/local/bin/perl5.16.3 to /usr/bin/perl
> Symlinking /usr/local/bin/perl5.16.3 to /usr/bin/perl5
> Done.
> Cleaning up /etc/manpath.config... Done.
> Spamming /etc/manpath.config... Done.
>  done
>  done
> Installing python27-2.7.5_3...Installing gettext-0.18.3.1...Installing 
> libiconv-1.14_1... done
>  done
>  done
> Installing python2-2_1... done
> Installing python-2.7_1,2... done
> Installing p5-Error-0.17021... done
> Installing curl-7.33.0... done
> Installing cvsps-2.1_1... done
> ===> Creating users and/or groups.
> Creating group 'git_daemon' with gid '964'.
> Creating user 'git_daemon' with uid '964'.
> Updating /etc/shells
>  done
> 
> Note that some of the standard modules are provided as separate
> ports since they require extra dependencies:
>
> bsddb   databases/py-bsddb
> gdbmdatabases/py-gdbm
> sqlite3 databases/py-sqlite3
> tkinter x11-toolkits/py-tkinter
>
> Install them as needed.
> 
>
> 
> *** GITWEB *
> If you installed the GITWEB option please follow these instructions:
>
> In the directory /usr/local/share/examples/git/gitweb you can find all files 
> to
> make gitweb work as a public repository on the web.
>
> All you have to do to make gitweb work is:
> 1) Copy the files /usr/local/share/examples/git/gitweb/* to a directory on
>your web server (e.g. Apache2) in which you are able to execute
>CGI-scripts.
> 2) In gitweb.cgi, adjust the variable $projectroot to point to
>your git repository (that is where you have your *.git project
>directories).
> *** GITWEB *
>
> *** CONTRIB 
> If you installed the CONTRIB option please note that the scripts are
> installed in /usr/local/share/git-core/contrib. Some of them require
> other ports to be installed (perl, python, etc), which you may need to
> install manually.
> *** CONTRIB 
> 
> ===>   Returning to build of multimarkdown-4.3.2
> ===
> ===
> ===>  License MIT accepted by the user
> ===> Fetching all distfiles required by multimarkdown-4.3.2 for building
> ===>  Extracting for multimarkdown-4.3.2
> /bin/mkdir -p /wrkdirs/usr/ports/textproc/multimarkdown/work
> cd /wrkdirs/usr/ports/textproc/multimarkdown/work && git clone 
> https://github.com/fletcher/MultiMarkdown-4.git
> Cloning into 'MultiMarkdown-4'...
> fatal: unable to access 'https://github.com/fletcher/MultiMarkdown-4.git/': 
> Could not resolve host: github.com
> *** Error code 128
>
> Stop in /usr/ports/textproc/multimarkdown.
> ===>  Cleaning for multimarkdown-4.3.2
>
> ___
> 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"



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Fwd: Compile error building audio/xmms2

[William Grzybowski]

On Fri, Oct 25, 2013 at 1:59 PM, Guido Falsi  wrote:
> On 10/25/13 15:09, Wolfgang Riegler wrote:
>>
>> Sorry, no attachment in last Email
>>
>>
>
> Hi, from this log I see it's the AVCODEC option causing problems. I'll test
> it and try to produce a fix.

Its a fallout from the ffmpeg update. Do you mind if I fix it for you,
as it was my fault?

Cheers


-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: sysutils/fusefs-kmod needs a poke

[William Grzybowski]

Hi,

Due to the bureaucracy involved its always best if you file a pr
(send-pr(1)) reporting the issue. Unless a portmgr steps in to fix the
problem.

Thanks

On Mon, Sep 30, 2013 at 9:58 PM, Kenta Suzumoto  wrote:
> The maintainer has ignored my emails so I'm sending to ports@
>
> ===
> ===
> ===
> ===>  Installing for fusefs-kmod-0.3.9.p1.20080208_11
> ===>   Generating temporary packing list
> ===>  Checking if sysutils/fusefs-kmod already installed
> ===> fuse_module (install)
> install -o root -g wheel -m 555   fuse.ko /usr/local/modules
> kldxref /usr/local/modules
> ===> mount_fusefs (install)
> install -s -o root -g wheel -m 555   mount_fusefs /usr/local/sbin/mount_fusefs
> install -o root -g wheel -m 444 mount_fusefs.8 /usr/local/man/man8
> ===> Staging rc.d startup script(s)
>
> cat: /usr/ports/sysutils/fusefs-kmod/pkg-message: No such file or directory
> *** [post-install] Error code 1
>
> Stop in /usr/ports/sysutils/fusefs-kmod.
> ===>  Cleaning for fusefs-kmod-0.3.9.p1.20080208_11
>
> If I run "touch /usr/ports/sysutils/fusefs-kmod/pkg-message" it works fine.
>
> ___
> 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"



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: [RFC] Stage support for easy_install

[William Grzybowski]

On Sat, Sep 28, 2013 at 6:56 AM, Marcus von Appen  wrote:
> On, Sat Sep 28, 2013, Olivier Duchateau wrote:
>
>> 2013/9/26 William Grzybowski :
>> > Hi,
>> >
>> > I made an attempt to support stage for easy-install, you can find the 
>> > patch here http://people.freebsd.org/~wg/easyinstall-stage.txt
>> >
>> > Aprrently it works :), let me know what you think.
>>
>> Thanks, it works fine.
>>
>> I made new diff after recent change in Mk/bsd.python.mk
>>
>> https://people.freebsd.org/~olivierd/patches/bsd.python.mk.diff
>>
>
> Unfortunately it does not. easy_install has the tendency to create .pth
> and site.py* files in the stagedir, causing leftovers that we are
> currently unable to handle.

Can you point at some port that it doesn't work?

Thanks



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: [REL - head-i386-default][security/sancp] Failed for sancp-1.6.1_4 in build (fwd)

[William Grzybowski]

===
> ===
> ===
> ===
> ===> Fetching all distfiles required by sancp-1.6.1_4 for building
> ===
> ===
> ===> Fetching all distfiles required by sancp-1.6.1_4 for building
> => SHA256 Checksum OK for sancp-1.6.1-stable.tar.gz.
> ===
> ===
> ===
> ===
> ===> Fetching all distfiles required by sancp-1.6.1_4 for building
> ===>  Extracting for sancp-1.6.1_4
> => SHA256 Checksum OK for sancp-1.6.1-stable.tar.gz.
> ===
> ===
> ===
> ===
> ===>  Patching for sancp-1.6.1_4
> ===
> ===
> ===
> ===
> ===
> ===
> ===>  Configuring for sancp-1.6.1_4
> ===
> ===
> ===>  Building for sancp-1.6.1_4
> g++ -Wall -O3 -I/usr/include/pcap -I/usr/local/include/pcap  -I./
> -L/usr/lib/libsocket.so  -g -L/opt/csw/lib -ggdb -c build_acl.cc -o
> build_acl.o make[2]: exec(g++) failed (No such file or directory)
> *** Error code 1
>
> Stop.
> make[2]: stopped in
> /wrkdirs/usr/ports/security/sancp/work/sancp-1.6.1-stable *** Error code 1
>
> Stop.
> make[1]: stopped in
> /wrkdirs/usr/ports/security/sancp/work/sancp-1.6.1-stable *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/security/sancp
> ===>  Cleaning for sancp-1.6.1_4
>
> -- End Forwarded Message --
>
>
>
> --
> Paul Schmehl (pa...@utdallas.edu)
> Senior Information Security Analyst
> The University of Texas at Dallas
> http://www.utdallas.edu/infosecurity/
>
> ___
> 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"



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Staging and read-only /usr/ports

[William Grzybowski]

On Thu, Sep 26, 2013 at 6:57 PM, Stefan Bethke  wrote:
>
> Am 26.09.2013 um 23:54 schrieb William Grzybowski :
>
>> On Thu, Sep 26, 2013 at 6:52 PM, Stefan Bethke  wrote:
>>> Guys,
>>>
>>> I've noticed that more and more ports are trying to build a package 
>>> /usr/ports/category/port/port-version.tgz. Since my /usr/ports is mounted 
>>> read-only (via nullfs), this fails. I've looked through Mk/*.mk trying to 
>>> figure out how I can redirect this to another dir. Is PACKAGES the way to 
>>> go? What if I don't want to keep packages around?
>>
>> Try set STAGEDIR=/somewhere/else/ in make.conf
>
> The staging dir is not the problem, that is set correctly:
> stb@mirror:/usr/ports/net-p2p/btpd$ make -V STAGEDIR
> /var/ports/work/net-p2p/btpd/stage
>
> Because of these make.conf settings:
> ### Ports
> DISTDIR?=   /var/ports/distfiles
> WRKDIRPREFIX?=  /var/ports/work
> WRKDIR?=${WRKDIRPREFIX}${.CURDIR:S/${PORTSDIR}//}
>
> The problem is the package destination, which error message you can examine 
> in my original message.

Ah sorry, I misread the question.
Well, it shouldn't create packages unless you use "make package", you
can set PACKAGES to move it from /usr/ports/packages.

-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Staging and read-only /usr/ports

[William Grzybowski]

On Thu, Sep 26, 2013 at 6:52 PM, Stefan Bethke  wrote:
> Guys,
>
> I've noticed that more and more ports are trying to build a package 
> /usr/ports/category/port/port-version.tgz. Since my /usr/ports is mounted 
> read-only (via nullfs), this fails. I've looked through Mk/*.mk trying to 
> figure out how I can redirect this to another dir. Is PACKAGES the way to go? 
> What if I don't want to keep packages around?

Try set STAGEDIR=/somewhere/else/ in make.conf



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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"

[RFC] Stage support for easy_install

[William Grzybowski]

Hi,

I made an attempt to support stage for easy-install, you can find the patch 
here http://people.freebsd.org/~wg/easyinstall-stage.txt

Aprrently it works :), let me know what you think.


Cheers,
___
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/179722: [patch] graphics/gifsicle: update to 1.71

[William Grzybowski]

On Mon, Jul 29, 2013 at 12:32 PM, Alexander Milanov  wrote:
> Hi committers,
>
> PR ports/179722 reached maintainer timeout. Can someone please take care of
> it?

Done

Thanks

-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: I want to maintain devel/fpp

[William Grzybowski]

Last I heard fortran@ was going to maintain it.

On Fri, Jul 19, 2013 at 11:42 AM, Anton Shterenlikht  wrote:
>
> ___
> 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"



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: Fetching from Github don't work

[William Grzybowski]

Update your ports tree. The site url has been updated yesterday.

On Tue, Jul 16, 2013 at 6:48 AM, Grzegorz Blach  wrote:
> I can't fetch tarballs from github, they are fetched only from FreeBSD
> mirror. For example:
>
> => ninja-1.3.4.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
> => Attempting to fetch
> https://nodeload.github.com/martine/ninja/legacy.tar.gz/v1.3.4?dummy=/ninja-1.3.4.tar.gz
> fetch:
> https://nodeload.github.com/martine/ninja/legacy.tar.gz/v1.3.4?dummy=/ninja-1.3.4.tar.gz:
>  Service Unavailable
> => Attempting to fetch
> http://nodeload.github.com/martine/ninja/legacy.tar.gz/v1.3.4?dummy=/ninja-1.3.4.tar.gz
> fetch:
> http://nodeload.github.com/martine/ninja/legacy.tar.gz/v1.3.4?dummy=/ninja-1.3.4.tar.gz:
>  Connection refused
> => Attempting to fetch
> http://cloud.github.com/downloads/martine/ninja/ninja-1.3.4.tar.gz
> fetch:
> http://cloud.github.com/downloads/martine/ninja/ninja-1.3.4.tar.gz:
> Forbidden
> => Attempting to fetch
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ninja-1.3.4.tar.gz
> ninja-1.3.4.tar.gz100% of  145 kB   29 kBps
> 00m05s
> ===> Fetching all distfiles required by ninja-1.3.4,1 for building
>
>
> Have someone a solution for this issue?
>
>
> ___
> 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"



-- 
William Grzybowski
--
Curitiba/PR - Brasil
___
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: x11/lxpanel and clang

[William Grzybowski]

On Tue, Jun 18, 2013 at 12:41:56PM -0400, Kenta Suzumoto wrote:
> Forwarding to ports@ since kmoore just stopped maintaining the port.
> 
> Hi. lxpanel doesn't build with clang on my 9.1-release i386 system. I saw 
> this PR about it: https://www.freebsd.org/cgi/query-pr.cgi?pr=176650 but it 
> still doesn't build with clang.
> Switching back to GCC lets it build, however. It should either be marked as 
> requiring GCC or a real clang fix should be added (which I don't have at the 
> moment).

By the time it was committed it worked with clang, tested in redports :)
Fixed it in r321204.
___
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: Samba / TDB Port update

[William Grzybowski]

On Thu, Jun 6, 2013 at 8:03 AM, Jos Chrispijn  wrote:
> Dear port maintainer,
> When updating Samba, I get this error:
>
> ===>  tdb-1.2.11,1 conflicts with installed package(s):
>   samba34-3.4.17
>
>   They will not build together.
>   Please remove them first with pkg_delete(1).
> *** [check-build-conflicts] Error code 1
>
> I don't want to delete Samba as I use it very frequently. Can you advise?

You have to update samba to 3.5 or 3.6. Or keep with your current tdb version.



--
William Grzybowski
--
Curitiba/PR - Brasil
___
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: NZBGet | Port needs a refreshj

[William Grzybowski]

On Sun, May 26, 2013 at 11:07:21AM +0200, Jos Chrispijn wrote:
> Dear port maintainer,
> 
> Can you please refresh the FreeBSD 9.0 Stable NZBGet port?

There is a PR for it, ports/177839. I'll take care.
___
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: mailman compile problem

[William Grzybowski]

On Wed, Apr 3, 2013 at 8:23 AM, Mario Polario  wrote:
> Hi!
>
> I'm trying to compile new version of mailman on 9.1 release:
> 9.1-RELEASE-p1
>
> Whatever I try, I get stuck with:
>
> SyntaxError: invalid syntax
> /usr/local/bin/python3.3 ../build/bin/msgfmt.py -o
> zh_TW/LC_MESSAGES/mailman.mo zh_TW/LC_MESSAGES/mailman.po
>   File "../build/bin/msgfmt.py", line 86
> 0x950412deL,   # Magic
>   ^
> SyntaxError: invalid syntax
>
>
> Any help is more than welcomed!

mailman is not ready for python 3, use 2.7:

make PYTHON_VERSION=2.7 install

We should fix it with USE_PYTHON= 2.7- in Makefile.



--
William Grzybowski
--
Curitiba/PR - Brasil
___
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"

FreeBSD Port: sge-6.2.2.1_3

[Shaddox, William]

I'm looking into the SGE for my work and handling the scheduling of our 
automation processes.  The current setup works wonderfully but my boss and I 
are worried about the future since Oracle decided to not have an open source 
version.  I was wondering, what are your thoughts about the future of this port?

Also, I've been testing Open Grid Scheduler with FreeBSD 9.0-RELEASE AMD64 and 
I've got it working but not the complete project.  I've had to remove qmon, add 
some libraries from my SGE install, and edit 
/usr/local/GE2011.11p1/source/scripts/distinst to get the install to complete 
but it's working.  Here's what I have so far.

./aimk -spool-classic -no-java -no-jni -no-gui-inst -no-secure -no-qtcsh 
-no-qmon -only-depend
./scripts/zerodepend
./aimk -spool-classic -no-java -no-jni -no-gui-inst -no-secure -no-qtcsh 
-no-qmon depend
./aimk -spool-classic -no-java -no-jni -no-gui-inst -no-secure -no-qtcsh 
-no-qmon -debug
./scripts/distinst -local -libs fbsd-amd64 -- man common sge_qmaster sge_execd 
sge_shadowd sge_shepherd sge_coshepherd qstat qsub qalter qconf qdel qacct qmod 
qsh utilbin jobs qhost qmake qping qloadsensor.exe sgepasswd qquota

I had to add libXltree.so to 
/usr/local/GE2011.11p1/source/3rdparty/qmon/FREEBSD_AMD64/ and qtcsh to 
/usr/local/ogs/bin/fbsd-amd64/ to get it to startup.

For the environmental variables:
setenv SGE_ROOT /usr/local/ogs
setenv SGE_QMASTER_PORT 6444
setenv SGE_EXECD_PORT 6445
setenv SGE_CELL TEST
setenv SGE_CLUSTER_NAME p6444
setenv SGE_DELAY_TIME 120
setenv SGE_GET_ACTIVE_INTERVAL 90
setenv CHECK_INTERVAL 60

And my updated path list:
set path = (/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin 
/usr/local/bin $HOME/bin /usr/local/ogs/bin/fbsd-amd64/ 
/usr/local/ogs/utilbin/fbsd-amd64)

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

Apache lockf state after implementing SSL

[William Markert]

Hi,

I've just setup a new dev server using FreeBSD 9 p3.

FreeBSD ibanez.x.com 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun
12 02:52:29 UTC 2012
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

Apache/2.2.22 (FreeBSD) PHP/5.3.16 with Suhosin-Patch mod_ssl/2.2.22
OpenSSL/0.9.8q DAV/2


I've created some self-signed certificates and implemented SSL with
Apache. When I am looking at "top", I see that I have 1 httpd in the
select state, and the rest of my httpd child processes are in the lockf
state. Before implementing SSL, none of my httpd processes were ever in
the lockf state when idle. Are these processes in the lockf state because
of the use of SSL with apache?

I'll apologize ahead of time as I read the digests, but never really post
and this is really bugging me. If this has been answered or someone has a
link just let me know. Please let me know if I need to include more
information. Also, apologies if I haven't formatted anything correctly.

Thank you in advance.

Kind Regards,

Billy Markert
Partner
Markert Consulting, LLC
Billy AT markertconsulting DOT com

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

FreeBSD Port: p5-DBD-Oracle-1.14_3

[William Bulley]

t;(OCIHandleFree skipped during global destruction)" :
+(PL_dirty) ? "(OCIHandleFree skipped during global destruction)" :
 (imp_sth->nested_cursor) ?"(OCIHandleFree skipped for nested cursor)" 
: "");
 
-if (!dirty) { /* XXX not ideal, leak may be a problem in some cases */
+if (!PL_dirty) { /* XXX not ideal, leak may be a problem in some cases */
if (!imp_sth->nested_cursor) {
OCIHandleFree_log_stat(imp_sth->stmhp, OCI_HTYPE_STMT, status);
if (status != OCI_SUCCESS)
oci_error(sth, imp_sth->errhp, status, "OCIHandleFree");
}
@@ -2280,11 +2280,11 @@
SV *sv;
char *key;
I32 retlen;
hv_iterinit(hv);
while( (sv = hv_iternextsv(hv, &key, &retlen)) != NULL ) {
-   if (sv != &sv_undef) {
+   if (sv != &PL_sv_undef) {
  phs_t *phs = (phs_t*)(void*)SvPVX(sv);
 
 
  if (phs->desc_h && phs->desc_t == OCI_DTYPE_LOB)
ora_free_templob(sth, imp_sth, (OCILobLocator*)phs->desc_h);
@@ -2340,11 +2340,11 @@
STRLEN lna;
/* dbd_describe has already called ora_error()  */
/* we can't return Nullsv here because the xs code will */
/* then just pass the attribute name to DBI for FETCH.  */
croak("Describe failed during %s->FETCH(%s): %ld: %s",
-   SvPV(sth,na), key, (long)SvIV(DBIc_ERR(imp_sth)),
+   SvPV(sth,PL_na), key, (long)SvIV(DBIc_ERR(imp_sth)),
SvPV(DBIc_ERRSTR(imp_sth),lna)
);
 }
 
 i = DBIc_NUM_FIELDS(imp_sth);
--- oci8.c.orig 2012-09-05 12:16:27.0 -0400
+++ oci8.c  2012-09-05 12:17:35.0 -0400
@@ -1536,11 +1536,11 @@
fbh->ftype  = fbh->dbtype;
fbh->disize = fbh->dbsize;
p = "Field %d has an Oracle type (%d) which is not explicitly 
supported%s";
if (DBIS->debug >= 1)
PerlIO_printf(DBILOGFP, p, i, fbh->dbtype, "\n");
-   if (dowarn)
+   if (PL_dowarn)
warn(p, i, fbh->dbtype, "");
break;
}
if (DBIS->debug >= 3)
PerlIO_printf(DBILOGFP,
@@ -2056,11 +2056,11 @@
 
 hv_iterinit(imp_sth->all_params_hv);
 while( (sv = hv_iternextsv(imp_sth->all_params_hv, &p, &i)) != NULL ) {
int matched = 0;
phs_t *phs = (phs_t*)(void*)SvPVX(sv);
-   if (sv == &sv_undef || !phs)
+   if (sv == &PL_sv_undef || !phs)
croak("panic: unbound params");
if (phs->ftype != SQLT_CLOB && phs->ftype != SQLT_BLOB)
continue;
 
hv_iterinit(lob_cols_hv);

Regards,

web...

-- 
William Bulley Email: w...@umich.edu

72 characters width template ->|
--- Oracle.c.orig   2012-09-05 11:59:43.0 -0400
+++ Oracle.c2012-09-05 12:12:04.0 -0400
@@ -1493,11 +1493,11 @@
 XS_EUPXS(XS_DBD__Oracle__st_ora_execute_array); /* prototype to pass 
-Wmissing-prototypes */
 XS_EUPXS(XS_DBD__Oracle__st_ora_execute_array)
 {
 dVAR; dXSARGS;
 if (items < 4 || items > 5)
-   croak_xs_usage(cv,  "sth, tuples, exe_count, tuples_status, 
cols=&sv_undef");
+   croak_xs_usage(cv,  "sth, tuples, exe_count, tuples_status, 
cols=&PL_sv_undef");
 {
SV *sth = ST(0)
 ;
SV *tuples = ST(1)
 ;
@@ -1510,11 +1510,11 @@
 D_imp_sth(sth);
 int retval;
 #line 1513 "Oracle.c"
 
if (items < 5)
-   cols = &sv_undef;
+   cols = &PL_sv_undef;
else {
cols = ST(4)
 ;
}
 #line 127 "Oracle.xs"
@@ -1547,11 +1547,11 @@
 {
SV *sth = ST(0)
 ;
 #line 147 "Oracle.xs"
 D_imp_sth(sth);
-ST(0) = dbd_st_cancel(sth, imp_sth) ? &sv_yes : &sv_no;
+ST(0) = dbd_st_cancel(sth, imp_sth) ? &PL_sv_yes : &PL_sv_no;
 #line 1554 "Oracle.c"
 }
 XSRETURN(1);
 }
 
@@ -1569,11 +1569,11 @@
 ;
char *  pwd = (char *)SvPV_nolen(ST(2))
 ;
 #line 159 "Oracle.xs"
 D_imp_dbh(dbh);
-ST(0) = ora_db_reauthenticate(dbh, imp_dbh, uid, pwd) ? &sv_yes : &sv_no;
+ST(0) = ora_db_reauthenticate(dbh, imp_dbh, uid, pwd) ? &PL_sv_yes : 
&PL_sv_no;
 #line 1576 "Oracle.c"
 }
 XSRETURN(1);
 }
 
@@ -1621,19 +1621,19 @@
 /* added by lab: */
 /* LAB do something about length here? see above comment */
 OCILobCharSetForm_log_stat( imp_dbh->envhp, imp_dbh->errhp, locator, 
&csform, status );
 if (status != OCI_SUCCESS) {
 oci_error(dbh, imp_dbh->errhp, status, "OCILobCharSetForm");
-   ST(0) = &sv_undef;
+ 

RE: FreeBSD Port: mysql-server-5.0.92

[Shaddox, William]

I forgot to add that I'm willing to help, I already have 7.1.13 and 7.2.2 of 
mysql cluster working and I'd be glad to help you.  I've already posted to the 
forms.  I'm Meroverance

http://forums.freebsd.org/showthread.php?p=161103


From: Shaddox, William
Sent: Friday, January 06, 2012 4:24 PM
To: 'a...@freebsd.org'
Cc: 'po...@freebsd.org'
Subject: FreeBSD Port: mysql-server-5.0.92

I'm doing testing with running MySQL-cluster versions 7.1.13 and 7.2.2 on 
FreeBSD and I was wondering if you had any plans for porting MySQL-cluster to 
FreeBSD?  If you do, what might the time frame be for a MySQL-cluster port?

I know 7.2.2 is beta, so I wouldn't want that to be ported, I just wanted to 
see the differences with the changes they added from the 5.1 to 5.5 version 
change they did.

   William M. Shaddox

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

FreeBSD Port: mysql-server-5.0.92

[Shaddox, William]

I'm doing testing with running MySQL-cluster versions 7.1.13 and 7.2.2 on 
FreeBSD and I was wondering if you had any plans for porting MySQL-cluster to 
FreeBSD?  If you do, what might the time frame be for a MySQL-cluster port?

I know 7.2.2 is beta, so I wouldn't want that to be ported, I just wanted to 
see the differences with the changes they added from the 5.1 to 5.5 version 
change they did.

       William M. Shaddox

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

compile time error in audio/xmixer 8.2-STABLE

[William Bulley]

I just updated my ports tree (csup -L2 ports-supfile) and while I was
building audio/xmixer I got the following unexpected error:

===>  Building for xmixer-gtk-0.9.4_6
[snip]
cc -O2 -fno-strict-aliasing -pipe -std=gnu89 -I/usr/local/include/  
-I/usr/local/include -DDEFAULT_MIXER=\"/dev/mixer\"  -DOSS -I. -I./icons  
-DVERSION=\"0.9.4\"  `pkg-config gtk+ --cflags` -c gui_gtk.c
gui_gtk.c:480: warning: cast from pointer to integer of different size
gui_gtk.c:480: error: initializer element is not constant
gui_gtk.c:480: error: (near initialization for 'menu_items[1].callback_action')
gui_gtk.c:481: warning: cast from pointer to integer of different size
gui_gtk.c:481: error: initializer element is not constant
gui_gtk.c:481: error: (near initialization for 'menu_items[2].callback_action')
gui_gtk.c:485: warning: cast from pointer to integer of different size
gui_gtk.c:485: error: initializer element is not constant
gui_gtk.c:485: error: (near initialization for 'menu_items[6].callback_action')
gui_gtk.c: In function 'gui_main':
gui_gtk.c:655: warning: cast from pointer to integer of different size
*** Error code 1

Stop in /usr/ports/audio/xmixer/work/xmixer.
*** Error code 1

Stop in /usr/ports/audio/xmixer.

What is this compile error caused by and how do I workaround it?  Thanks.

Regards,

web...

-- 
William Bulley Email: w...@umich.edu

72 characters width template ->|
___
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"

FreeBSD Port: pdftk-1.44

[Shaddox, William]

We use pdftk for shuffling pdfs together and adding watermarks to a pdf with 
the stamp command.  We've found that if we start with a pdf that's over 2GB in 
size, pdftk will give the error below and stop working.  Is there any work 
around for this or is this a known issue?  I've checked the FAQ but I didn't 
see anything about this size limitation.

Our system is running FreeBSD version 8.2 -RELEASE AMD64 and pdftk version 1.44


Error: Failed to open PDF file:
   Output_name.pdf
Errors encountered.  No output created.
Done.  Input errors, so no output created.


   William M. Shaddox

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

can't build graphics/xfig-3.2.5b on 8.2-STABLE nor databases/p5-DBD-Oracle with lang/perl5.14

[William Bulley]

First there is the xfig issue:

No matter what the setting is for I18N (WITH or WITHOUT) there is this:

cc -c -O2 -fno-strict-aliasing -pipe   -I/usr/local/include 
-I/usr/local/include/libpng -I/usr/local/include/X11 -I. -I/usr/local/include   
 -DCSRG_BASED  -DFUNCPROTO=15 -DNARROWPROTO 
 -DUSE_INLINE -DUSE_XPM -DXAW3D -DXAW3D1_5E 
-DUSE_JPEG -DI18N  -DNEWARROWTYPESe_edit.c
e_edit.c: In function 'generic_window':
e_edit.c:3214: warning: cast from pointer to integer of different size
e_edit.c: In function 'str_panel':
e_edit.c:4252: error: 'XtNinternational' undeclared (first use in this function)
e_edit.c:4252: error: (Each undeclared identifier is reported only once
e_edit.c:4252: error: for each function it appears in.)
*** Error code 1

Stop in /usr/ports/graphics/xfig/work/xfig.3.2.5b.
*** Error code 1

Stop in /usr/ports/graphics/xfig.
*** Error code 1

I tracked this down to a problem in the Imakefile around line 153:

   #define I18N

This line was not commented out when building xfig using:

   # make install   (and WITHOUT_I18N=true inside /var/db/ports/xfig/options)

Looking further I found these two lines:

   -XCOMM #define I18N
   +#define I18N

inside the /usr/ports/graphics/xfig/files/patch-Imakefile patch file.  I think
this may be incorrect.  After commenting out the #define in the Imakefile, the
build of xfig was successful.

Secondly, I found that building databases/p5-DBD-Oracle when Perl 5.14 (from
lang/perl5.14) was present failed in the compilation of the Oracle.c file.
It seems that several Perl constants sv_undef, sv_yes, and sv_no (and others)
changed between Perl 5.12.3 and Perl 5.14 to PL_sv_undef, PL_yes, and PL_sv_no,
respectively.  I didn't take the time to debug this further since I had other
Perl 5.14 issues that forced me to completely rebuild my system from scratch
starting with Perl 5.12.3 (lang/perl5.12) this time.  Once I had Perl 5.12.3
built, databases/p5-DBD-Oracle built just fine.

My other problems with Perl 5.14 were observed trying to launch apache2 (2.2.19)
with mod_perl2 (2.0.5).  Those problems also went away once I rebuilt my ports
starting with Perl 5.12.3 version.  This makes me suspect Perl 5.14 changes or
the effect those changes have had on other ports in the ports tree.

Regards,

web...

--
William Bulley Email: w...@umich.edu

72 characters width template ->|


___
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: can't build graphics/xfig-3.2.5b on 8.2-STABLE

[William Bulley]

According to Anton Shterenlikht  on Thu, 06/23/11 at 06:53:
> 
> Perhaps x11-toolkits/Xaw3d and x11-toolkits/libXaw need updating.
> 
> I got xfig-3.2.5b working fine on -current.
> 
> Have you followed /usr/ports/UPDATING entry 20110605 (gnutls update) ?

The entire system was upgraded June 21.  The buildworld/installworld
of FreeBSD 8.2-STABLE, every single port was rebuild from source.

When I got to xfig (which normally builds just fine) it caused the
error.  I have these ports:

   Xaw3d-1.5E_4A 3-D Athena Widget set that looks like Motif
   libXaw-1.0.8,1  X Athena Widgets library

How do I know if these are in need of updating or not?  I did the
normal csup -L2 ports-supfile as part of the above rebuild, so I
expect these two ports are as up-to-date as could be as of 6/21.

Regards,

web...

--
William Bulley Email: w...@umich.edu

72 characters width template ->|
___
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"

can't build graphics/xfig-3.2.5b on 8.2-STABLE

[William Bulley]

No matter what the setting for I18N is (WITH or WITHOUT) there is this:

cc -c -O2 -fno-strict-aliasing -pipe   -I/usr/local/include 
-I/usr/local/include/libpng -I/usr/local/include/X11 -I. -I/usr/local/include   
 -DCSRG_BASED  -DFUNCPROTO=15 -DNARROWPROTO 
 -DUSE_INLINE -DUSE_XPM -DXAW3D -DXAW3D1_5E 
-DUSE_JPEG -DI18N  -DNEWARROWTYPESe_edit.c
e_edit.c: In function 'generic_window':
e_edit.c:3214: warning: cast from pointer to integer of different size
e_edit.c: In function 'str_panel':
e_edit.c:4252: error: 'XtNinternational' undeclared (first use in this function)
e_edit.c:4252: error: (Each undeclared identifier is reported only once
e_edit.c:4252: error: for each function it appears in.)
*** Error code 1

Stop in /usr/ports/graphics/xfig/work/xfig.3.2.5b.
*** Error code 1

Stop in /usr/ports/graphics/xfig.
*** Error code 1


Regards,

web...

--
William Bulley Email: w...@umich.edu

72 characters width template ->|
___
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"

FreeBSD Port: rubygem-rails-3.0.0

[William DiNoia]

I got an error in upgrading to rubygem-rails-3.0.0. The gem is installed 
but portmaster(?) returns an error...


Successfully installed rails-3.0.0
1 gem installed
Installing RDoc documentation for rails-3.0.0...
File not found: lib
*** Error code 1

Stop in /usr/ports/www/rubygem-rails.
*** Error code 1

Stop in /usr/ports/www/rubygem-rails.

===>>> Installation of rubygem-rails-3.0.0 (www/rubygem-rails) failed
===>>> Aborting update
___
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"

FreeBSD Port: gcalctool-5.30.2,2

[William DiNoia]

 I was wondering if gcalctool needs all of the listed gnome 
requirements to build. The Debian stable package of gcalctool 5.22-3, 
which is a little dated, only requires gconf2, gnome-icon-theme, libatk, 
libc6, libc6.1, libgconf2, libglade2, libglib2, libgtk, libpango, and 
libxml.

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

FreeBSD Port: virtualbox-ose-3.1.6_2

[William DiNoia]

http://pynej.blogspot.com/2010/04/patch-for-virtualbox-not-working-on.html
___
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"

FreeBSD Port: virtualbox-ose-3.1.4

[William DiNoia]

I'm getting an Error code 71 while building virtualbox-ose:

/bin/ln -sf /usr/local/lib/virtualbox/VBoxSDL /usr/local/bin/
install  -s -o root -g wheel -m 555 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.4_OSE/out/freebsd.x86/release/bin/VBoxTestOGL 
/usr/local/lib/virtualbox/
install: 
/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.4_OSE/out/freebsd.x86/release/bin/VBoxTestOGL: 
No such file or directory

*** Error code 71

Stop in /usr/ports/emulators/virtualbox-ose.
*** Error code 1

Stop in /usr/ports/emulators/virtualbox-ose.

===>>> Installation of virtualbox-ose-3.1.4 (emulators/virtualbox-ose) 
failed

===>>> Aborting update

===>>>  complete

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

FreeBSD Port: pcb-20081128_1

[William Bulley]

I am building cad/pcb on 7.2-STABLE and I get this:

cc -std=gnu99 -DNDEBUG -O2 -fno-strict-aliasing -pipe
-I/usr/local/include -I/usr/local/include  -I/usr/local/include
-Wall -Wdeclaration-after-statement  -pthread -L/usr/local/lib
-rdynamic -o pcb action.o autoplace.o autoroute.o buffer.o
change.o clip.o command.o compat.o copy.o create.o crosshair.o
data.o djopt.o draw.o drill.o edif.o error.o file.o find.o flags.o
fontmode.o heap.o insert.o intersect.o line.o lrealpath.o main.o
mirror.o misc.o move.o mtspace.o mymem.o netlist.o parse_l.o parse_y.o
polygon.o polygon1.o puller.o print.o rats.o remove.o report.o res_parse.o
res_lex.o rotate.o rtree.o rubberband.o search.o select.o set.o strflags.o
thermal.o undo.o vector.o vendor.o hid/common/actions.o hid/common/flags.o
hid/common/hidinit.o hid/common/hidnogui.o hid/common/extents.o
liblesstif.a liblpr.a libbom.a libgerber.a libnelma.a libpng.a libps.a
-lXm -lXpm -lXmu -lXt -lXext -lSM -lICE -lX11 -lfl -lm-lXrender
-L/usr/local/lib -R/usr/local/lib   -L/usr/local/lib -L/usr/local/lib -lgd -lgd
main.o(.text+0xc8e): In function `main':
: undefined reference to `bindtextdomain'
main.o(.text+0xca2): In function `main':
: undefined reference to `bind_textdomain_codeset'
gmake[4]: *** [pcb] Error 1
gmake[4]: Leaving directory `/usr/ports/cad/pcb/work/pcb-20081128/src'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/usr/ports/cad/pcb/work/pcb-20081128/src'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/usr/ports/cad/pcb/work/pcb-20081128/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/cad/pcb/work/pcb-20081128'
gmake: *** [all] Error 2
*** Error code 1

My build line in /usr/ports/cad/pcb was:

  # make WITH_MOTIF_GUI=yes install

It builds fine if I use:

  # make install

Regards,

web...

--
William Bulley Email: w...@umich.edu

72 characters width template ->|
___
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"

FreeBSD Port: Thunar-0.9.3

[William DiNoia]

With respect to Thunar's dependencies, I was wondering if 
xfce4-mcs-manager and xfce4-panel are strictly required? The Debian 
package of Thunar lists xfce4-panel as a recommendation and makes no 
mention of xfce4-mcs-manager.


I've been using openbox and I installed the Thunar port for file 
management but I was surprised when the config dialogs came up for 
xfce4-mcs-manager and xfce4-panel.


thanks,
Will


___
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/128999: [vuxml] [patch] update audio/streamripper to 1.64.0, fix CVE-2008-4829

[William Palfreman]

2008/11/24 Volker <[EMAIL PROTECTED]>:
> On 11/24/08 19:55, William Palfreman wrote:
>> 2008/11/23  <[EMAIL PROTECTED]>:
>>> Synopsis: [vuxml] [patch] update audio/streamripper to 1.64.0, fix 
>>> CVE-2008-4829
>>
>> Can we not have these on the freebsd-secuirty list please?  I
>> subscribe to freebsd-security to get security alerts, not to get
>> emails every time a port is changed.
>>
>> William Palfreman
>
> You should better head over to security-advisories@ if you're only
> interested in SA's. Claiming about reading security related issues on a
> security mailing list sounds like fun.
>
> I appreciate Eygenes' work.

That's nice.  I am sure it is very useful on the ports mailinglist
where it belongs.  I also greatly enjoy the frequent interesting and
informed discussion on the security mailinglist - of which Eirik
Overby's thread recently about syn+fin is one example.  But all these
ports announcements, raw patches, garbled html etc. I could really do
without.  It is why there are separate lists.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ports/128999: [vuxml] [patch] update audio/streamripper to 1.64.0, fix CVE-2008-4829

[William Palfreman]

2008/11/23  <[EMAIL PROTECTED]>:
> Synopsis: [vuxml] [patch] update audio/streamripper to 1.64.0, fix 
> CVE-2008-4829

Can we not have these on the freebsd-secuirty list please?  I
subscribe to freebsd-security to get security alerts, not to get
emails every time a port is changed.

William Palfreman
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD Port: sysutils/daemontools

[William Olson]

Hello,

I am having issues installing daemontools from the ports system. Please see
below:

whateva# pwd
/usr/ports/sysutils/daemontools
whateva# make install clean
===>  Vulnerability check disabled, database not found
===>  Found saved configuration for daemontools-0.76_12
=> daemontools-0.76-man-20010714.tar.gz doesn't seem to exist in
/usr/ports/distfiles/.
=> Attempting to fetch from http://smarden.org/pape/djb/manpages/.
fetch:
http://smarden.org/pape/djb/manpages/daemontools-0.76-man-20010714.tar.gz:
Operation timed
out
=> Attempting to fetch from
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
fetch:
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/daemontools-0.76-man-20010714.tar.gz:
File
unavailable (e.g., file not found, no access)
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/ and try again.
*** Error code 1

Stop in /usr/ports/sysutils/daemontools.
*** Error code 1

Stop in /usr/ports/sysutils/daemontools.
whateva#

I took a look at freshports this morning and saw this:

http://www.freshports.org/search.php?query=daemontools&search=go&num=10&stype=name&method=match&deleted=excludedeleted&start=1&casesensitivity=caseinsensitive

It looks like it's now restricted? Please let me know.

-- 
-
My favorite quote from Everybody loves Raymond:

I'm tired. Can you just call yourself an idiot?

-

Bill
http://www.antagonism.org/qmr-faq.shtml
http://www.catb.org/~esr/faqs/smart-questions.html#before
http://www.goodcleanemail.com
http://www.freebsdrocks.net
http://listarchive.qmailrocks.org/splash/index.html
Live Help also available on IRC Server Freenode in channel #qmr
QMR List Archive is available at http://dir.gmane.org/gmane.mail.qmail.qmr
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Web Design / IT / Computer Support available in Durango.

[William]

Good Morning!
I wanted to drop you a note and let you know that I am a web designer with 12+ 
years of experience available for work in the Durango and surrounding areas. I 
am fluent in Logo & Print design, Photoshop, Flash, HTML, PHP, MYSQL databases, 
Ecommerce & Search Engine Optimization.

I am also MECP and HP LaserJet certified and am available for all networking, 
computer repair and mainenance work.

My list of services include:
Custom Web & Logo Design
Website Maintenance & Updates
Print Layout & Design
Website Hosting
Custom Online Applications & Databases
Ecommerce
Search Engine Optimization
Network Setup (Including Wireless) & Maintenance
Computer Maintenance, Repair & Upgrades

HP LaserJet Maintenance & Repair


Please feel free to contact me if you would like to chat or see examples of my 
work.


Sincerely,
William Glenn
1.970.749.3829

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