USES = libtool and missing .la files [WAS Re: pkg-plist for devel/glib20]

2014-09-08 Thread gtodd


On Sun, 7 Sep 2014, Cary wrote:

Here it shows a diff for pkg-plist of port devel/glib20:

http://svnweb.freebsd.org/ports/head/devel/glib20/pkg-plist?r1=324037r2=366944

Five files which the port is building are not being installed. They are:

lib/libgio-2.0.la
lib/libglib-2.0.la
lib/libgmodule-2.0.la
lib/libgobject-2.0.la
lib/libgthread-2.0.la

In my directory /usr/ports/devel/glib20:

$ find work/ -type f -name libg[ilmot]*-2.0.la
work/glib-2.36.3/gio/libgio-2.0.la
work/glib-2.36.3/gthread/libgthread-2.0.la
work/glib-2.36.3/glib/libglib-2.0.la
work/glib-2.36.3/gmodule/libgmodule-2.0.la
work/glib-2.36.3/gobject/libgobject-2.0.la

So far two other builds have failed for me because
two of the above listed files were not found.
Ports that failed to build were :
gnome-desktop-2.32.1_4 x11/gnome-desktop
xfce4-desktop-4.10.2_2 x11-wm/xfce4-desktop


For the last few days I have been seeing the same thing scattered around 
the ports tree. It seems various libtool archive files (e.g. the above as 
well as libiconv.la, liffi.la, probably others ...) are no longer being 
installed. When subsequent builds are run they are unable to find libtool 
archive dependencies. e.g. libpurple will fail not finding 
libgobject.2.0.la ... copying libgobject.2.0.la from previous package or 
backup will allow the build to proceed until another missing *.la file 
causes the build to fail. And so on ...


I have not been continuously building ports so I can't say when the 
failures started but a larger number of ports began to include 
'USES=libtool ' about a week ago. Perhaps pkg-plist files are not

including the files due to this change.

/usr/port/UPDATING doesn not warn of any problems or fallout from 
'USES=libtool'. How best to resolve this?


cheers,

G. Todd
___
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


sysutils/fsc (fbsd service monitor) broken build w/ clang-devel-3.4.r181598_3

2013-05-28 Thread gtodd


Hi and thanks for your work on fsc service monitoring tool.

I have been using it for a while but haven't tried to rebuild it very 
often until today.  It may have worked with earlier versions of clang.


PR filed. Here is the error message.

Warning: Object directory not changed from original 
/usr/ports/sysutils/fsc/work/fsc/fscd
clang -O2 -pipe -fno-strict-aliasing  -std=c99 -std=gnu99 
-Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall 
-Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual 
-Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
-Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls 
-Wold-style-definition -Wno-pointer-sign -c fscd.c
fscd.c:977:13: error: variable 'sendstr' is used uninitialized whenever 
'if' condition is false

  [-Werror,-Wsometimes-uninitialized]
} else if (strcmp(arglst[0], status) == 0) {
   ^~~~
fscd.c:984:16: note: uninitialized use occurs here
send(sock_fd, sendstr, strlen(sendstr), 0);
  ^~~
fscd.c:977:9: note: remove the 'if' if its condition is always true
} else if (strcmp(arglst[0], status) == 0) {
   ^~
fscd.c:934:15: note: initialize the variable 'sendstr' to silence this 
warning

char *sendstr;
 ^
  = NULL
1 error generated.
*** [fscd.o] Error code 1

Stop in /usr/ports/sysutils/fsc/work/fsc/fscd.
*** [all] Error code 1

Stop in /usr/ports/sysutils/fsc/work/fsc.
*** [do-build] Error code 1

Stop in /usr/ports/sysutils/fsc.

:w

___
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


x11-toolkits/pango update to 1.30 fails to build

2013-03-10 Thread gtodd


Posting this for the benefit of search engines and seekers.

Following the most recent ports update to pango (svn 313633) I was unable 
to get it to build properly until I rebuilt cairo with this bit flipped:


WITH GLIB Enable GObject Functions Feature

A bunch of interdependent ports (glib gtk gobject-introspection etc) were 
were also rebuit, so I'm not sure what broke but it seems similar to what 
is described here:


http://lists.freebsd.org/pipermail/freebsd-ports/2012-June/075519.html


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


zsh/pkg - solaris completions used for pkgNG

2012-10-18 Thread gtodd


Just a heads up (or reminder) to zsh and pkg maintainers that - at least 
with zsh-5.0 - zshell's completion is picking up solaris pkg commands as 
targets. I remember a discussion of tab completion targets for pkgNG from 
several months ago but I'm not sure this particular issue was raised.


e.g.

~/ % pkg info -x pkg- zsh
pkg-1.0.1  New generation package manager
zsh-5.0.0  The Z shell

~/ % pkg [TAB]
add-property-value list   unavoid
avoid  mediator   unfreeze
change-facet   property   uninstall
change-variant publisher  unset-mediator
contents   purge-history  unset-property
facet  rebuild-index  unset-publisher
fixrefreshupdate
freeze remove-property-value  update-format
help   revert variant
historysearch verify
image-create   set-mediator   version
info   set-property
installset-publisher

The completions come from:

/usr/local/share/zsh/5.0.0/functions/Completion/Solaris/_pkg5

A fix is to write completion for pkgNG one day ;-) or, for now, to simply 
remove that file from the zsh port. My guess is the _pkg5 functions can be 
hacked a bit to fit the needs of a very simple pkgNG but I haven't started 
doing that yet.


Regards,

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