[SOLVED] Re: Baikal caldav and documentroot
On 03/19/15 11:29, Da Rock wrote: Just a quick one: is anyone using Baikal for caldav? Is there a reason it _must_ be documentroot? I haven't been successful in finding out the why - no docs either. Bit of a pain in the butt with my current setup, but if I _must_ then I guess I'll have to figure out how to adjust. Well I figured it out, and I thought I'd let those interested ( :) ) know what the solution is to this one. There are practically no docs to this webapp, so I thought I'd check out the rewrite rules in apache (of which I haven't had anything to do with as yet) to see if that might make it work for me. There is a rewrite rule already referencing .well-known/caldav|carddav, and looking at this I decided to run a search to see what might be happening. Apparently this an rfc expectation for easy implementation by clients - although I have yet to find a client that does use it! So, while it is best practice for this to be documentroot - namely this particular rfc requirement, the rewrite rule is supposed to take care of this. An adjustment to this will allow the sysadmin to allocate baikal to a subfolder. This will allow access to baikal, but it still won't allow it to be used as a caldav - yet. To get this working fully, you need to go into system settings in baikal admin and change the variables for the _web path_ only. Keep in mind this is for the port install only, it may be different for a manual install. To summarise, this is what you need to do to make baikal work as a subfolder of another vhost (not necessarily documentroot): 1. Adjust the rewrite rule in your apache setup to reflect the new home you want your caldav in: RewriteEngine On RewriteRule /.well-known/carddav new home/card.php [R,L] RewriteRule /.well-known/caldav new home/cal.php [R,L] 2. Navigate to the baikal admin page and go to system settings and adjust the top 2 variables that relate to the absolute web path _only_. Do not touch the server path settings! PROJECT_BASEURI . new home/cal.php/ PROJECT_BASEURI . new home/card.php/ 3. Test! Mat, perhaps this will be a good note in the port install message as well, as its not up to the port maintainer to take care of documentation of an application itself. Either that or maybe a readme somewhere in either share/ or the baikal/ directory. A note that this is at the sysadmins own risk might be in order too :) Having said that, it would be good if all projects did at least some basic documentation for the apps created! HTH ___ 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
heimdal/krb5 conflicts
I've asked around trying to get a quick answer on this, but it seems it is not too well known. Reasonably recently I've installed krb5 on a system but only in the past few weeks have I run into some real trouble with a conflict with heimdal trying to install as a port, so I don't know which exactly is the cause of the issue. Regardless, how do I tell my ports to stop insisting on using heimdal? I've googled, but everything is like a decade old. I have tried a few things from these though, but to no avail. My make.conf has these options in it now: NO_KERBEROS=YES KRB5_HOME=/usr/local(also tried /usr/local/lib/krb5) #WITH_HEIMDAL=NO KRB5_IMPL=MIT(and mit) What else can I do? What is the magic incantation to make this stupid issue go away :) ? 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
Mesa and libICE issues
I'm just getting used to tinderbox and pkgng as well, which is adding a new dimension to the issue; this is a new tinderbox setup though, so it shouldn't be an issue. I'm trying to do a new build for a new FreeBSD 10 install, and I'm running into issues with building for Xorg. It does seem rather odd though. Firstly, Mesa related ports lib/dri and lib/GL are failing with configure errors, with a message that a sanity check on /lib/cpp fails (which the /lib/cpp is not around), and looking at the log it shows that it is failing when it runs cc -V saying it is missing input. I tried the command myself and it doesn't work. It also is only those two ports as far as I can see atm. Second, lib/SM is saying it can't find libICE (missing dependency ORIGIN). I'm still trying to learn how to get around tinderbox, but I updated the ports tree again and rmPort on each of those, but still get the same errors. Can someone see how to get around these issues? 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: fixing missing launch icons
On 11/11/12 04:08, Beeblebrox wrote: Unfortunately, it was too soon to tag the problem solved. I tried an entry like so: Encoding=UTF-8 Name=Emma-SQL GenericName=Emma-SQL Comment=Emma-SQL Manager TryExec=emma Exec=emma Icon=emma Type=Application Categories=Programming Directory=Programming 1. This did not show up anywhere in any sub-menus. 2. When I change the desktop session I use from say Gnome to Fluxbox, the Applications menu changes completely and not only has a very different sub-menu (Directory) structure than Gnome but also many of the menu items are missing, while some menu icons which were not in Gnome become visible. Emma-SQL did not show up in the Fluxbox menu either, btw. 3. Categories has influence on this as well, because to fix a multiple-entry item I just removed the other categories and the icons reverted to a single sub-menu. Thanks and Regards. Don't know precisely why this entry didn't show up (if it is exactly as it is here), but there is an item that tells it which DE to allow use under such as Gnome, KDE, etc. I don't have the exact details in front of me now, but looking at the specs under freedesktop.org should shed light on it. HTH ___ 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: wine/i386 for FreeBSD/amd64 port (aka wine-fbsd64)
On 11/04/12 21:31, Chris Rees wrote:
On 4 November 2012 11:16, Thomas Mueller muelle...@insightbb.com wrote:
from David Naylor naylor.b.da...@gmail.com:
Hi List,
# Executive Summary
Over the past years I have been maintaining the wine-fbsd64 port (see
http://mediafire.com/wine_fbsd64 for more). The port itself effectively
does
static linking (it bundles all the libraries wine needs) with scripts to
bootstrap the environment to easily use wine from FreeBSD/amd64. There is
also a script to install the i386 nVidia graphic drivers so that wine has
access to nVidia accelerated graphics from FreeBSD/amd64.
I would like to propose this port gets included in the port's collection and
would like to get feedback, your comments please :-).
P.S. I'm not subscribed to the list, so please ensure I'm cc'ed in the
discussion.
# Details of the Port
Please see attached for the actual port.
## Port Preamble
This port is a slave port to emulators/wine(-devel). The master port needed
to be modified (already done):
- to conditionally set USE_LDCONFIG (if USE_LDCONFIG32 was not set)
- to allow the library directory to be changed (see WINELIBDIR)
- to allow configure arguments to be appended
## Port Targets
The port itself does the following in the preamble:
- specifies the pkg(de)install script to handle nVidia driver patching
- overrides ACTUAL-PACKAGE-DEPENDS (all depends are bundled with the port)
- defined the library directory to ${PREFIX}/lib32
- defined the binary directory to ${PREFIX}/bin32
- patches the PLIST to refer to lib32 (not lib)
- defined USE_LDCONFIG32 appropriately
The post-install-script target:
- Installs the files/binbounce file in ${PREFIX}/bin for each
${PREFIX}/bin32
file (hard linked)
- Finds all linked library, copies them to ${PREFIX}/lib32, and added them
to
the plist
- Finds all dlopen'ed libraries, copies them to ${PREFIX}/lib32, and added
them to the plist
- Installs the nVidia patch file
- Run the (PRE-|POST-)INSTALL script
The post-package-script (run only if WITH_PKGNG is defined):
- Amends the package so the arch label to 64bit
## Port scripts (in files/)
The binbounce file does the following to transparently fix the environment
to
allow seamless running of the wine programs:
- determines the location of the TARGET (follows symbolic links to itself)
- fixes LD_LIBRARY_PATH if in an i386 environment (so lib32, lib32/wine is
found)
- fixes LD_32_LIBRARY_PATH if in an amd64 environment (so lib32,
lib32/wine,
/usr/lib32)
- fixes PATH (so bin32 is found)
- passes execution to the counterpart in bin32
The patch-nvidia.sh file does the following:
- Downloads the nVidia distfile for i386 (iff nVidia amd64 driver is
installed)
- Installs the required libraries into ${PREFIX}/lib32
- When run from the install script it does _not_ download the distfile,
only
installs the libraries iff the distfiles are already downloaded.
# Shortcomings of the port
The following are shortcomings that I am aware of:
- Can only be compiled in an i386 environment, but the resulting package is
*intended* for amd64 (although works fine in an i386 environment)
- If, somehow, there is a recursive calling of wine programs then
LD_(32_)LIBRARY_PATH and PATH will continue to grow with every iteration.
- The pkgng ports cannot be installed in an i386 environment as they are
labelled for amd64.
# Testing
The ports published on mediafire have been tested by many users. The port
itself works flawlessly however there have been some reports about some
flaws
in the 32-bit compatibility layer of the kernel (although I cannot remember
the specifics now).
To produce the package on an amd64 system do the following:
# (cd /usr/ports/emulators/; patch -p0 /path/to/diff)
# make -C /usr/src world DESTDIR=/i386 TARGET=i386
# mount -t devfs devfs /i386/dev
# mkdir /i386/usr/ports
# mount -t nullfs /usr/ports /i386/usr/ports
# chroot make -C /usr/ports/emulators/wine-fbsd64 package WITH_PKGNG=yes
The package wine-fbsd64-1.5.16,1.txz (in pkgng format) will be available
from
/usr/ports/packages/All/
# Conclusion
It is based completely off the main port and uses the hack to,
effectively, use static linking (or bundling of libraries). In a
sense it is a complete, yet quite stable and encompassing, hack.
- David ;-)
It would be nice to have wine-fbsd64 as a port, but that might unfortunately
deprive the user of certain flexibility.
Also, nVidia support should be an option, since users with other graphics
cards might have no use for it.
I would really prefer to build the i386 FreeBSD system as a separate part,
including kernel,
since some users, myself included, might want to run an actual FreeBSD i386,
especially on an older computer. So one could build this FreeBSD i386 on a
USB stick or USB hard drive, and then be able to run wine on an i386 system.
Would wine-fbsd64 be a separate port, or would it
GRegexp crashing
I just installed this to help me with some of my programming (got sick
of using online ones), only to find it won't run at all. There is no
error, but this is what I got from truss:
v\0\0\0\0\0\0\0\0\0\n\0\0\0...,4096) = 1428 (0x594)
read(3,0x80c9ba02c,4096) ERR#35 'Resource temporarily
unavailable'
read(3,0x80c9ba02c,4096) ERR#35 'Resource temporarily
unavailable'
read(3,0x80c9ba02c,4096) ERR#35 'Resource temporarily
unavailable'
read(3,0x80c9ba02c,4096) ERR#35 'Resource temporarily
unavailable'
__sysctl(0x7fffc5c0,0x2,0x7fffc617,0x7fffc5b8,0x0,0x0) = 0 (0x0)
open(/home/admin/.Xdefaults-laptop3.herveybayaustralia.com.au,O_RDONLY,00)
ERR#2 'No such file or directory'
stat(${prefix}/share/gregexp/glade/gregexp.glade,0x7fffd810) ERR#2
'No such file or directory'
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-WARNING **: could not find glade file
'${prefix}/share/gregexp/glade/gregexp.glade'
write(2,\n(gregexp:14404): libglade-WARN...,111) = 111 (0x6f)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_signal_autoconnect:
assertion `self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,102) = 102 (0x66)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): libglade-CRITICAL **: glade_xml_get_widget: assertion
`self != NULL' failed
write(2,\n(gregexp:14404): libglade-CRIT...,94) = 94 (0x5e)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **: IA__gtk_text_view_get_buffer:
assertion `GTK_IS_TEXT_VIEW (text_view)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,113) = 113 (0x71)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **: IA__gtk_text_buffer_create_tag:
assertion `GTK_IS_TEXT_BUFFER (buffer)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,114) = 114 (0x72)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **: IA__gtk_tree_view_get_model: assertion
`GTK_IS_TREE_VIEW (tree_view)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,112) = 112 (0x70)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **:
IA__gtk_tree_view_insert_column_with_attributes: assertion
`GTK_IS_TREE_VIEW (tree_view)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,132) = 132 (0x84)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **: IA__gtk_tree_view_get_column:
assertion `GTK_IS_TREE_VIEW (tree_view)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,113) = 113 (0x71)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **:
IA__gtk_tree_view_column_set_clickable: assertion
`GTK_IS_TREE_VIEW_COLUMN (tree_column)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,132) = 132 (0x84)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **:
IA__gtk_tree_view_insert_column_with_attributes: assertion
`GTK_IS_TREE_VIEW (tree_view)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,132) = 132 (0x84)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **: IA__gtk_tree_view_get_column:
assertion `GTK_IS_TREE_VIEW (tree_view)' failed
write(2,\n(gregexp:14404): Gtk-CRITICAL ...,113) = 113 (0x71)
getpid() = 14404 (0x3844)
(gregexp:14404): Gtk-CRITICAL **:
Re: Dropping maintainership of science/gramps!
On 11/01/12 17:19, Anders Troback wrote: I do not use FreeBSD any more (I feel in love with OpenBSD:-)) so please remove me as maintainer of the science/gramps port. I can take it over unless someone else is better suited (and actually uses the program). How do you go about doing this, though? ___ 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
wine won't build - inotify errors
Just trying to sort out some issues with wine and I originally used pkg_add I think to install it, now I need to ensure certain features are enabled like ssl connections and I need to be able to build wine from port source. The errors are as follows: cc -o wineserver async.o atom.o change.o class.o clipboard.o completion.o console.o debugger.o device.o directory.o event.o fd.o file.o handle.o hook.o mach.o mailslot.o main.o mapping.o mutex.o named_pipe.o object.o process.o procfs.o ptrace.o queue.o region.o registry.o request.o semaphore.o serial.o signal.o snapshot.o sock.o symlink.o thread.o timer.o token.o trace.o unicode.o user.o window.o winstation.o -L../libs/wine -lwine ../libs/port/libwine_port.a -L/usr/local/lib -Wl,--rpath,\$ORIGIN/../libs/wine change.o: In function `inotify_add_dir': change.c:(.text+0x526): undefined reference to `inotify_add_watch' change.o: In function `free_inode': change.c:(.text+0x812): undefined reference to `inotify_rm_watch' change.o: In function `req_read_directory_changes': change.c:(.text+0x1310): undefined reference to `inotify_init' gmake[1]: *** [wineserver] Error 1 A quick poke at the sore point shows that there is a define around the declarations required. I think it should be using sys/inotify.h but that doesn't appear to be happening. Without a good dig I can't tell precisely what is going on, but I figured I might ask here in case someone knows either a workaround or can offer some points on what is going on. FWIW it is technically a cross-build for i386 on FreeBSD 9.0 AMD64, and I'm using /compat/i386 to provide a base using chroot similar to linux - as outlined on the freebsd wine wiki. I considered using the amd64 version, but I was running some other testing for i386 on amd64 as well. 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: FreeBSD Port: samba34-3.4.14
On 04/10/12 16:30, Chuck Swiger wrote: On Apr 9, 2012, at 5:26 PM, Da Rock wrote: [ ... ] If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve. Ah. I wasn't aware that was the case, especially if the maintainer cannot specifically commit. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Hmmm. You're right. I can narrow it down to the SWAT or AIO option (most likely given the obvious network connection there), but it could be ADS, ACL, or FAM; but I doubt that very much. You have me intrigued now, I have to look into it to know :) So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? Don't know-- I don't recall having a build of Samba fail for me any time recently, but if you can confirm that a specific option causes the build failure, that would help reproduce. So far all the options are causing _a_ failure- swat, ads, aio, acl, fam. I'm still going, but I think thats all of them. Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency... I am still looking into it as time permits, but I'm not sure I understand the difference? I had to install libnet separately in order to build. How does that fit in your comment? I'm still a very newbie developer so I'm not always accurately understanding the terms, I think. If I start getting these terms right I think I might just get better at this stuff in the makefiles :) ___ 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: samba34-3.4.14
On 04/10/12 18:06, Timur I. Bakeyev wrote: On Tue, Apr 10, 2012 at 9:57 AM, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 04/10/12 16:30, Chuck Swiger wrote: On Apr 9, 2012, at 5:26 PM, Da Rock wrote: [ ... ] If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve. Ah. I wasn't aware that was the case, especially if the maintainer cannot specifically commit. Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency... I am still looking into it as time permits, but I'm not sure I understand the difference? I had to install libnet separately in order to build. How does that fit in your comment? I'm still a very newbie developer so I'm not always accurately understanding the terms, I think. I'm not sure, which libnet you are referring to. None of the Sambas should really depend from anything called libnet. At least - externally. Thats what I'm trying to figure out now, well, as my time permits anyway :) Also, please show the content of your /etc/make.conf, it could be that you are mangling include flags. make.conf: end of make.conf ;) Well thats not entirely accurate, I only have a USE_OPENSSL_BASE and the usual perl stuff and thats all. I get a bit of a kick out of that when someone asks if there's something in the make.conf- I only use some of the kerberos options on occasion when called for (not lately), but I learnt my lesson a long time ago: don't touch the make.conf! I created some issues in the past doing that... :) ___ 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: mail/imaptools: port removal at Monday April 9th
On 04/10/12 03:49, Julian H. Stacey wrote: From: Chris Reescr...@freebsd.org Well, whatever he says, he can't revoke the license of what's already been distributed. # Copyright (c) 2008 Rick Sandersrfs9...@earthlink.net # # # # Permission to use, copy, modify, and distribute this software for any# # purpose with or without fee is hereby granted, provided that the above # # copyright notice and this permission notice appear in all copies.# ... Exactly ! From: Mark Linimonlini...@lonesome.com portmgr's policy is to honor removal requests, no matter the circumstances. Irresponsible. Real 'Managers' shoulder responsibility. So ... In /usr/ports/Mk/bsd.port.mk, define a warning variable after NO_CDROM, NO_PACKAGE, [ RESTRICTED_FILES ], with example: WARNING+=Generic author tried to retrospectively withdraw sources. #Maintainer suggest see files/... http://... Allow individual ports Maintainers to indicate status of issues. Allow individual installers to decide their Own take on issues, Not Yours ! - Ports wrappers belong to FreeBSD, not generic authors. - Sources once published can't be unpublished. (IMO No need of a new project port name to excuse retention). - Distfiles if not on freebsd.org site are not even our problem. portmgr should retain respect by dumping a foolish policy. sticking to technical avoiding programmers guesses fears about laws, or assumptions USA law controls global law or whatever else. Stay technical. The globe has 196 countries with their own legal jurisdictions, individual installers should be able to make their own decision on law risks morality as localy appropriate. To stick my nose where it probably doesn't belong: indeed. This is one area where linux annoys the most for that very reason. Let the user decide and bear the responsibility. ___ 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: mail/imaptools: port removal at Monday April 9th
On 04/10/12 08:30, Doug Barton wrote: On 04/09/2012 15:21, Da Rock wrote: To stick my nose where it probably doesn't belong: indeed. This is one area where linux annoys the most for that very reason. Let the user decide and bear the responsibility. If you want to put up a server with all the encumbered software and let people download it, go right ahead. Meanwhile, the project has chosen (wisely) not to run the risk of legal entanglements. ... not to mention the common courtesy of following the wishes of those who created the software in the first place. Part of the beauty of FreeBSD is ports, so that the user downloads from the source (or somewhere appropriate) and _not_ the project's servers. The only possible area for the 'entanglement' is the fact the framework lists where to download from. As for the wishes of the author... plain english is plain english- when you relinquish a right you can't un-relinquish it (if that is actually a word). Even the legal system has trouble (or simply cannot do it) with putting the cat back in the bag, unbolting the horse, etc, when there is a legal right to do so; to say nothing about this case. ___ 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: samba34-3.4.14
On 04/08/12 09:59, Da Rock wrote: On 04/08/12 00:02, Chris Rees wrote: On 7 April 2012 13:51, Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: On 04/06/12 13:20, Timur I. Bakeyev wrote: Hi! Can you show the build output? Port should't directly dipend from anything like this. Sorry, it was on a clients system and I couldn't get the info across. I can only say for sure that installing libnet fixed the issue. The build error was an undeclared function or const (most likely const) that was supplied by libnet. Sorry I can't tell you any more information; I emailed this to notify of the fix, and for others if they come across the issue in the future. Googling was what put me on to this fix as well. If you could give some idea of the site that advised this, that could probably help too. Again, my apologies. Let me try this again and see if I can be a little more organised with my description. This was a clean, fresh install on an amd64 (Atom cpu, although I did try on a real cpu too). I tried 3.6 first, it didn't build. Then I tried 3.5, when that didn't work (same error) I looked at the handbook and it was still on 3.4, and during my googling I noticed that there could be an issue with incompatibility with the libsmbclient; so I reverted to 3.4. It didn't build either, and they all had the same error. So I googled some more on this error, but there wasn't much on it at all. I did notice a lot of comments on samba, tdb, and libnet, and there was a clue in the error of a libnet dependency (sorry I just can't remember, so much has happened in the 24 hr period); so I tried installing libnet and then built samba 3.4 (to avoid further issues and conflicts) and presto! it all built. That was the day prior to my post, and I figured someone could run a clean build and find this as well; failing that, someone would come across this again in the future. As you can see it wasn't anything in particular that set me on this, just a hunch I followed and lucked out on a resolution, but it worked :) I hope that helps someone... To drag this up again, I was thinking about the number of cases I've found like this recently, and I was considering what the most appropriate action to take here. This one is obviously controversial, and I didn't have the time to do more or test further, but for future reference I'd like some clarification. I'd say a PR is not really appropriate as a response to an issue such as this (unless the maintainer offers no response at all), but should I create a patch to assist the maintainer? Or is that over doing it? If I were to create a patch, what is the correct (usable) procedure? And for something like this it would be an adjustment to BUILD_DEPENDS, correct? Thanks for the clarification guys. ___ 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: samba34-3.4.14
On 04/10/12 09:12, Chuck Swiger wrote: Hi-- On Apr 9, 2012, at 4:01 PM, Da Rock wrote: To drag this up again, I was thinking about the number of cases I've found like this recently, and I was considering what the most appropriate action to take here. This one is obviously controversial, and I didn't have the time to do more or test further, but for future reference I'd like some clarification. I'd say a PR is not really appropriate as a response to an issue such as this (unless the maintainer offers no response at all), but should I create a patch to assist the maintainer? Or is that over doing it? If I were to create a patch, what is the correct (usable) procedure? And for something like this it would be an adjustment to BUILD_DEPENDS, correct? If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Hmmm. You're right. I can narrow it down to the SWAT or AIO option (most likely given the obvious network connection there), but it could be ADS, ACL, or FAM; but I doubt that very much. You have me intrigued now, I have to look into it to know :) So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? ___ 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: samba34-3.4.14
On 04/10/12 13:14, Mel Flynn wrote: On 4/10/2012 02:26, Da Rock wrote: So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? I'd like to divert your attention to the libnet source directory in samba distribution. It's built by default and integrated into pretty much every binary through libnetapi. Your focus should shift to the compilation error itself, your solution of installing the port libnet masked the actual problem. I'll look into it then. I'm still trying to determine what sets it off. I'm fairly sure ADS is a major factor, though simply disabling it merely grows another failure elsewhere... :/ I'll start posting the logs soon. Is there a particular reason why a dependency on libnet is an 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
Re: FreeBSD Port: samba34-3.4.14
On 04/06/12 13:20, Timur I. Bakeyev wrote: Hi! Can you show the build output? Port should't directly dipend from anything like this. Sorry, it was on a clients system and I couldn't get the info across. I can only say for sure that installing libnet fixed the issue. The build error was an undeclared function or const (most likely const) that was supplied by libnet. Sorry I can't tell you any more information; I emailed this to notify of the fix, and for others if they come across the issue in the future. Googling was what put me on to this fix as well. Cheers Cheers. On Fri, Apr 6, 2012 at 3:40 AM, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: Building samba 3.6, 3.5, 3.4... noticed a missing dependency during build on net/libnet. Maybe need to add this to the port? 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 ___ 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: samba34-3.4.14
On 04/08/12 00:02, Chris Rees wrote: On 7 April 2012 13:51, Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: On 04/06/12 13:20, Timur I. Bakeyev wrote: Hi! Can you show the build output? Port should't directly dipend from anything like this. Sorry, it was on a clients system and I couldn't get the info across. I can only say for sure that installing libnet fixed the issue. The build error was an undeclared function or const (most likely const) that was supplied by libnet. Sorry I can't tell you any more information; I emailed this to notify of the fix, and for others if they come across the issue in the future. Googling was what put me on to this fix as well. If you could give some idea of the site that advised this, that could probably help too. Again, my apologies. Let me try this again and see if I can be a little more organised with my description. This was a clean, fresh install on an amd64 (Atom cpu, although I did try on a real cpu too). I tried 3.6 first, it didn't build. Then I tried 3.5, when that didn't work (same error) I looked at the handbook and it was still on 3.4, and during my googling I noticed that there could be an issue with incompatibility with the libsmbclient; so I reverted to 3.4. It didn't build either, and they all had the same error. So I googled some more on this error, but there wasn't much on it at all. I did notice a lot of comments on samba, tdb, and libnet, and there was a clue in the error of a libnet dependency (sorry I just can't remember, so much has happened in the 24 hr period); so I tried installing libnet and then built samba 3.4 (to avoid further issues and conflicts) and presto! it all built. That was the day prior to my post, and I figured someone could run a clean build and find this as well; failing that, someone would come across this again in the future. As you can see it wasn't anything in particular that set me on this, just a hunch I followed and lucked out on a resolution, but it worked :) I hope that helps someone... ___ 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: samba34-3.4.14
Building samba 3.6, 3.5, 3.4... noticed a missing dependency during build on net/libnet. Maybe need to add this to the port? 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
system-config-printer missing runtime dependency on libxml2
I just ran a clean install and built system-config-printer which wouldn't run. It complained about a missing 'libxml2' module. I had to run a search and I found textproc/py-libxml2 which I installed and it all runs fine now. Might need to adjust the runtime dependencies on this port. Excuse if I sound a little disconnected- too much multitasking :) 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: libreoffice-3.4.5.2 failing to build
On 04/01/12 15:55, Da Rock wrote: On 03/30/12 17:03, Da Rock wrote: On 03/30/12 16:22, Baptiste Daroussin wrote: On Thu, Mar 29, 2012 at 02:11:33PM +1000, Da Rock wrote: On 03/27/12 21:42, Da Rock wrote: I've been hunting down some info on why this is failing, but all I keep running into is the previous versions failings... :( I'm building libreoffice on 9.0-Release amd64, and I'm getting build errors qa testing(?) sd. I followed the instructions, but it still failed. It spits out this: scripting deliver deliver -- version: 275594 module 'scripting' delivered successfully. 0 files copied, 28 files unchanged terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' /usr/local/bin/bash: line 1: 2019 Abort trap: 6 (core dumped) [ a whole lot of code (I'm copying by hand, so it is a bit overwhelming) - involving clone/impress/sd/unxfbsd.pro, solver, and qa_unit ] dmake: Error code 134, while making 'test' gb_LinkTarget_add_library_objects,CppunitTest/libtest_sc_ucalc.so,sc gb_LinkTarget_add_linktarget_objects,CppunitTest/libtest_sc_ucalc.so,Library/libscfb.so [ build all ] top level modules: sc [ build all ] loaded modules: sc [ build cut ] sc_ucalc Abort trap (core dumped) terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' gmake[1]: *** [/usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/solver/340/unxfbsd.pro/workdir/CppunitTest/sc_ucalc.test] Error 1 dmake: Error code 2, while making 'all' [ build all ] top level modules: sw [ build all ] loaded modules: sw [ build all ] loaded modules: sw [ build log ] sw sw deliver deliver -- version: 275594 Module 'sw' delivered successfully. 0 files copied, 1 files unchanged - [ standard error message with webpage link to debug page ] internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sd/qa/unit ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sc/prj [ instructions to build sd part of the build to isolate the issue ] As I mentioned I followed the directions and still hit the same error filed above (if more of the data is needed I guess I'll have to find a way to post it...). I'm on a deadline for this one, so I have to get this to work. How should I further debug this to fix it? Or failing that (as an extreme last resort), will an older package already built work IF it is built for 8.2? After a portsnap update I still get core dumps in the calc/sc/cppunittester and the impress/sd/qa/unit/cppunittester. I've tried turning off make jobs, and I also checked the core files (when I finally found them). The only clue I have is this: #0 0x0008016bca7c in ?? This is in _both_ core files, and although its not very helpful it says its stopping in exactly the same place (duh). Seriously guys, where do I go from here? Googling isn't exactly offering up much - my searches can be as much as 7 results (usually my own stuff or duplicates of the same). Or, as my last resort, can I use the 8.2 package instead? Need some serious pointers, pleeease... :) is you 9.0-RELEASE a freshly built system? or installed installed from installers or upgraded? Completely clean install last week, and ports tree refreshed since on wed. I've been on the libreoffice-dev lists and the only advice is to disable the tests - but if the test is failing it must be for a reason don't you think? So why? Thanks for these couple of responses, still need help though :) I have news from the eastern front :) I've hotwired the makefile to use clang, and I have some errors cropping up close to where I was having issues using gcc: In file included from /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/soltools/giparser/gi_list.cxx:33: In file included from ../inc/gi_list.hxx:33: ../inc/st_list.hxx:298:10: error: use of undeclared identfier 'push_back' push_back( new XY(*(*it)) ); ^ this- ... more notes - usually related to this issue... ../inc/st_list.hxx:311:5: error: use of undeclared identifier 'checkSize' checkSize(DynamicListXY::len-2); ^ this- ... even more notes the last error... And then the usual fail routine. Any pointers on what is going on? What can I switch to improve the situation? The identifiers are there, but it doesn't seem to see that. Is this a C89/99 thing maybe? I love clang - it shows up all the little nuances More than likely the root of my original issue... Interesting outcome on this one. I'm not 100% sure who to send this to, but I post here for interest sake. I built this port on another 9.0 amd64 system and it built fine. The only difference between them is an Atom processor. Apparently some things can not be built on an Atom processor
Re: libreoffice-3.4.5.2 failing to build
On 03/30/12 17:03, Da Rock wrote: On 03/30/12 16:22, Baptiste Daroussin wrote: On Thu, Mar 29, 2012 at 02:11:33PM +1000, Da Rock wrote: On 03/27/12 21:42, Da Rock wrote: I've been hunting down some info on why this is failing, but all I keep running into is the previous versions failings... :( I'm building libreoffice on 9.0-Release amd64, and I'm getting build errors qa testing(?) sd. I followed the instructions, but it still failed. It spits out this: scripting deliver deliver -- version: 275594 module 'scripting' delivered successfully. 0 files copied, 28 files unchanged terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' /usr/local/bin/bash: line 1: 2019 Abort trap: 6 (core dumped) [ a whole lot of code (I'm copying by hand, so it is a bit overwhelming) - involving clone/impress/sd/unxfbsd.pro, solver, and qa_unit ] dmake: Error code 134, while making 'test' gb_LinkTarget_add_library_objects,CppunitTest/libtest_sc_ucalc.so,sc gb_LinkTarget_add_linktarget_objects,CppunitTest/libtest_sc_ucalc.so,Library/libscfb.so [ build all ] top level modules: sc [ build all ] loaded modules: sc [ build cut ] sc_ucalc Abort trap (core dumped) terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' gmake[1]: *** [/usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/solver/340/unxfbsd.pro/workdir/CppunitTest/sc_ucalc.test] Error 1 dmake: Error code 2, while making 'all' [ build all ] top level modules: sw [ build all ] loaded modules: sw [ build all ] loaded modules: sw [ build log ] sw sw deliver deliver -- version: 275594 Module 'sw' delivered successfully. 0 files copied, 1 files unchanged - [ standard error message with webpage link to debug page ] internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sd/qa/unit ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sc/prj [ instructions to build sd part of the build to isolate the issue ] As I mentioned I followed the directions and still hit the same error filed above (if more of the data is needed I guess I'll have to find a way to post it...). I'm on a deadline for this one, so I have to get this to work. How should I further debug this to fix it? Or failing that (as an extreme last resort), will an older package already built work IF it is built for 8.2? After a portsnap update I still get core dumps in the calc/sc/cppunittester and the impress/sd/qa/unit/cppunittester. I've tried turning off make jobs, and I also checked the core files (when I finally found them). The only clue I have is this: #0 0x0008016bca7c in ?? This is in _both_ core files, and although its not very helpful it says its stopping in exactly the same place (duh). Seriously guys, where do I go from here? Googling isn't exactly offering up much - my searches can be as much as 7 results (usually my own stuff or duplicates of the same). Or, as my last resort, can I use the 8.2 package instead? Need some serious pointers, pleeease... :) is you 9.0-RELEASE a freshly built system? or installed installed from installers or upgraded? Completely clean install last week, and ports tree refreshed since on wed. I've been on the libreoffice-dev lists and the only advice is to disable the tests - but if the test is failing it must be for a reason don't you think? So why? Thanks for these couple of responses, still need help though :) I have news from the eastern front :) I've hotwired the makefile to use clang, and I have some errors cropping up close to where I was having issues using gcc: In file included from /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/soltools/giparser/gi_list.cxx:33: In file included from ../inc/gi_list.hxx:33: ../inc/st_list.hxx:298:10: error: use of undeclared identfier 'push_back' push_back( new XY(*(*it)) ); ^ this- ... more notes - usually related to this issue... ../inc/st_list.hxx:311:5: error: use of undeclared identifier 'checkSize' checkSize(DynamicListXY::len-2); ^ this- ... even more notes the last error... And then the usual fail routine. Any pointers on what is going on? What can I switch to improve the situation? The identifiers are there, but it doesn't seem to see that. Is this a C89/99 thing maybe? I love clang - it shows up all the little nuances More than likely the root of my original 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
libreoffice ignores defined CC variables and friends
In an attempt to build libreoffice I'm trying to build libreoffice-3.4.5.2 with clang, but it is ignoring every attempt I have made to set env variables, configure args. I have used -DCC=clang -DCXX=clang++ -DCPP=clang-cpp, I edited the Makefile to check these and set them in CONFIGURE_ARGS or CONFIGURE_ENV. It is not listening and is determined to use gcc :/ Am I missing something fundamental in my understanding of how things work here? 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: libreoffice-3.4.5.2 failing to build
On 03/30/12 16:22, Baptiste Daroussin wrote: On Thu, Mar 29, 2012 at 02:11:33PM +1000, Da Rock wrote: On 03/27/12 21:42, Da Rock wrote: I've been hunting down some info on why this is failing, but all I keep running into is the previous versions failings... :( I'm building libreoffice on 9.0-Release amd64, and I'm getting build errors qa testing(?) sd. I followed the instructions, but it still failed. It spits out this: scripting deliver deliver -- version: 275594 module 'scripting' delivered successfully. 0 files copied, 28 files unchanged terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' /usr/local/bin/bash: line 1: 2019 Abort trap: 6 (core dumped) [ a whole lot of code (I'm copying by hand, so it is a bit overwhelming) - involving clone/impress/sd/unxfbsd.pro, solver, and qa_unit ] dmake: Error code 134, while making 'test' gb_LinkTarget_add_library_objects,CppunitTest/libtest_sc_ucalc.so,sc gb_LinkTarget_add_linktarget_objects,CppunitTest/libtest_sc_ucalc.so,Library/libscfb.so [ build all ] top level modules: sc [ build all ] loaded modules: sc [ build cut ] sc_ucalc Abort trap (core dumped) terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' gmake[1]: *** [/usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/solver/340/unxfbsd.pro/workdir/CppunitTest/sc_ucalc.test] Error 1 dmake: Error code 2, while making 'all' [ build all ] top level modules: sw [ build all ] loaded modules: sw [ build all ] loaded modules: sw [ build log ] sw sw deliver deliver -- version: 275594 Module 'sw' delivered successfully. 0 files copied, 1 files unchanged - [ standard error message with webpage link to debug page ] internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sd/qa/unit ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sc/prj [ instructions to build sd part of the build to isolate the issue ] As I mentioned I followed the directions and still hit the same error filed above (if more of the data is needed I guess I'll have to find a way to post it...). I'm on a deadline for this one, so I have to get this to work. How should I further debug this to fix it? Or failing that (as an extreme last resort), will an older package already built work IF it is built for 8.2? After a portsnap update I still get core dumps in the calc/sc/cppunittester and the impress/sd/qa/unit/cppunittester. I've tried turning off make jobs, and I also checked the core files (when I finally found them). The only clue I have is this: #0 0x0008016bca7c in ?? This is in _both_ core files, and although its not very helpful it says its stopping in exactly the same place (duh). Seriously guys, where do I go from here? Googling isn't exactly offering up much - my searches can be as much as 7 results (usually my own stuff or duplicates of the same). Or, as my last resort, can I use the 8.2 package instead? Need some serious pointers, pleeease... :) is you 9.0-RELEASE a freshly built system? or installed installed from installers or upgraded? Completely clean install last week, and ports tree refreshed since on wed. I've been on the libreoffice-dev lists and the only advice is to disable the tests - but if the test is failing it must be for a reason don't you think? So why? Thanks for these couple of responses, still need help though :) ___ 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/fireflies build fail - typo
Not trying to piss everyone off here with all these build failures I'm throwing in :) Can I get a confirmation on this one though? I was installing xscreensaver and this came port up as a failed build due to missing file. Due to a break in convention I had to edit /usr/ports/x11/fireflies/work/firelies-2.07/libgfx/src/gui.cxx: -#include FL/fl_file_chooser.H +#include FL/Fl_File_Chooser.H Build was successful once this change was made. If someone else can confirm I'll notify the maintainer. 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: libreoffice-3.4.5.2 failing to build
On 03/27/12 21:42, Da Rock wrote: I've been hunting down some info on why this is failing, but all I keep running into is the previous versions failings... :( I'm building libreoffice on 9.0-Release amd64, and I'm getting build errors qa testing(?) sd. I followed the instructions, but it still failed. It spits out this: scripting deliver deliver -- version: 275594 module 'scripting' delivered successfully. 0 files copied, 28 files unchanged terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' /usr/local/bin/bash: line 1: 2019 Abort trap: 6 (core dumped) [ a whole lot of code (I'm copying by hand, so it is a bit overwhelming) - involving clone/impress/sd/unxfbsd.pro, solver, and qa_unit ] dmake: Error code 134, while making 'test' gb_LinkTarget_add_library_objects,CppunitTest/libtest_sc_ucalc.so,sc gb_LinkTarget_add_linktarget_objects,CppunitTest/libtest_sc_ucalc.so,Library/libscfb.so [ build all ] top level modules: sc [ build all ] loaded modules: sc [ build cut ] sc_ucalc Abort trap (core dumped) terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' gmake[1]: *** [/usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/solver/340/unxfbsd.pro/workdir/CppunitTest/sc_ucalc.test] Error 1 dmake: Error code 2, while making 'all' [ build all ] top level modules: sw [ build all ] loaded modules: sw [ build all ] loaded modules: sw [ build log ] sw sw deliver deliver -- version: 275594 Module 'sw' delivered successfully. 0 files copied, 1 files unchanged - [ standard error message with webpage link to debug page ] internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sd/qa/unit ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sc/prj [ instructions to build sd part of the build to isolate the issue ] As I mentioned I followed the directions and still hit the same error filed above (if more of the data is needed I guess I'll have to find a way to post it...). I'm on a deadline for this one, so I have to get this to work. How should I further debug this to fix it? Or failing that (as an extreme last resort), will an older package already built work IF it is built for 8.2? After a portsnap update I still get core dumps in the calc/sc/cppunittester and the impress/sd/qa/unit/cppunittester. I've tried turning off make jobs, and I also checked the core files (when I finally found them). The only clue I have is this: #0 0x0008016bca7c in ?? This is in _both_ core files, and although its not very helpful it says its stopping in exactly the same place (duh). Seriously guys, where do I go from here? Googling isn't exactly offering up much - my searches can be as much as 7 results (usually my own stuff or duplicates of the same). Or, as my last resort, can I use the 8.2 package instead? Need some serious pointers, pleeease... :) ___ 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
libreoffice-3.4.5.2 failing to build
I've been hunting down some info on why this is failing, but all I keep running into is the previous versions failings... :( I'm building libreoffice on 9.0-Release amd64, and I'm getting build errors qa testing(?) sd. I followed the instructions, but it still failed. It spits out this: scripting deliver deliver -- version: 275594 module 'scripting' delivered successfully. 0 files copied, 28 files unchanged terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' /usr/local/bin/bash: line 1: 2019 Abort trap: 6 (core dumped) [ a whole lot of code (I'm copying by hand, so it is a bit overwhelming) - involving clone/impress/sd/unxfbsd.pro, solver, and qa_unit ] dmake: Error code 134, while making 'test' gb_LinkTarget_add_library_objects,CppunitTest/libtest_sc_ucalc.so,sc gb_LinkTarget_add_linktarget_objects,CppunitTest/libtest_sc_ucalc.so,Library/libscfb.so [ build all ] top level modules: sc [ build all ] loaded modules: sc [ build cut ] sc_ucalc Abort trap (core dumped) terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' gmake[1]: *** [/usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/solver/340/unxfbsd.pro/workdir/CppunitTest/sc_ucalc.test] Error 1 dmake: Error code 2, while making 'all' [ build all ] top level modules: sw [ build all ] loaded modules: sw [ build all ] loaded modules: sw [ build log ] sw sw deliver deliver -- version: 275594 Module 'sw' delivered successfully. 0 files copied, 1 files unchanged - [ standard error message with webpage link to debug page ] internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sd/qa/unit ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.5.2/sc/prj [ instructions to build sd part of the build to isolate the issue ] As I mentioned I followed the directions and still hit the same error filed above (if more of the data is needed I guess I'll have to find a way to post it...). I'm on a deadline for this one, so I have to get this to work. How should I further debug this to fix it? Or failing that (as an extreme last resort), will an older package already built work IF it is built for 8.2? TIA guys ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What about Firefox 11?
On 03/25/12 16:06, Heino Tiedemann wrote: Florian Smeetsf...@freebsd.org wrote: For those who cannot wait we are always looking for testes ;) svn co https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox/ LOL. Do you mean those with the balls enough to try it out? Or is that a typo? :) ___ 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: print/cups: CUPS-1.5.0 IPP protocoll issues - no printing possible on IPP capable network printers
On 02/07/12 18:40, O. Hartmann wrote: We use a bunch of HP and Xerox printers across our network, all capable of being accessed via network over IPP protocoall (so they claim). Printing worked for me flawless on FreeBSD 8.2-STABLE, 9.0-CURRENT, now 9.0-STABLE on all boxes in question. Since updating cups to revision 1.5.0 (this is the most recent port version and I recently updated/recompiled the port and dependencies for all parts of CUPS either with CLANG and GCC 4.2.1), I get massive problems accessing printers on the network. Most HP printers accept a print job, but after accepting, CUPS reports printer has been stopped, can not obtain printer status. The job remains in the queue. Then I restart printer via CUPS, print job gets printed, but immediateley after printing has finished, the same problem occurs again: printer stopped - can not get printer status. Job remains still in the queue. Restarting printer via CUPS will start the game again, with the result of printing endless the same job, first in queue. I have to check whether the printer indeed has printed the job, delete the first queue entry, restart the printer again to get next job started ... and so on. A similar game on the Xerox printer facility. The printer reports Unablae to get printer status, printing is here impossible! The XEROX printer is now attached to a Linux print server box running CUPS, an older CUPS on something like CentOS, I do not know what crap is running on the hardware. But: the printer works fine with older CUPS! Digging the internet revealed an issue reported in an Ubuntu forum/list, I already filed a PR (ports/164759). The Ubuntu report is about to be found here: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/877958 I was wondering if this patch, whatever the Ubuntu fellows patched, couldn't be introduced to FreeBSD's CUPS port. Well, sorry about my impatience, but I'm floating like a dead man in the water, since I have to prepare printouts for a conference and printing is some kind of neurological point around here. Whoopsy doodle! I wasn't aware you had included ports _and_ questions... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Any common policy against conflicting choice in Makefile OPTIONS?
On 02/06/12 03:41, Chris Rees wrote:
On 5 February 2012 17:37, Olli Haueroha...@freebsd.org wrote:
On 2012-02-05 18:23, Chris Rees wrote:
On 5 February 2012 17:21, Olli Haueroha...@freebsd.org wrote:
On 2012-02-05 17:19, RyōTa SimaMoto wrote:
Hi, I'm a port maintainer for multimedia/qmmp, and some ports.
Before upgrading QMMP port, may I ask what is the common policy how to
offer Makefile OPTIONS containing a certain contradictory pair?
Actually the latest version of QMMP supports several versions of ffmpeg,
including 0.7.11, 0.9, 0.9.1, and 2012.01.22 that I tested to verify, so it
allows user to choose one of multimedia/ffmpeg or multimedia/ffmpeg-devel.
As you know you should not select both of them, otherwise they may conflict
with each other. I plan to provide an entry for each of them.
|
| [*] FFMPEGSupport to playback by FFMPEG
| [ ] FFMPEG_DEVEL Support to playback by FFMPEG-devel
|
Then how should the Makefile proceed after the user's choice?
When the user did not install any of them yet, it's easy: The installation
would obey the user's order except when occationally both of them are
enabled that results to fail with an alert message. On the other hand, if
one of them are already installed, Makefile would know which one is
installed using 'exists(${LOCALBASE}/include/libavcodec/vda.h)' command.
So, in fact, there is no question that which version the user want to use.
The smartest way would be that provides a single entry which corresponds
to the existing version and hides the other entry that should not be
choosen. Unfortunately, the value LOCALBASE is not defined until
bsd.port.options.mk macro is loaded, that means we don't have any proper
steps to determine what version is already installed when the Makefile
construct the OPTIONS set. So we have no other way than to let the option
dialog always show both entries including quite wrong option.
Then if the user selects the other one that might conflict with the
installed version, there are six possible courses I assume.
0x000. Quit the session with alert message instructing user to retry
'make config' to choose the already installed one that Makefile
knows.
0x001. Dare to go through and expect that the depending port deals with
the conflicting issue.
0x002. Use the installed version and omit the choice implicitly.
0x004. Warn with short pause, then use the installed version and omit
the choice.
0x010. Store options into /var/db/ports/* as are that the user selects.
0x020. Store options into /var/db/ports/* with correction as actually
working. (If option variables are allowed to be changed at
testing stage.)
Is there any recommended policy? If so, what way or a set of ways should I
choose?
The following patch will do what you want, just polish the IGNORE messages.
Hopefully the include files do not change with the next versions.
--- Makefile.orig 2012-02-05 17:53:58.0 +0100
+++ Makefile2012-02-05 18:16:00.0 +0100
@@ -35,6 +35,7 @@
FLACSupport to playback FLAC files on \
MUSEPACKSupport to playback MPC files on \
FFMPEG Support to playback FFMPEG files on \
+ FFMPEG_DEVELSupport to playback FFMPEG-devel files on \
Hm, breaks itself by default ;)
where?
(Maybe I had not enough sleep tomight)
Here (both are on by default):
+.if defined(WITH_FFMPEG) defined (WITH_FFMPEG_DEVEL)
+IGNORE=coose only one FFMPEG option
+.endif
I still think depending on ffmpeg binary and defaulting to
multimedia/ffmpeg and just having the one OPTION is the simplest
solution.
Sure, but the OP maybe wants to give the ability to choose which ffmpeg version
in case the ffmpeg port is not already installed.
I'm just pointing out that it's not easy, and probably not a good idea :)
If the user cares that much about which ffmpeg version is installed
s/he would have installed it already.
True +1.
Usually it is this that breaks most similar ports (xine, mplayer, etc).
Can't install devel without breaking, and to fix you have to install the
non devel version.
JIC: this is not an official complaint, or a stolen thread. Just an
observation for the OP to consider when setting their own port.
___
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: Good source for linux libs
On 02/03/12 06:27, Conrad J. Sabatier wrote: On Thu, 02 Feb 2012 17:03:50 +0100 Dominic Fandreykamik...@bsdforen.de wrote: I need some linux libraries to throw in with a port of Eagle6. http://www.freebsd.org/cgi/query-pr.cgi?pr=164581 I'm Linux illiterate, does anyone know a good source for all of these: - libpng14.so.14 - libssl.so.1.0.0 - libcrypto.so.1.0.0 - libjpeg.so.8 With good source I mean something that qualifies as a respectable MASTER_SITE like some Linux distro that packs the right versions of the libraries. I'm afraid I might also need a different glibc version, but I'll burn that bridge when I cross it. Check /usr/ports/Mk/bsd.sites.mk for the definitions of all of the Linux repositories used by the ports collection. Better yet, run a google search for those libs - you also need to use linux f10 (fedora 10) as the distro, as that is what comes installed for the linuxulator. Running through those sites looking for libs will be very time consuming and download hungry, and therefore not very productive. You'll need to know what rpm they're located in first. For a first hint though, I'd say the ssl is in an openssl rpm, and crypto as well too probably. HTH ___ 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: Port libSwiften Request
On 01/25/12 19:44, Jaret Bartsch wrote: Hi there. I have recently tried to compile a software, but a port called libSwiften (on linux) is not available for FreeBSD as Swiften or libSwiften. Is it possible the ports team could perhaps include this software in the ports collection? Would you be willing to have a crack at porting it yourself? I'm a newb myself at this, but it is possible- even if you don't fully understand makefiles :) Otherwise I'd be willing to help, but there are plenty here better qualified to answer any queries about how to do it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
port license framework
I'm just trying to get my head around the license framework. Is it supposed to be a means for a sysadmin to control what licensed software is installed? Or is it more than that? If it is more than that, why would one need to install a license from the framework if the software usually has it in the docs as copying or something else? Or am I way off? 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: What is the best way to _not_ install licenses?
On 01/22/12 23:44, Chris Rees wrote: On 22 January 2012 13:13, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I'm back to resolve some issues with my new port ports/164113. I have to not install license as per instructions in the porters handbook (which I wasn't aware it was doing). What is the best way to achieve this? Huh? Why don't you want to install the licence? According to the handbook there is enough copies to go around and the system doesn't need to be overloaded with license copies (GPL only). Meh... I'll comply. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-misc.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
Re: What is the best way to _not_ install licenses?
On 01/23/12 00:54, Chris Rees wrote: On 22 January 2012 13:55, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/22/12 23:44, Chris Rees wrote: On 22 January 2012 13:13, Da Rock freebsd-po...@herveybayaustralia.com.auwrote: I'm back to resolve some issues with my new port ports/164113. I have to not install license as per instructions in the porters handbook (which I wasn't aware it was doing). What is the best way to achieve this? Huh? Why don't you want to install the licence? According to the handbook there is enough copies to go around and the system doesn't need to be overloaded with license copies (GPL only). Meh... I'll comply. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-misc.html Ah, that refers to people sticking the GPL in to pkg-descr. That probably could be clearer... but if it complains about the GPL file not being removed from the system on deinstall, what then? It specifically mentions plist as well. So what is it supposed to do? Is there another linux port that shows how it should be handled correctly that I could check out? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: What is the best way to _not_ install licenses?
On 01/23/12 01:13, Alexander Leidinger wrote: On Sun, 22 Jan 2012 13:44:25 + Chris Reescr...@freebsd.org wrote: On 22 January 2012 13:13, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I'm back to resolve some issues with my new port ports/164113. I have to not install license as per instructions in the porters handbook (which I wasn't aware it was doing). What is the best way to achieve this? Huh? Why don't you want to install the licence? Seems there's a little bit of confusion around. The port itself is fine, the version in ports does not install any license. The redports log he looked at was based upon what he submitted, but it is not what I committed. So for the port there's nothing to do ATM. The problem with the licenses framework and the linuxulator ports is, that the licenses framework assumes, that PREFIX/share does not need to be removed (it needs to be removed in the linuxulator case). My workaround was to specify NO_LICENSES_INSTALL=yes. Another problem is probably, that the licenses framework writes the license to WRKDIR/license_name and the linuxulator ports install everything from WRKDIR except WRKDIR/.*. This way we get PREFIX/license_name, again without a PLIST entry like the PREFIX/share directory. My workaround was to do a RM PREFIX/license_name in post-install. I tried that, but it came up error again. I haven't yet tried with the rm in post-extract, but I thought I'd check in first to see if I was on the right track. The other issues I mentioned are a bit of a worry as well. Sorry, I'm a bit pedantic :) Also, what exactly is QATty in reports? It goes with a bang... ___ 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: acroread8/9 cups support (Re: acroead8 and libcups dependencies)
On 01/23/12 16:28, Hiroki Sato wrote: Da Rockfreebsd-po...@herveybayaustralia.com.au wrote in4f139c43.1050...@herveybayaustralia.com.au: fr I'm trying to contact the maintainer of the acroread ports to see if fr they can put in a dependency on linux-f10-cups-libs for the ease of fr use by general users, and to enable acceptance by the graphics fr industry niche. Cejka Rudolfcej...@fit.vutbr.cz wrote in2002110904.ga...@fit.vutbr.cz: cedo you have plans to add support for cups printing from acroread9-9.4.2? I added CUPS support into both acroread8 and acroread9. It seems working as far as I can check all versions in the ports tree, but please test them. Thank you. -- Hiroki Will do. Cheers Hiroki ___ 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
Acroread: contacting maintainer
What is the correct way to contact the maintainer for a port? Does one contact directly? Or through a list (this one?)? Or pr? I'm trying to contact the maintainer of the acroread ports to see if they can put in a dependency on linux-f10-cups-libs for the ease of use by general users, and to enable acceptance by the graphics industry niche. I tried a direct email, but I've received no response as yet after several days; and I'm not 100% sure I did the right thing. 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: [SUBMITTED] linux-f10-nss_ldap: my first port - be gentle :)
On 01/14/12 05:53, Boris Samorodov wrote: 13.01.2012 18:51, Da Rock пишет: Once submitted do the committers offer any advice on improvements? Yep, it happens from sometime. Ok. I've submitted; but I have a problem viewing it on the pr web page. According to my mail system it has gone through hours ago. Is the system manual or automatic? One other thing: this process of porting (Makefiles and such) are these standard commands, functions, formatting for make? Or is it solely FreeBSD specific? Aside from policies and such of course... This is the first time I've used Makefiles to any such depth you see, so I'm curious to know where make stuff ends and the Freebsd tweaks begin. I know I have to read the mk files more thoroughly, but not even all the quirks in there would be completely FreeBSD in origin. So I suppose I'm asking how to tell the difference between the two. 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
OT: Tinderbox and kernel building
I know this is not ports related, but the tool is :) So thought this would be the best place for an answer. Anyway, one can use Tinderbox to build port packages for users; but can it be used to build kernel binaries too? Or maybe I'm just off my rocker... 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/12/12 17:54, Matthew Seaman wrote: On 12/01/2012 06:44, Da Rock wrote: I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also have the files hosted and the MASTER_FILES set to include the linux sites (just where the files are located). I am looking for a backup site to all that IF I can twist someones arm? I have triple tested it all in all iterations and its as smooth as now- no issues whatsoever. So what happens now? How does it get into the ports tree now? Can someone have a look see and test it before I submit this thing? Run 'portlint -C' and fix anything it flags up -- well, within reason. Sometimes portlint complains about things it shouldn't. Then submit your port. For a new port, you need to create a .shar of the port directory, which you can attach to the PR like so: send-pr -a newport.shar When filling in the PR in the editor it pops you into, you need to set the appropriate field in the PR to 'change-request'. No need to fill in all the sections -- for ports PRs it's mostly 'Description' that gets filled in. Everything else is pretty obvious I think. The comitter who works on the port will run it through tinderbox testing and get back to you if there are any problems. I would have preferred to know about the -C option earlier- I hadn't realised how helpful it was. I used -Cv in the end which gave me a better overview. I do have a WARN: no CVS directories. Use -N to check a new port. Is this normal? Is this simply expected of a new uncommitted port? I assume this is the case due to -N mentioned in the warning, I also ran it with -CvN and it came back with looks fine. I'll upload a new .shar to my URI now. THX :) ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/13/12 04:19, Chris Rees wrote: On 12 January 2012 12:26, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 01/12/12 17:54, Matthew Seaman wrote: On 12/01/2012 06:44, Da Rock wrote: I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also have the files hosted and the MASTER_FILES set to include the linux sites (just where the files are located). I am looking for a backup site to all that IF I can twist someones arm? I have triple tested it all in all iterations and its as smooth as now- no issues whatsoever. So what happens now? How does it get into the ports tree now? Can someone have a look see and test it before I submit this thing? Run 'portlint -C' and fix anything it flags up -- well, within reason. Sometimes portlint complains about things it shouldn't. Then submit your port. For a new port, you need to create a .shar of the port directory, which you can attach to the PR like so: send-pr -a newport.shar When filling in the PR in the editor it pops you into, you need to set the appropriate field in the PR to 'change-request'. No need to fill in all the sections -- for ports PRs it's mostly 'Description' that gets filled in. Everything else is pretty obvious I think. The comitter who works on the port will run it through tinderbox testing and get back to you if there are any problems. I would have preferred to know about the -C option earlier- I hadn't realised how helpful it was. I used -Cv in the end which gave me a better overview. I do have a WARN: no CVS directories. Use -N to check a new port. Is this normal? Is this simply expected of a new uncommitted port? I assume this is the case due to -N mentioned in the warning, I also ran it with -CvN and it came back with looks fine. I'll upload a new .shar to my URI now. Hm, for a new port, you should use portlint -A; portlint -C is for existing ports. portlint -A searches for stupid things like a work/ directory still existing too. portlint -A: looks fine. I'll put it in later today, I think. ___ 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: unassociated shell command
On 01/13/12 07:30, Chris Rees wrote:
On 12 January 2012 06:27, Jason Helfmanjhelf...@e-e.com wrote:
On Wed, Jan 11, 2012 at 10:25:26PM -0600, Stephen Montgomery-Smith thus
spake:
On 01/11/2012 10:14 PM, Da Rock wrote:
I'm still very new to this, but I'm almost complete on my first
port. I
do have an unusual error which crops up from time to time and I'm
usually able to fudge along and clear it- but this last little bit
won't
clear!
The particular lines in question are as follows:
post-extract:
[snip]
.if defined(NOPORTDOCS)
@if [ -d ${WRKDIR}/usr/share/doc ]; then \
${RM} -rf ${WRKDIR}/usr/share/doc; \
fi
PLIST_SUB+=@comment
.else
PLIST_SUB+= PORTDOCS=
.endif
and I get the following error make -DNOPORTDOCS install:
Makefile, line 59: Unassociated shell command @if [ -d
${WRKDIR}/usr/share/doc ]; then ${RM} -rf ${WRKDIR}/usr/share/doc;
fi
make: fatal errors encountered -- cannot continue
What am I possibly missing? No googling helps, and I've tried many
different tricks that have worked in the past as ${DIRRM}, ${RM},
individual directory/file removal, etc.
The indentation is exactly as in the Makefile.
Is the indentation whitespace, or using tabs? It should be tabs, in my
experience.
Quite right, it should be tabs!
Also, no, you shouldn't (can't) set Make variables inside a target, as
covered before.
However... instead of
.if defined(NOPORTDOCS)
PLIST_SUB etc etc
stuff, just remove all the PORTDOCS lines from pkg-plist, and use the
magic variable PORTDOCS:
PORTDOCS= *
:)
I must be a little slow this morning... I don't get it. How does that work?
I would like to point out also that the docs are 30/70 nss and pam
related respectively. So if I install without pam then the pam docs are
not installed.
___
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
unassociated shell command
I'm still very new to this, but I'm almost complete on my first port. I
do have an unusual error which crops up from time to time and I'm
usually able to fudge along and clear it- but this last little bit won't
clear!
The particular lines in question are as follows:
post-extract:
[snip]
.if defined(NOPORTDOCS)
@if [ -d ${WRKDIR}/usr/share/doc ]; then \
${RM} -rf ${WRKDIR}/usr/share/doc; \
fi
PLIST_SUB+=@comment
.else
PLIST_SUB+= PORTDOCS=
.endif
and I get the following error make -DNOPORTDOCS install:
Makefile, line 59: Unassociated shell command @if [ -d
${WRKDIR}/usr/share/doc ]; then ${RM} -rf ${WRKDIR}/usr/share/doc; fi
make: fatal errors encountered -- cannot continue
What am I possibly missing? No googling helps, and I've tried many
different tricks that have worked in the past as ${DIRRM}, ${RM},
individual directory/file removal, etc.
The indentation is exactly as in the Makefile.
___
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: unassociated shell command
On 01/12/12 13:01, Stephen Montgomery-Smith wrote:
I usually see this error when there is a command that doesn't belong
to a target. For example, if I create a Makefile that contains only:
echo xxx
I get the same error. So I think it is something in the part you
snipped out that makes this error happen.
Yes, I have run that scenario too and learnt from it.
The snipped bit is basically the same- but it works :/
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist; \
fi
.if defined(WITH_PAM)
PLIST_SUB+= PAM=
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} -rf ${WRKDIR}/lib/; \
fi
@if [ -f ${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap
]; then \
${RM} ${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam*; \
${RM} -rf ${WRKDIR}/usr/share/doc/nss_ldap-264/pam.d; \
fi
@if [ -f ${WRKDIR}/usr/share/man/man5/pam_ldap.5.gz ]; then \
${RM} ${WRKDIR}/usr/share/man/man5/pam_ldap.5.gz; \
fi
PLIST_SUB+= PAM=@comment
.endif
Again, the indent is as is.
Removing the @ didn't work either...
On 01/11/2012 07:37 PM, Da Rock wrote:
I'm still very new to this, but I'm almost complete on my first port. I
do have an unusual error which crops up from time to time and I'm
usually able to fudge along and clear it- but this last little bit won't
clear!
The particular lines in question are as follows:
post-extract:
[snip]
.if defined(NOPORTDOCS)
@if [ -d ${WRKDIR}/usr/share/doc ]; then \
${RM} -rf ${WRKDIR}/usr/share/doc; \
fi
PLIST_SUB+=@comment
.else
PLIST_SUB+= PORTDOCS=
.endif
and I get the following error make -DNOPORTDOCS install:
Makefile, line 59: Unassociated shell command @if [ -d
${WRKDIR}/usr/share/doc ]; then ${RM} -rf ${WRKDIR}/usr/share/doc; fi
make: fatal errors encountered -- cannot continue
What am I possibly missing? No googling helps, and I've tried many
different tricks that have worked in the past as ${DIRRM}, ${RM},
individual directory/file removal, etc.
The indentation is exactly as in the Makefile.
___
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-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: unassociated shell command
On 01/12/12 13:59, Stephen Montgomery-Smith wrote:
On 01/11/2012 09:48 PM, Da Rock wrote:
On 01/12/12 13:01, Stephen Montgomery-Smith wrote:
I usually see this error when there is a command that doesn't belong
to a target. For example, if I create a Makefile that contains only:
echo xxx
I get the same error. So I think it is something in the part you
snipped out that makes this error happen.
Yes, I have run that scenario too and learnt from it.
The snipped bit is basically the same- but it works :/
I tried this Makefile, and got the same error.
all:
XXX=xxx
echo xxx
Putting in the assignment seems to split the command echo xxx from
the target all:.
So it looks like you need to separate the assignments from the commands.
How do I do that, though? I have tried the assignment following the
commands (as it is now), but obviously thats not working either.
And why does it work in the other settings?
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} ${WRKDIR}/etc/ldap.conf ${WRKDIR}/etc/ldap.conf.dist; \
fi
.if defined(WITH_PAM)
PLIST_SUB+= PAM=
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} -rf ${WRKDIR}/lib/; \
fi
@if [ -f ${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
${RM} ${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam*; \
${RM} -rf ${WRKDIR}/usr/share/doc/nss_ldap-264/pam.d; \
fi
@if [ -f ${WRKDIR}/usr/share/man/man5/pam_ldap.5.gz ]; then \
${RM} ${WRKDIR}/usr/share/man/man5/pam_ldap.5.gz; \
fi
PLIST_SUB+= PAM=@comment
.endif
Again, the indent is as is.
Removing the @ didn't work either...
On 01/11/2012 07:37 PM, Da Rock wrote:
I'm still very new to this, but I'm almost complete on my first
port. I
do have an unusual error which crops up from time to time and I'm
usually able to fudge along and clear it- but this last little bit
won't
clear!
The particular lines in question are as follows:
post-extract:
[snip]
.if defined(NOPORTDOCS)
@if [ -d ${WRKDIR}/usr/share/doc ]; then \
${RM} -rf ${WRKDIR}/usr/share/doc; \
fi
PLIST_SUB+=@comment
.else
PLIST_SUB+= PORTDOCS=
.endif
and I get the following error make -DNOPORTDOCS install:
Makefile, line 59: Unassociated shell command @if [ -d
${WRKDIR}/usr/share/doc ]; then ${RM} -rf ${WRKDIR}/usr/share/doc; fi
make: fatal errors encountered -- cannot continue
What am I possibly missing? No googling helps, and I've tried many
different tricks that have worked in the past as ${DIRRM}, ${RM},
individual directory/file removal, etc.
The indentation is exactly as in the Makefile.
___
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: unassociated shell command
On 01/12/12 14:25, Stephen Montgomery-Smith wrote:
On 01/11/2012 10:14 PM, Da Rock wrote:
On 01/12/12 13:59, Stephen Montgomery-Smith wrote:
On 01/11/2012 09:48 PM, Da Rock wrote:
On 01/12/12 13:01, Stephen Montgomery-Smith wrote:
I usually see this error when there is a command that doesn't belong
to a target. For example, if I create a Makefile that contains only:
echo xxx
I get the same error. So I think it is something in the part you
snipped out that makes this error happen.
Yes, I have run that scenario too and learnt from it.
The snipped bit is basically the same- but it works :/
I tried this Makefile, and got the same error.
all:
XXX= xxx
echo xxx
Putting in the assignment seems to split the command echo xxx from
the target all:.
So it looks like you need to separate the assignments from the
commands.
How do I do that, though? I have tried the assignment following the
commands (as it is now), but obviously thats not working either.
And why does it work in the other settings?
Maybe WITH_PAM is not defined.
But try something like this:
.if (conditionA)
XXX=
.endif
.if (conditionB)
ZZZ=
.endif
post-extract:
.if (conditionA)
@echo Doing A with ${XXX}
.endif
.if (conditionB)
@echo Doing B with ${ZZZ}
.endif
You're a genius! Whether you realise it or not or it was accidental...
I split the 2 defines and set PLIST_SUB in the main, and ran the shell
commands in post-extract. What I was attempting was for elegance I
thought by keeping it all together. She runs as smooth as silk now :D
Thanks man...
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} ${WRKDIR}/etc/ldap.conf ${WRKDIR}/etc/ldap.conf.dist; \
fi
.if defined(WITH_PAM)
PLIST_SUB+= PAM=
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} -rf ${WRKDIR}/lib/; \
fi
@if [ -f ${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ];
then \
${RM} ${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam*; \
${RM} -rf ${WRKDIR}/usr/share/doc/nss_ldap-264/pam.d; \
fi
@if [ -f ${WRKDIR}/usr/share/man/man5/pam_ldap.5.gz ]; then \
${RM} ${WRKDIR}/usr/share/man/man5/pam_ldap.5.gz; \
fi
PLIST_SUB+= PAM=@comment
.endif
Again, the indent is as is.
Removing the @ didn't work either...
On 01/11/2012 07:37 PM, Da Rock wrote:
I'm still very new to this, but I'm almost complete on my first
port. I
do have an unusual error which crops up from time to time and I'm
usually able to fudge along and clear it- but this last little bit
won't
clear!
The particular lines in question are as follows:
post-extract:
[snip]
.if defined(NOPORTDOCS)
@if [ -d ${WRKDIR}/usr/share/doc ]; then \
${RM} -rf ${WRKDIR}/usr/share/doc; \
fi
PLIST_SUB+=@comment
.else
PLIST_SUB+= PORTDOCS=
.endif
and I get the following error make -DNOPORTDOCS install:
Makefile, line 59: Unassociated shell command @if [ -d
${WRKDIR}/usr/share/doc ]; then ${RM} -rf
${WRKDIR}/usr/share/doc; fi
make: fatal errors encountered -- cannot continue
What am I possibly missing? No googling helps, and I've tried many
different tricks that have worked in the past as ${DIRRM}, ${RM},
individual directory/file removal, etc.
The indentation is exactly as in the Makefile.
___
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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/12/12 02:23, Matthew Seaman wrote:
On 11/01/2012 16:10, Eitan Adler wrote:
post-extract:
.if defined(WITH_PAM)
PLIST_FILES+=lib/security/pam_ldap.so
.else
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so
${DIRRM} ${WRKDIR}/lib/;
fi
^
This is what's wrong. In port Makefiles, it's .if, .else, .endif not fi.
You need both: .endif and fi in this case (the 'fi' is part of the shell script)
Also the shell script part needs to be backslashed, and statements
separated by semi-colons, like so:
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
${RM} ${WRKDIR}/lib/security/pam_ldap.so ; \
${DIRRM} ${WRKDIR}/lib/ ; \
fi
Looking back at the OP's previous posts, it's this backslashing thing
which is missing: the (make) .if is properly closed with a .endif, which
unfortunately got cropped in one of the replies upthread.
Another point: its not usual to modify variables like PLIST_FILES or
PORTDOCS as part of the post-extract target. Usually that's done
earlier in the Makefile before any of the actual make targets.
You were right Matthew.
It's all done now guys- what now?
I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also
have the files hosted and the MASTER_FILES set to include the linux
sites (just where the files are located). I am looking for a backup site
to all that IF I can twist someones arm?
I have triple tested it all in all iterations and its as smooth as now-
no issues whatsoever. So what happens now? How does it get into the
ports tree now? Can someone have a look see and test it before I submit
this thing?
As for the bsd.sites question: before I posted this I navigated to the
sites in question, and they had messages to redirect to this URI that I
have posted.
As for my own files, I can use release, updates, or testing. ATM its set
to the testing files. Should I back that off a bit?
I set the portversion to the nss_ldap_version (264). What about the 6 do
you think? It could be trickier...
The Makefile has lost weight - I trimmed it aggressively, but if I can
cut it back further I'd be happy to know.
I've posted the shar to
http://herveybayaustralia.com.au/ports/distfiles/linux-f10-nss_ldap.shar
if people want to check it out. Please don't hold back if there is
something I've missed.
I have a query on the tabbing - I have either ee or gedit (atm) how can
I set them to the correct tab spacing?
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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/11/12 07:11, Alexander Leidinger wrote:
On Mon, 09 Jan 2012 15:55:48 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
The PORTVERSION looks a little bit off to me. I would use something
like ${NSS_LDAP_VERSION} or ${NSS_LDAP_VERSION}.${RPMVERSION} (the
later may look a little bit strange... or not) to make it easy to
compare what is installed on a system with what is available on linux.
Yeah, I'm still stuck on that - trying to find more info on what to use
there. I've checked the handbook cover to cover, but still haven't
discovered anything. I've left it till last to work out.
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search for
it. If we have them (and they are OK), it would be better to use the
bsd.sites.mk shortcodes for them. This would change automatically the
master sites for this port if they are changed/improved in bsd.sites.mk.
I'm not 100% sure about the fedora archives, but I don't think they're
exactly right. I keep getting (in most linux ports) a hunt through the
MASTER_SITES for the file, starting with the archives.
The other pbone.net is definitely not in the sites list. I did check
that file thoroughly using grep and by manual sighting.
One thing to note though is that when I tried with MASTER_SITES set to
the FEDORA_LINUX set it failed to find the files. Also the files I need
are only on pbone.net- they are more recent than the original. Or can I
set the rpm version to float a bit?
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
Hmmm... I would expect that USE_LINUX_RPM automatically sets
USE_LINUX_PREFIX... to be verified.
Possibly. I just wanted to be sure. I'll try it with it removed once I
get it working correctly.
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ];
then \ rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf
${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam* fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
\ usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
\ usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.includebsd.port.mk
The man pages under the linux chroot, but the docs I thought would go
into the /usr/share/doc/as linux-f10-nss_ldap?
If you are talking about the FreeBSD location /usr/share/doc and not
the linux location /compat/linux/usr/share/doc:
Linux ports are special to this. In the linux base we do not bend the
install to put some stuff outside of /compat/linux.
If you talk about the linux location: we do not bend the stuff
inside /compat/linux to complay to the FreeBSD hier-man-page.
Or short: let the RPM install the files where it wants to have them. Do
not move them around.
Ok, ok, I'll leave them alone :) I did mention that I was over-thinking
things before... I am pedantic enough to stick by the rules though.
On an aside I noticed that there is a better site to use straight up
for linux dist rpms
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/11/12 07:11, Alexander Leidinger wrote:
On Mon, 09 Jan 2012 15:55:48 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
The PORTVERSION looks a little bit off to me. I would use something
like ${NSS_LDAP_VERSION} or ${NSS_LDAP_VERSION}.${RPMVERSION} (the
later may look a little bit strange... or not) to make it easy to
compare what is installed on a system with what is available on linux.
Yeah, I'm still stuck on that - trying to find more info on what to use
there. I've checked the handbook cover to cover, but still haven't
discovered anything. I've left it till last to work out.
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
I can't remember if we have the fedora archives in bsd.sites.mk (if
not, it would be worth to add it), and I'm too lazy ATM to search for
it. If we have them (and they are OK), it would be better to use the
bsd.sites.mk shortcodes for them. This would change automatically the
master sites for this port if they are changed/improved in bsd.sites.mk.
I'm not 100% sure about the fedora archives, but I don't think they're
exactly right. I keep getting (in most linux ports) a hunt through the
MASTER_SITES for the file, starting with the archives.
The other pbone.net is definitely not in the sites list. I did check
that file thoroughly using grep and by manual sighting.
One thing to note though is that when I tried with MASTER_SITES set to
the FEDORA_LINUX set it failed to find the files. Also the files I need
are only on pbone.net- they are more recent than the original. Or can I
set the rpm version to float a bit?
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
Hmmm... I would expect that USE_LINUX_RPM automatically sets
USE_LINUX_PREFIX... to be verified.
Possibly. I just wanted to be sure. I'll try it with it removed once I
get it working correctly.
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ];
then \ rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf
${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam* fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
\ usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
\ usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.includebsd.port.mk
The man pages under the linux chroot, but the docs I thought would go
into the /usr/share/doc/as linux-f10-nss_ldap?
If you are talking about the FreeBSD location /usr/share/doc and not
the linux location /compat/linux/usr/share/doc:
Linux ports are special to this. In the linux base we do not bend the
install to put some stuff outside of /compat/linux.
If you talk about the linux location: we do not bend the stuff
inside /compat/linux to complay to the FreeBSD hier-man-page.
Or short: let the RPM install the files where it wants to have them. Do
not move them around.
Ok, ok, I'll leave them alone :) I did mention that I was over-thinking
things before... I am pedantic enough to stick by the rules though.
On an aside I noticed that there is a better site to use straight up
for linux dist rpms
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/10/12 08:28, Paul Schmehl wrote: --On January 9, 2012 3:55:48 PM +1000 Da Rock freebsd-po...@herveybayaustralia.com.au wrote: I just need to work out how to check the checksum against a linux source. I haven't found that yet. My brief search was unsuccessful as well. Is it really possible that the LInux community has abandoned providing checksums for RPM packages? If so, that boggles the mind. Surely they don't believe their repositories are unassailable? I don't know. I believe they have a gpg key they use, at least with their repo system. How that specifically works I don't know. ___ 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: define issue - linux-f10-nss_ldap: my first port - be gentle :)
I'm having some trouble using knobs and defined in the Makefile. It keeps complaining about the unexpected. I've tried .if defined(WITH_PAM) and .ifdefined(WITH_PAM) and it complains about an unexpected ( in the first, and an unexpected word in the second. How do I conditionally handle the knobs? ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
All arguments aside, I've finally made headway - I think... its really
frustrating for me because to me it seems a bit of a blackbox atm. I'm
still trying to untangle the threads.
I fiddled and tweaked and finally got make to run. I then ran make
-DPACKAGE_BUILD makesum and got a checksum (SHA256 too). All the while I
had portlint run every now and again spitting out errors I couldn't
quite translate. After makesum I ran it again and it said looks fine.
- I called have slapped it silly! :) Bloody pretentious snot... could've
been more helpful earlier
I just need to work out how to check the checksum against a linux
source. I haven't found that yet.
Now my Makefile looks like this:
# New ports collection makefile for:linux-f10-nss_ldap
# Date created: 2012-01-04
# Whom: da porta
port_maintai...@herveybayaustralia.com.au
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=0.01
CATEGORIES=net linux
MASTER_SITES=
ftp://ftp.pbone.net/mirror/archive.fedoraproject.org/fedora/linux/updates/testing/10/i386/
\
http://archives.fedoraproject.org/pub/archive/fedora/linux/releases/10/Everything/i386/os/Packages/
\
http://herveybayaustralia.com.au/ports/distfiles/
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${NSS_LDAP_VERSION}-${RPMVERSION}
MAINTAINER=port_maintai...@herveybayaustralia.com.au
COMMENT=RFC 2307 NSS Module (Linux Fedora 10)
LICENSE=GPLv2
NSS_LDAP_VERSION=264
USE_LINUX_RPM= yes
USE_LINUX_PREFIX=yes
LINUX_DIST_VER= 10
RPMVERSION= 6.fc10
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=
${PREFIX}/usr/share/doc/${PKGNAMEPREFIX}-${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
post-extract:
.if !defined(WITH_PAM)
@if [ -f ${WRKDIR}/lib/security/pam_ldap.so ]; then \
rm -rf ${WRKDIR}/lib/
fi
@if [ -f
${WRKDIR}/usr/share/doc/nss_ldap-264/COPYING.pam_ldap ]; then \
rm -rf ${WRKDIR}/usr/share/doc/nss_ldap-264/*.pam*
fi
.else
PLIST_FILES+=lib/security/pam_ldap.so \
usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap \
usr/share/doc/nss_ldap-264/COPYING.pam_ldap \
usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap \
usr/share/doc/nss_ldap-264/NEWS.pam_ldap \
usr/share/doc/nss_ldap-264/README.pam_ldap \
usr/share/doc/nss_ldap-264/ldap.conf.pma_ldap
.endif
@if [ -f ${WRKDIR}/etc/ldap.conf ]; then \
${MV} -p ${WRKDIR}/etc/ldap.conf
${WRKDIR}/etc/ldap.conf.dist;
fi
PLIST_FILES+=usr/share/doc
post-install:
@${CAT} ${PKGMESSAGE}
.include bsd.port.mk
I'm cutting it to the bone as much as I can. But I am also trying to cut
some of the files that are unnecessary and could be risky. After running
make the directory looks like this:
./
./Makefile
./pkg-descr
./work
./work/etc
./work/etc/ldap.conf
./work/lib
./work/lib/security
./work/lib/security/pam_ldap.so
./work/usr
./work/usr/lib
./work/usr/lib/libnss_ldap-264.so
./work/usr/lib/libnss_ldap.so
./work/usr/lib/libnss_ldap.so.2
./work/usr/share
./work/usr/share/doc
./work/usr/share/doc/nss_ldap-264
./work/usr/share/doc/nss_ldap-264/ANNOUNCE.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.nss_ldap
./work/usr/share/doc/nss_ldap-264/AUTHORS.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.LIB.pam_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.nss_ldap
./work/usr/share/doc/nss_ldap-264/COPYING.pam_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.nss_ldap
./work/usr/share/doc/nss_ldap-264/ChangeLog.pam_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.nss_ldap
./work/usr/share/doc/nss_ldap-264/NEWS.pam_ldap
./work/usr/share/doc/nss_ldap-264/README.TLS
./work/usr/share/doc/nss_ldap-264/README.nss_ldap
./work/usr/share/doc/nss_ldap-264/README.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.nss_ldap
./work/usr/share/doc/nss_ldap-264/ldap.conf.pam_ldap
./work/usr/share/doc/nss_ldap-264/ldapns.schema
./work/usr/share/doc/nss_ldap-264/ns-pwd-policy.schema
./work/usr/share/doc/nss_ldap-264/nsswitch.ldap
./work/usr/share/doc/nss_ldap-264/pam.d
./work/usr/share/doc/nss_ldap-264/pam.d/chfn
./work/usr/share/doc/nss_ldap-264/pam.d/chsh
./work/usr/share/doc/nss_ldap-264/pam.d/ftp
./work/usr/share/doc/nss_ldap-264/pam.d/gdm
./work/usr/share/doc/nss_ldap-264/pam.d/halt
./work/usr/share/doc/nss_ldap-264/pam.d/imap
./work/usr/share/doc/nss_ldap-264/pam.d/kde
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/07/12 19:11, Gary Jennejohn wrote: On Sat, 07 Jan 2012 12:46:54 +1000 Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: And finally checksums: I create a checksum for the port, the linux sites have checksums, and I was advised in passing to check the checksums match. The checksums are going to differ aren't they? Linux and BSD checksums wouldn't be the same, surely? MD5 checksums should always match - it's the same algorithm. Not sure what the various distros use for Linux. Thats my point - linux uses SHA256 I believe. And thats not my biggest problem. As I suspected the linux sites have removed the rpm, so I have to either find it on a host somewhere or host it myself. My goal is to somehow prepend MASTERSITES to look to my host first, then one of the linux sites, then a backup host? and hopefully one will hit if mine is down for whatever reason. Has anyone had any experience with rpm.pbone.net? ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 21:18, Gary Jennejohn wrote:
On Thu, 05 Jan 2012 09:52:40 +1000
Da Rockfreebsd-po...@herveybayaustralia.com.au wrote:
On 01/04/12 23:27, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rockfreebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
Ok, thats good so far then. Thanks for the assessment.
Now, what's portlint?
/usr/ports/ports-mgmt/portlint. It does syntax checking on the Makefile
and checks things like correct checksums in distfile. You run it in the
port's directory.
And I have a question or two about the rpm. Do I need to script
something to just extract the files needed, or is it already in the mk
files already somewhere?
I suspect that setting USE_LINUX_RPM= yes in Makefile should be all
you need, but I've never done a RPM port. Some seem to use only
LINUX_RPM_ARCH= i386, which is the only option at the moment since
we don't have a AMD64 Linux base port.
And how do I work out the url for fetching the rpm? This particular one
is a moving target as the distro is already eol. Is it stored on the
FreeBSD servers? Or what do I do here?
That could be a problem. Maybe a committer could host it for you. I'm
hosting flwm-1.00.tgz, although I don't think it's used anymore.
In the porters handbook it mentions checksums and make makesum - does
that mean I have to put it in the ports tree to try it?
I just update Makefile, fetch the tarball and then run make makesum
before generating diffs or making a tarball of the port.
And is pkg-message scripted or do I just create it?
See the comment in /usr/ports/Mk/bsd.port.mk. There are lots of very
informative comments in that file.
I've read that before too, but I seem to be missing something
fundamental about ports here. I need to get a handle on all this before
I can proceed. I'm pulling it apart now, anyway.
There are native ports, and there are the linux base ports. For the
native ports the maintainer hosts? But these linux ports are they hosted
on the linux rpm sites? Or are they hosted by the maintainer? So I
believe I cannot sort a few things out until I know exactly what is
going on here. As I mentioned its eol, but if the rest come from the
linux sites...
All I want is 3 files from the usr/lib in the rpm (I think). What I
couldn't quite ascertain is what is done here in the bsd.linux-rpm.mk:
is it extracted and the files copied by make? Or is the rpm installed as
in linux?
If I have to find a host for it I can host it, but what opportunities
for a backup site exist in case of failure? Do I have to arrange that as
the maintainer, or is it mirrored by FreeBSD automatically? Ideally I
suppose both those scenarios would be in order.
And Chris, the license to most linux core stuff is GPL - I also checked
the COPYING file for nss_ldap (as that is the only one we're concerned
with here) and its GPLv2.
I've been spending the past few days trying to work out a tinderbox but
my resources are stretched. I'm hoping to rectify this in the near
future, but so far nada...
The checksums are all tied up with the hosting and so I'm still stuck
there until I work it out, Paul. So I have to untangle these threads so
I have a clearer picture on what I'm doing. from what I understand in
what you're telling me it means I have to create the checksums to make
available from the site, and makesum downloads it. If thats right, what
do I have to do to create them? The handbook says differently (I think?
Maybe I'm reading it wrong...)
Re: linux-f10-nss_ldap: my first port - be gentle :)
Ok, clean slate. Lets start afresh :) First I need a way to test properly. Alex, you mention I need a ports tree on the machine, and then you say to create a directory somewhere and put Makefile in it and run make (as root). Does the directory need to be in the ports tree then? The rpm files extracted: is there anyway to distinguish which files are copied or is it simply put into LINUXBASE wholesale? I ask because the rpm in question contains pam libraries which are unneeded obviously as authentication is done by the host? system. I believe this could represent a bit of a security risk, but I suppose one could setup an option if wanted. And how does this affect PLIST? And by running make a port is normally built in the port's directory. In the case of a linux port it is only downloaded into the distfiles/. Is it extracted during make or make install though? I couldn't quite determine that categorically. I've also changed the Makefile to use bsd.linux-rpm.mk instead of bsd.port.mk. I have setup a pkg-descr file to be put in the directory. Chris, you're right about the license situation. I nearly fell for it: ass-u-me... :) Hosting: I downloaded the rpm myself (including srpm), and I can host them and maybe arrange for them to be hosted elsewhere as well. Can I use MASTER_SITES to append/prepend? I also have to untangle the web of how to determine which file to download - argh hem! Sorry, fetch ;) if the linux-f10 base ports are obtained from the Fedora sites, then what happens if f10 rpms are no longer available there? And finally checksums: I create a checksum for the port, the linux sites have checksums, and I was advised in passing to check the checksums match. The checksums are going to differ aren't they? Linux and BSD checksums wouldn't be the same, surely? I'll keep at it in the meantime... :) ___ 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
linux-f10-nss_ldap: my first port - be gentle :)
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.include bsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/04/12 23:27, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rockfreebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
Ok, thats good so far then. Thanks for the assessment.
Now, what's portlint?
And I have a question or two about the rpm. Do I need to script
something to just extract the files needed, or is it already in the mk
files already somewhere?
And how do I work out the url for fetching the rpm? This particular one
is a moving target as the distro is already eol. Is it stored on the
FreeBSD servers? Or what do I do here?
In the porters handbook it mentions checksums and make makesum - does
that mean I have to put it in the ports tree to try it?
And is pkg-message scripted or do I just create it?
Thanks again.
___
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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 07:10, Alexander Leidinger wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port
and I would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so
I've used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES= CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME= ${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
This should be you (if you're willing to maintain the port).
You keep dropping hints like this all the time Alex :)
Honestly, though, I'm not sure whats involved or whether I'm capable of
handling the responsibility. This one is not likely to change too much
over time, but my skills are probably wanting.
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
This does not sound like you took a Fedora 10 RPM here, but you
specified in LINUX_DIST_VER that you use Fedora 10.
I wasn't sure exactly what to put there yet, but this was a Makefile for
linux-f10-ucl so I thought it would be at least close. The filename is
supposed to be nss_ldap-264-6.fc10.i386.rpm.
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
You don't need DESCR this way, it looks like this sets it to the same
file (but in a different way) than the default value of DESCR.
I have a pkg-descr file setup. That should be right, isn't it?
.includebsd.port.mk
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
When doing the make makesum, please use make -DPACKAGE_BUILDING
makesum to get the checkums of the SRPMs recorded too. We are obliged
to provide the GNU sources the same way like the binaries, and IIRC we
have some logic which fetches the SRPMs on tha packaga bulding cluster.
Oh, dear. I'll have to go hunting for them then.
___
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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 12:11, Chad Perrin wrote: On Thu, Jan 05, 2012 at 10:42:17AM +1000, Da Rock wrote: On 01/05/12 07:10, Alexander Leidinger wrote: This should be you (if you're willing to maintain the port). You keep dropping hints like this all the time Alex :) Honestly, though, I'm not sure whats involved or whether I'm capable of handling the responsibility. This one is not likely to change too much over time, but my skills are probably wanting. The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 12:08, Chad Perrin wrote:
On Thu, Jan 05, 2012 at 09:53:25AM +1000, Da Rock wrote:
On 01/05/12 01:41, Chad Perrin wrote:
On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
freebsd-po...@herveybayaustralia.com.au wrote:
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
[snip]
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
It also lacks license information.
How do I set that? Its linux so its GPL.
This is an example from /usr/ports/x11/xsel-conrad/Makefile:
LICENSE=xsel-conrad
LICENSE_GROUPS= COPYFREE
LICENSE_NAME= xsel-conrad license
LICENSE_FILE= ${WRKSRC}/COPYING
LICENSE_PERMS= auto-accept dist-mirror dist-sell pkg-mirror pkg-sell
I'm not sure it's perfect port maintainer Makefile practice, but it
works, and it's a lot better than no license information at all in my
opinion. I'd suggest checking that Makefile to see where in the Makefile
to put it.
Ok. I've been working through the handbook step by step, and I'm stuck
at checksums so I probably haven't yet reached that part yet. I'll check
it out now
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 14:13, Janketh Jay wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys! On 01/04/2012 08:19 PM, Chad Perrin wrote: On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: On 01/05/12 12:11, Chad Perrin wrote: The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Other than that, I can always help out as much as I can with questions if you want to email me directly about your port. I know the ins-and-outs about porting and I'd be more than happy to lend a hand. Regards, Janky Jay, III Thanks Jay. ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 14:15, Eitan Adler wrote: On Wed, Jan 4, 2012 at 11:13 PM, Janketh Jayjan...@unfs.us wrote: As much as I hate to toss Chris Rees under the bus on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a mentor, I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Or just continue to ask on this mailing list. No need to bug specific people when you could get everyone to answer you. You could also pop by on #bsdports on EFNet. A lot of us hang out there. Oh you can be sure I'll be doing that :) I'm only just starting IRC (if thats what you mean there), but I'll drop in once I'm configured. ___ 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: libxul build hit the roof!
On 01/01/11 07:07, Chris Rees wrote: I would argue that anyone messing with CFLAGS should expect and know how to fix trouble like that. This would also save noise. Unless they're just following a HowTo off a site to improve performance. Besides that, is it really that hard to offer a warning? Chris Sorry for top-posting, Android won't let me quote, but K-9 can't yet do threading. On 31 Dec 2010 05:42, Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: On 12/31/10 02:47, jhell wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/29/2010 18:04, Da Rock wrote: I got it worked out in the end, but it still took 2G+ memory to build; so my suggestion is a warning to EU in the make process that this could take a lot of memory to build, and some suggestions as to how to prevent or workaround the problem so they don't go whining on the list about it being broken. Turning off OPTIMIZED_CFLAGS for 'libxul, firefox* thunderbird*' ports would have stopped all this swapping from happening. Is there a specific reason why you changed it from its defaults ? is there really anything to gain ? in respect to 'libxul'... I see your point and I'll raise you a does it matter? There are sites and howto's on improving performance overall, especially regarding the revival of older machines. The recommendation on a lot of these is to put CFLAGS+= -O -pipe in the make.conf. If they already have low memory, then they'll be up the creek won't they? And the updates won't happen so they'll simply be broken and unsure of why. I'd say a simple note to say whats up is definitely in order, to prevent a lot of traffic. I don't believe thats too hard to do, given jdk16 and OOO have messages reflecting HDD space. I only noticed the issue because I watched it happen- given the little relevance that most (including yourself) put on it, it would easily be overlooked unless a simple solution was presented. The only message you get from say portupgrade is new compiler error, most would then put it in the too hard basket. ___ 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-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-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: libxul build hit the roof!
On 12/31/10 02:47, jhell wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/29/2010 18:04, Da Rock wrote: I got it worked out in the end, but it still took 2G+ memory to build; so my suggestion is a warning to EU in the make process that this could take a lot of memory to build, and some suggestions as to how to prevent or workaround the problem so they don't go whining on the list about it being broken. Turning off OPTIMIZED_CFLAGS for 'libxul, firefox* thunderbird*' ports would have stopped all this swapping from happening. Is there a specific reason why you changed it from its defaults ? is there really anything to gain ? in respect to 'libxul'... I see your point and I'll raise you a does it matter? There are sites and howto's on improving performance overall, especially regarding the revival of older machines. The recommendation on a lot of these is to put CFLAGS+= -O -pipe in the make.conf. If they already have low memory, then they'll be up the creek won't they? And the updates won't happen so they'll simply be broken and unsure of why. I'd say a simple note to say whats up is definitely in order, to prevent a lot of traffic. I don't believe thats too hard to do, given jdk16 and OOO have messages reflecting HDD space. I only noticed the issue because I watched it happen- given the little relevance that most (including yourself) put on it, it would easily be overlooked unless a simple solution was presented. The only message you get from say portupgrade is new compiler error, most would then put it in the too hard basket. ___ 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
libxul build hit the roof!
I was doing an update of my system, and I hit these errors and skipped builds all over the place; so I've been eliminating them one by one and making the skipped list smaller. In the process of these investigations I noticed that my system practically froze several times and I spotted multiple pfaults through top. I also ran a lone run of just libxul as it was one in the list with an error: new compiler error. I then basically shut every app I was running down and ran it again with just top showing. I found that at least one part hit the roof of my system, with nsCharacter... something or rather running at 1430M+ in swap, and 520M+ resident when compiling. Does anyone else think it might be wise to put a warning during build saying that this could take over 2G+ of memory to compile, and rebuild with no apps running if it fails? ___ 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: libxul build hit the roof!
On 12/30/10 01:23, Anonymous wrote: Da Rockfreebsd-po...@herveybayaustralia.com.au writes: I was doing an update of my system, and I hit these errors and skipped builds all over the place; so I've been eliminating them one by one and making the skipped list smaller. In the process of these investigations I noticed that my system practically froze several times and I spotted multiple pfaults through top. Try building with -Wl,--no-keep-memory in CFLAGS/LDFLAGS. My guess is that you don't have enough memory to keep linking process from being swapped out. I also ran a lone run of just libxul as it was one in the list with an error: new compiler error. I then basically shut every app I was running down and ran it again with just top showing. I found that at least one part hit the roof of my system, with nsCharacter... something or rather running at 1430M+ in swap, and 520M+ resident when compiling. Does anyone else think it might be wise to put a warning during build saying that this could take over 2G+ of memory to compile, and rebuild with no apps running if it fails? No need to kill (inactive) apps, they'd be swapped out during build. I apologise, I should have been more specific. I have a system with 1G RAM, and 2G swap. This I would say is average, but I dare say there'd be others out there with less. It also runs as a desktop system. I got it worked out in the end, but it still took 2G+ memory to build; so my suggestion is a warning to EU in the make process that this could take a lot of memory to build, and some suggestions as to how to prevent or workaround the problem so they don't go whining on the list about it being broken. There are other ports out there with messages about drive space, why not memory? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[SOLVED] Re: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating
On 12/28/10 21:55, David Southwell wrote: On 12/27/10, David Southwell da...@vizion2000.net wrote: On 12/27/10, David Southwell da...@vizion2000.net wrote: Agreed - but following Doug's commit I can vouch that the PERL_THREADED hack was still needed for 7.2 p3 systems on amd64. It shouldn't be needed. Can you remove this definition from any locally-modified Makefiles, and provide the same information that was requested from Da Rock? (Why do I feel like a WWE announcer when I type that? ...) b. I do not want to rebuild WITHOUT_IMAGEMAGICK_PERL on a running system with active user access which needs perl. Have you got the replies from Da Rock? Before going any further I would suggest that Da Rock be advised to update his ports tree followed by # pkgdb -F Fix any problems then. If there are any problems he cannot fix at this stage then report those. Then: # portmaster -a or portupgrade -a If he gets any failure which may possibly be linked to a Perl problem he should rebuild perl with upward and downward recursion. e.g #portupgrade -rR lang/perl5.8 I dare say I'd come back with an error given I have 5.10 installed on the system. Until that is completed any other report could send us off on a wild goose chase. My twopennorth I can do what you suggested when we have a report from Da Rock with his results from a system with thoroughly updated ports. My guess is that his probs will be solved by the above. Ok, so it took a while and I'm still reviewing some other issues. The real problem is that the error msg sends all on a wild goose chase. I got it updated but the problem had absolutely nothing to do with perl, djvu, and their threads. After some scratching about with configs and Makefiles, I discover there is an option not selected (not sure why) dealing with ImageMagick's threads- not perls or djvus! Now, IF those options are selected (and remember this is an upgrade) why not assume threads and print an info msg saying so? And why does the error msg not even allude to this instead of sending everyone on a chase after a mythical error that is not even the fault of the dependency? Thanks for the hints guys, but I'm now trying to figure a method that may resolve this type of issue in the future- I remember using dialog boxes in extremely old installs of linux (and BSD packages I think) that automatically selects or deselects based on a selections required/incompatible dependencies. That would save hours of fart-arsing about for many- even searching for known answers takes time, easily resolved if something stable can be figured this way. Thanks again. ___ 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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating
On 12/27/10 20:22, David Southwell wrote: On 12/27/10 01:05, Roland Smith wrote: On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote: Something I'm missing here? A fix would be nice, I should be used to it though- ImageMagick _always_ has issues for me. I just thought it'd be nice to get it updated for once- it looked so close :) I'm getting something similar, have been for a couple of weeks: ** Port marked as IGNORE: graphics/ImageMagick: OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL ** Listing the failed packages (-:ignored / *:skipped / !:failed) - graphics/ImageMagick (marked as IGNORE) (Follow-ups redirected to ports@, or I tried to.) Hmm. I'm not alone then. I'll do some poking then and see what comes up... :) Any hints guys? Try building ImageMagick without perl support. Works for me, with EXR, but haven't tested with Djvu; cd /usr/ports/graphics/ImageMagick make config ┌── ──┐ │ Options for ImageMagick 6.6.5.10 │ │ ┌^(-)┐ │ ... │ │[X] IMAGEMAGICK_OPENEXR OpenEXR support (needs threads) │ │ │ │[X] IMAGEMAGICK_OPENMP OpenMP for SMP (needs threads) │ │ │ │[ ] IMAGEMAGICK_PDF PDF format support │ │ │ │[ ] IMAGEMAGICK_PERL Perl support │ │ ... Roland ImageMagick is already installed, so getting something to work is not a problem. Its updating it... What concerns me is perl-threaded _is_ installed but it can't see it. Do you have in: etc/make.conf PERL_THREADED=true Perhaps I'm a little daft atm. Either way I want to be clear: Are you saying the define needs to be in the make.conf so that it will build correctly? It _does not_ actually look at what perl is installed? IF that is the case, then wtf? Either ImageMagick should be checking the actual pkg installed, or the perl port should be defining this in the make.conf, right? Seeing as perl already makes a define in make.conf... Meanwhile I'll check it out. 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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating
On 12/26/10 23:04, Robert Huff wrote: Da Rock writes: I'm running another set of updates, and I can't for the life of me get rid of this erroneous behaviour. I run portupgrade and it tells me it can't update ImageMagick because the Djvu option requires threads, and needs perl, therefore perl needs to be threaded. So it comes up with an IGNORE which is nuts because I run threaded perl. #pkg_version -v | grep perl mod_perl2-2.0.4_2,3 = up-to-date with port perl-threaded-5.10.1_3 = up-to-date with port Something I'm missing here? A fix would be nice, I should be used to it though- ImageMagick _always_ has issues for me. I just thought it'd be nice to get it updated for once- it looked so close :) I'm getting something similar, have been for a couple of weeks: ** Port marked as IGNORE: graphics/ImageMagick: OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL ** Listing the failed packages (-:ignored / *:skipped / !:failed) - graphics/ImageMagick (marked as IGNORE) (Follow-ups redirected to ports@, or I tried to.) Hmm. I'm not alone then. I'll do some poking then and see what comes up... :) Any hints guys? ___ 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: ImageMagick, Djvu, and Perl-threaded - marked as IGNORE when updating
On 12/27/10 01:05, Roland Smith wrote: On Sun, Dec 26, 2010 at 11:42:37PM +1000, Da Rock wrote: Something I'm missing here? A fix would be nice, I should be used to it though- ImageMagick _always_ has issues for me. I just thought it'd be nice to get it updated for once- it looked so close :) I'm getting something similar, have been for a couple of weeks: ** Port marked as IGNORE: graphics/ImageMagick: OpenEXR requires threads. . Perl is non-threaded. Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL ** Listing the failed packages (-:ignored / *:skipped / !:failed) - graphics/ImageMagick (marked as IGNORE) (Follow-ups redirected to ports@, or I tried to.) Hmm. I'm not alone then. I'll do some poking then and see what comes up... :) Any hints guys? Try building ImageMagick without perl support. Works for me, with EXR, but haven't tested with Djvu; cd /usr/ports/graphics/ImageMagick make config ┌┐ │ Options for ImageMagick 6.6.5.10 │ │ ┌^(-)┐ │ ... │ │[X] IMAGEMAGICK_OPENEXR OpenEXR support (needs threads)│ │ │ │[X] IMAGEMAGICK_OPENMP OpenMP for SMP (needs threads) │ │ │ │[ ] IMAGEMAGICK_PDF PDF format support │ │ │ │[ ] IMAGEMAGICK_PERL Perl support │ │ ... Roland ImageMagick is already installed, so getting something to work is not a problem. Its updating it... What concerns me is perl-threaded _is_ installed but it can't see it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Rosegarden seg faults
Tried -questions@ but got no bites, plus I think its more appropriate here... I've installed rosegarden for a task my missus has to do. The only problem is its seg faults and can't do anything. I can run rosegarden at the prompt, but when I click notation or sequencer it fails with a seg fault. The symptoms are the same as bug #346448 at the debian bugs site, but that is 2006 and is supposedly resolved; although the version in freebsd hasn't seemed to have changed since then. I running Freebsd 8 amd64, rosegarden 2.1pl2. Running gdb I find: 0x000800c938b2 in _XtCountVaList () from /usr/local/lib/libXt.so.6 The fault was apparently solved in 2.1pl4-2. 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: net/samba-libsmbclient fails build
On Thu, 2009-01-29 at 12:22 +1100, David N wrote: 2009/1/27 Da Rock rock_on_the_...@comcen.com.au: I get the following error in this build (make, make install clean): In file included from libsmb/libsmbclient.c:25: include/includes.h:1112: error: conflicting types for 'krb5_set_real_time' /usr/local/include/krb5-protos.h:3486: error: previous declaration of 'krb5_set_real_time' was here I was considering debugging this myself and submitting it to you guys here, but then I looked closer... my question is now where do I submit this kind of info? If not here then let me know where. Cheers FreeBSD laptop1.herveybayaustralia.com.au 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Thu Jan 15 16:27:55 EST 2009 xxx...@laptop1.herveybayaustralia.com.au:/usr/obj/usr/src/sys/GENERIC 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 try rebuilding it with KRB5_HOME=/usr/local i think you need to do a make clean first and then do make install KRB5_HOME=/usr/local That didn't work. I've narrowed it down to broken Active Directory support, but I haven't been able to debug further- I will post when I get the time to do so. For now my system should start working again properly :) Perhaps, though, someone could add a note in the options that AD support is broken for this port? ___ 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/samba-libsmbclient fails build
On Tue, 2009-01-27 at 10:21 +1000, Da Rock wrote: I get the following error in this build (make, make install clean): In file included from libsmb/libsmbclient.c:25: include/includes.h:1112: error: conflicting types for 'krb5_set_real_time' /usr/local/include/krb5-protos.h:3486: error: previous declaration of 'krb5_set_real_time' was here I was considering debugging this myself and submitting it to you guys here, but then I looked closer... my question is now where do I submit this kind of info? If not here then let me know where. Cheers FreeBSD laptop1.herveybayaustralia.com.au 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Thu Jan 15 16:27:55 EST 2009 xxx...@laptop1.herveybayaustralia.com.au:/usr/obj/usr/src/sys/GENERIC amd64 Any ideas guys? Evolution won't start and neither will nautilus. ___ 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: xorg upgrade and /etc/ttys regression
On Tue, 2009-01-27 at 19:02 +0100, Oliver Lehmann wrote: Hi, I've used to start my login manager with /etc/ttys for years now (After I considered myself became to lazy to type startx). After yesterdays xorg upgrade I've noticed, that the login manager which comes up right after going to multiuser has no working mouse or keyboard support. This is probably because the login manager gets started by /sbin/init which uses getttyent which parses /etc/ttys. This all happens before hald is being started which is the problem here. So the solution seems to be to drop/remove login manager startups from /etc/ttys and move over to rc.d startup. This might be an information which others (people also using /etc/ttys) might find usefull so I'm sharing it... When upgrading to latest xorg - make sure you are retiring your /etc/ttys upgrade (Or am I the only one experiencing this? Maybe my system is just to slow to start hald fast enough? ;) I had a similar problem: I rebooted after a failed portupgrade -a and lost X. I then found out I needed to comment out RGBPath (which kinda fixed the X crashing) but XDM still wasn't working because update wasn't finished. So I uncommented the RGBPath, completed my update, and then commented RGBPath again (stopped X annoying me by popping up every so often due to ttys). XDM came up, but mouse wasn't working so I rebooted and it was fine again. I didn't need to change my method at all. Question is: which X are you running? 7.4? Might be hald is not started high enough on the list in rc.conf? ___ 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: Kdenlive video non linear editor port
On Mon, 2007-08-06 at 13:05 +0200, Chris Billington wrote: On 8/6/07, Angelo Turetta ature...@commit.it wrote: Chris Billington wrote: Has anyone had any success with producing a port for the Kdenlive video editor (kdenlive.sourceforge.net)? It looks like a more sophisticated version of Kino, indeed the Kino main developer is joining that project. It's indeed a totally different project from kino, based on much better design (multitrack timeline, ecc..). It's fun you ask today: I've been thinking for 6+ months about writing a port for kdenlive, and yesterday I decided I'd give a try. Not that hard, but the resulting binary has problems playing audio: I guess it's a device name problem. All other KDE applications can playback audio files, kdenlive not. If you want to try, or help me iron out the last issues, you can download the following files: http://www.commit.it/kdenlive-ports.tgz (ports for kdenlive/mlt/mlt++, untar in /usr/ports/multimedia) http://www.commit.it/kdenlive-20070804.tar.bz2 http://www.commit.it/mlt-20070804.tar.bz2 http://www.commit.it/mltpp-20070804.tar.bz2 (source tarballs extracted form SVN on 2007-08-04, save them in folder /usr/ports/distfiles) Then, to install: #cd /usr/ports/multimedia/kdenlive #make install I'm not yet sure what to do about tarball hosting, so the ports doesn't fetch automatically by now. Please beware that some dependencies may be missing (i.e.: it just occurred to me that I've not put multimedia/ffmpeg among the RUN/BUILD_DEPENDS, please install it before trying). I only tested on RELENG_6/AMD64. Let me know how it works for you Angelo Turetta. Fantastic news- will test tonight and report back. regards Chris Any further news on this project? ___ 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
net/samba-libsmbclient fails build
I get the following error in this build (make, make install clean): In file included from libsmb/libsmbclient.c:25: include/includes.h:1112: error: conflicting types for 'krb5_set_real_time' /usr/local/include/krb5-protos.h:3486: error: previous declaration of 'krb5_set_real_time' was here I was considering debugging this myself and submitting it to you guys here, but then I looked closer... my question is now where do I submit this kind of info? If not here then let me know where. Cheers FreeBSD laptop1.herveybayaustralia.com.au 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #0: Thu Jan 15 16:27:55 EST 2009 xxx...@laptop1.herveybayaustralia.com.au:/usr/obj/usr/src/sys/GENERIC 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
x11/libXrandr, x11-toolkits/libXmu, graphics/jasper fails to build
Here's another one: /bin/sh ../libtool --tag=CC--mode=link cc -D_THREAD_SAFE -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -DMALLOC_0_RETURNS_NULL -O2 -fno-strict-aliasing -pipe -version-number 2:1:0 -no-undefined -o libXrandr.la -rpath /usr/local/lib Xrandr.lo XrrConfig.lo XrrCrtc.lo XrrMode.lo XrrOutput.lo XrrProperty.lo XrrScreen.lo -L/usr/local/lib -lX11 -L/usr/local/lib -lXext -lXrender -lX11 grep: /usr/local/lib/libxcb-xlib.la: No such file or directory sed: /usr/local/lib/libxcb-xlib.la: No such file or directory libtool: link: `/usr/local/lib/libxcb-xlib.la' is not a valid libtool archive *** Error code 1 I tried a search myself: ng. I tried to find a config switch for libxcb: ng. Let me know what else you need or what I can do to help here. Obviously other ports are dependent on these and are therefore failing as well. FWIW this is an upgrade using portupgrade. 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: x11/libXrandr, x11-toolkits/libXmu, graphics/jasper fails to build
On Mon, 2009-01-26 at 22:04 -0500, Robert Noland wrote: On Tue, 2009-01-27 at 11:22 +1000, Da Rock wrote: Here's another one: /bin/sh ../libtool --tag=CC--mode=link cc -D_THREAD_SAFE -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -DMALLOC_0_RETURNS_NULL -O2 -fno-strict-aliasing -pipe -version-number 2:1:0 -no-undefined -o libXrandr.la -rpath /usr/local/lib Xrandr.lo XrrConfig.lo XrrCrtc.lo XrrMode.lo XrrOutput.lo XrrProperty.lo XrrScreen.lo -L/usr/local/lib -lX11 -L/usr/local/lib -lXext -lXrender -lX11 grep: /usr/local/lib/libxcb-xlib.la: No such file or directory sed: /usr/local/lib/libxcb-xlib.la: No such file or directory libtool: link: `/usr/local/lib/libxcb-xlib.la' is not a valid libtool archive *** Error code 1 I tried a search myself: ng. I tried to find a config switch for libxcb: ng. Let me know what else you need or what I can do to help here. Obviously other ports are dependent on these and are therefore failing as well. FWIW this is an upgrade using portupgrade. This is fallout from the libxcb update. xcb-xlib no longer exists, you need to update everything that depends on libxcb using your preferred method. robert. I'm now aware of that, but I'm trying to do the updates and nothing is working because they're all still asking for that package. I have to admit I'm not 100% proficient with updating to handle curl balls like this; can you supply some pointers as to how to get around this? I'd also like to point out that I just rebooted and X died in the hole... :) Missing rgb files and what not Thanks ___ 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/libXrandr, x11-toolkits/libXmu, graphics/jasper fails to build
On Tue, 2009-01-27 at 00:53 -0500, Robert Noland wrote: On Tue, 2009-01-27 at 15:28 +1000, Da Rock wrote: On Mon, 2009-01-26 at 22:04 -0500, Robert Noland wrote: On Tue, 2009-01-27 at 11:22 +1000, Da Rock wrote: Here's another one: /bin/sh ../libtool --tag=CC--mode=link cc -D_THREAD_SAFE -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -DMALLOC_0_RETURNS_NULL -O2 -fno-strict-aliasing -pipe -version-number 2:1:0 -no-undefined -o libXrandr.la -rpath /usr/local/lib Xrandr.lo XrrConfig.lo XrrCrtc.lo XrrMode.lo XrrOutput.lo XrrProperty.lo XrrScreen.lo -L/usr/local/lib -lX11 -L/usr/local/lib -lXext -lXrender -lX11 grep: /usr/local/lib/libxcb-xlib.la: No such file or directory sed: /usr/local/lib/libxcb-xlib.la: No such file or directory libtool: link: `/usr/local/lib/libxcb-xlib.la' is not a valid libtool archive *** Error code 1 I tried a search myself: ng. I tried to find a config switch for libxcb: ng. Let me know what else you need or what I can do to help here. Obviously other ports are dependent on these and are therefore failing as well. FWIW this is an upgrade using portupgrade. This is fallout from the libxcb update. xcb-xlib no longer exists, you need to update everything that depends on libxcb using your preferred method. robert. I'm now aware of that, but I'm trying to do the updates and nothing is working because they're all still asking for that package. I have to admit I'm not 100% proficient with updating to handle curl balls like this; can you supply some pointers as to how to get around this? I don't use portupgrade, so someone more proficient with it can probably be of more assistance. You did read UPDATING, right? Actually I'm ashamed to say it didn't occur to me to look at that... :S I'd also like to point out that I just rebooted and X died in the hole... :) Missing rgb files and what not Depending on the state of the upgrade, this is not really surprising. Me either- I'm afraid my brain happened to be on suspend mode at the time :D I did an elaborate search on google and found a reference to try portupgrade -a -rf libxcb so I'm in the middle of that (which seems to be working- fingers crossed), and having just read UPDATING I found a reference to use portupgrade -rf. Therefore, given my current circumstances, the cmd I've given could very well work- I hope! :) I'll post back if it doesn't... ___ 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
[Fwd: Re: Firebird client fails port install]
I tried the questions list, but I can't seem to get an answer apart from a workaround (which I already implemented anyway). Any ideas on how to fix this? ---BeginMessage--- On Mon, 2008-12-15 at 14:29 -0500, Lowell Gilbert wrote: Da Rock rock_on_the_...@comcen.com.au writes: I'm trying to install php5-extensions (which includes firebird), but its failing with an error code 1 on firebird20-client. It does mention running make to build firebird, but not as root. So I've tried everything to get this to work: running make as my wheel group user, installing as a pkg instead. What could I be missing? (And before anybody asks: I ran portsnap fetch update twice yesterday - and I did run the update. I've learnt my lesson from last time...) Unless you set variables to put the work directory somewhere non-standard, the ports system will try to do its building under each port's directory, which is normally not writable by regular users. Similarly, installing a port (or a package, for the same reasons) normally requires root permissions for access to system directories and in many cases to let programs installed by ports run as special-purpose users. What is the reason you're trying to install ports as a different user? Because the first stop error occurs and it says to run make to build firebird, but it also says Please do not build firebird as 'root' because this may cause conflicts with SysV semaphores of running services. ___ freebsd-questi...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ---End Message--- ___ 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: Kde4 install - no Xorg
On Sat, 2008-11-29 at 02:26 +0100, Alexey Shuvaev wrote: On Sat, Nov 29, 2008 at 10:10:28AM +1000, Da Rock wrote: Funny thing happened to me on a new install... [snip] A day and a half later, the install is finished so I run kdm. Not found so I run a find search and then run /usr/local/kde4/bin/kdm. It comes up saying it can't find and run the Xserver on display :0. What the?! So I run a search on pkg_version -v and find xorg is not installed- what the?! Maybe I'm missing something here, but I thought installing kde4 would install xorg (I'm pretty sure it has before if I remember right- it has been a while, but I'm sure I'm not that daft) as it kinda needs it to run and ports generally install dependencies. Has someone forgotten this in the Makefile? Not trying to be picky, but I thought it might more sense and offer my view :) Well, I would say it is not a bug, it is a feature of X window system. I think that X libraries are there, it is X server missing. One can install all X applications on one machine (let's say, server) and X servers on any number of graphical terminals (yes, X servers are run on what is normally called a client). After that it is possible to point clients on the server to the right X server (via DISPLAY environment, for example). That way the application will be run on server displaying output and receiving input from the remote X server. (Yes the terminology is weird :) If you don't care about unnecessary components you can cd /usr/ports/x11/xorg make intstall clean Yeah I do understand all that, but it did kinda take me by surprise to find that no xserver was installed (or at least an option to install xorg wasn't offered in that cool little config window now available). The libraries were installed, for reference. That feature to point the clients to one machine is cool, and I have used it before between desktops, but how often do sysadmins use it like this on a regular basis as a standalone terminal server? Most regular setups (xwindow anyway) would normally be running on a decentralised basis unless there was a specific need, surely. Just a little warning and/or the option to install xorg might be in order to give people a heads up would be in order I'm sure. Obviously not a high priority, but a reasonable request. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FBSD 7, Gnome2-lite port broken
On Mon, 2008-04-21 at 00:17 +0200, Alexey Shuvaev wrote: plain text document attachment (gstscrpt) On Sun, Apr 20, 2008 at 05:16:43AM +1000, Da Rock wrote: I've tried checking as far as my knowledge will allow the reason for this error, but its got me beat. I was installing the above port, and the config screen came up for one of its dependencies surrounding ghostscript I believe where it said don't be stingy on the options selected as another port might need it later. So I checked them all as I probably will need them all at some point in the future. Also to note here there was a majority already selected to begin with. Unfortunately, I can't find that screen again to uncheck some options, and I think its ghostscript-gpl which is failing. It errors on not finding vga.h and lvga.h files. So I installed all src's from sysinstall, but NG. It seems that you have checked lvga256 and vgalib options in ghostscript-gpl configuration dialog. This dialog is not the standart port's OPTIONS dialog and it doesn't remember the options you have choosen between builds. So, to fix the build: cd /usr/ports/print/ghostscript-gpl make clean make install Once you are in this dialog again, just go on with the defaults. BTW, can someone more experienced comment on reasons to have non-standard configure script? Possibly related: are there any non-trivial reasons to have ghostscript (rather significant for many other ports) maintained by ports@ ? Or are there just no volunteers? Thank god! I got that dialog again... Thanks for that bit of saving info. But I think the more important question here is why does it say go nuts with the options submitted (which you can't go back and make config) if there's these traps in there. Perhaps it should say don't change them unless you know what you're in for (or doing)? Cheers! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FBSD 7, Gnome2-lite port broken
I've tried checking as far as my knowledge will allow the reason for this error, but its got me beat. I was installing the above port, and the config screen came up for one of its dependencies surrounding ghostscript I believe where it said don't be stingy on the options selected as another port might need it later. So I checked them all as I probably will need them all at some point in the future. Also to note here there was a majority already selected to begin with. Unfortunately, I can't find that screen again to uncheck some options, and I think its ghostscript-gpl which is failing. It errors on not finding vga.h and lvga.h files. So I installed all src's from sysinstall, but NG. I think I have to ways to solve this: find the vga files it wants, or find that screen again and uncheck those options. The former seems like the responsible thing to do (if it can be resolved), but I'll settle for the latter if I have to. Unless, of course, I can be of some help to the list in this issue... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openldap server install failure - openldap client conflict
On Wed, 2008-04-16 at 07:03 +0100, Matthew Seaman wrote: Da Rock wrote: I'm trying to install OpenLDAP as a server to attempt to try it out for our network. The problem is the openldap client is already installed for other apps as php, apache, asterisk, etc. So my question is: is it possible to uninstall the client? Will the server include the client required for these other apps? The client installs libldap.so and liblber.so (plus variants based on OpenLDAP version and ABI version) -- like so for OpenLDAP 2.3: /usr/local/lib/liblber-2.3.so /usr/local/lib/liblber-2.3.so.2 /usr/local/lib/liblber.a /usr/local/lib/liblber.la /usr/local/lib/liblber.so /usr/local/lib/libldap-2.3.so /usr/local/lib/libldap-2.3.so.2 /usr/local/lib/libldap.a /usr/local/lib/libldap.la /usr/local/lib/libldap.so /usr/local/lib/libldap_r-2.3.so /usr/local/lib/libldap_r-2.3.so.2 /usr/local/lib/libldap_r.a /usr/local/lib/libldap_r.la /usr/local/lib/libldap_r.so (OpenLDAP 2.4 does similarly except replace '2.3' with '2.4') If you force uninstall openldap-client, then everything depending on it will refuse to run because of the unfulfilled shlib dynamic linkage. One of the programs that depends on the client is OpenLDAP-server -- so just by typing portinstall net/openldap23-server you'll cause openldap23-client (or openldap23-sasl-client) to be installed as a normal consequence of ports dependency resolution. The problem comes if you've already got, say, openldap23-client installed and you want openldap24-client -- other applications: Apache, PHP etc. will work with just about any LDAP version but openldap-server needs the matching client version. The solution is something like this: # portupgrade -o net/openldap24-client -f openldap-client-2.3.41 # portupgrade -fr openldap-client-2.4.8 to switch from the 23 series to the 24 series. Also -- handy tip -- adding flags like the following to /etc/make.conf will generally enable LDAP and SASL capabilities for any ports that can support them. (SASL highly recommended for securing access to LDAP, and also LDAP highly recommended as a back-end for SASL...) WITH_SASL= yes WITH_LDAP=yes WANT_OPENLDAP_VER= 23 WANT_OPENLDAP_SASL= yes However, don't insert the 'WANT_OPENLDAP_VER' line into /etc/make.conf until /after/ you've got the right openldap-client port installed, as it screws up switching between versions. 23 is the default stable release, 24 is also available but still in beta. So my question was if I install the server I'll get the client, and you're saying yes? If thats the case then, why is it stopping because the client is already installed? And while I'm here... I tried installing the odbc backend, but it conflicts with other apps as well. How can I have both the libiodbc and unixodbc at the same time for openldap server (requires libiodbc), php5, etc? Do you really need the odbc *backend* for LDAP? That allows LDAP to store its data in a MSSQL database somewhere -- which implies the data store is on a different server to the OpenLDAP instance. That's not ideal for good performance. Unless you know you have a specific need for one of the particular back-ends and certainly if you are a beginner with openldap, I'd strongly recommend sticking with the default local storage based on Berkeley DB. Actually I thought it covered most sql servers not just mssql- if thats the case then good bye for sure. I was interested in maybe mysql though- this is not usable for that I take it? If your aim is to interoperate with ActiveDirectory then I believe that is possible at the LDAP level via the usual delegation and referral mechanisms. It may even be possible to replicate either to or from AD or to use OpenLDAP (+ Kerberos + Samba v4 I think) as a drop in replacement for AD. I have no direct knowledge of that, but I'm sure a little Google action will turn up any number of HowTos on the subject. Replacing a Windows server would be a nice goal... I will succeed on that one in the near future- just not this project. Thanks for the help. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openldap server install failure - openldap client conflict
On Wed, 2008-04-16 at 16:48 +1000, Da Rock wrote: On Wed, 2008-04-16 at 07:03 +0100, Matthew Seaman wrote: Da Rock wrote: I'm trying to install OpenLDAP as a server to attempt to try it out for our network. The problem is the openldap client is already installed for other apps as php, apache, asterisk, etc. So my question is: is it possible to uninstall the client? Will the server include the client required for these other apps? The client installs libldap.so and liblber.so (plus variants based on OpenLDAP version and ABI version) -- like so for OpenLDAP 2.3: /usr/local/lib/liblber-2.3.so /usr/local/lib/liblber-2.3.so.2 /usr/local/lib/liblber.a /usr/local/lib/liblber.la /usr/local/lib/liblber.so /usr/local/lib/libldap-2.3.so /usr/local/lib/libldap-2.3.so.2 /usr/local/lib/libldap.a /usr/local/lib/libldap.la /usr/local/lib/libldap.so /usr/local/lib/libldap_r-2.3.so /usr/local/lib/libldap_r-2.3.so.2 /usr/local/lib/libldap_r.a /usr/local/lib/libldap_r.la /usr/local/lib/libldap_r.so (OpenLDAP 2.4 does similarly except replace '2.3' with '2.4') If you force uninstall openldap-client, then everything depending on it will refuse to run because of the unfulfilled shlib dynamic linkage. One of the programs that depends on the client is OpenLDAP-server -- so just by typing portinstall net/openldap23-server you'll cause openldap23-client (or openldap23-sasl-client) to be installed as a normal consequence of ports dependency resolution. The problem comes if you've already got, say, openldap23-client installed and you want openldap24-client -- other applications: Apache, PHP etc. will work with just about any LDAP version but openldap-server needs the matching client version. The solution is something like this: # portupgrade -o net/openldap24-client -f openldap-client-2.3.41 # portupgrade -fr openldap-client-2.4.8 to switch from the 23 series to the 24 series. Also -- handy tip -- adding flags like the following to /etc/make.conf will generally enable LDAP and SASL capabilities for any ports that can support them. (SASL highly recommended for securing access to LDAP, and also LDAP highly recommended as a back-end for SASL...) WITH_SASL= yes WITH_LDAP= yes WANT_OPENLDAP_VER= 23 WANT_OPENLDAP_SASL= yes However, don't insert the 'WANT_OPENLDAP_VER' line into /etc/make.conf until /after/ you've got the right openldap-client port installed, as it screws up switching between versions. 23 is the default stable release, 24 is also available but still in beta. So my question was if I install the server I'll get the client, and you're saying yes? If thats the case then, why is it stopping because the client is already installed? Actually, let me clarify: The error message I get is openldap-sasl-server-2.3.40 conflicts with installed package openldap-client-2.3.40, they install files into the same place. Therefore, I cannot install openldap server 2.3.40 And while I'm here... I tried installing the odbc backend, but it conflicts with other apps as well. How can I have both the libiodbc and unixodbc at the same time for openldap server (requires libiodbc), php5, etc? Do you really need the odbc *backend* for LDAP? That allows LDAP to store its data in a MSSQL database somewhere -- which implies the data store is on a different server to the OpenLDAP instance. That's not ideal for good performance. Unless you know you have a specific need for one of the particular back-ends and certainly if you are a beginner with openldap, I'd strongly recommend sticking with the default local storage based on Berkeley DB. Actually I thought it covered most sql servers not just mssql- if thats the case then good bye for sure. I was interested in maybe mysql though- this is not usable for that I take it? If your aim is to interoperate with ActiveDirectory then I believe that is possible at the LDAP level via the usual delegation and referral mechanisms. It may even be possible to replicate either to or from AD or to use OpenLDAP (+ Kerberos + Samba v4 I think) as a drop in replacement for AD. I have no direct knowledge of that, but I'm sure a little Google action will turn up any number of HowTos on the subject. Replacing a Windows server would be a nice goal... I will succeed on that one in the near future- just not this project. Thanks for the help. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openldap server install failure - openldap client conflict
On Wed, 2008-04-16 at 08:29 +0100, Matthew Seaman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Da Rock wrote: On Wed, 2008-04-16 at 07:03 +0100, Matthew Seaman wrote: Da Rock wrote: One of the programs that depends on the client is OpenLDAP-server -- so just by typing portinstall net/openldap23-server you'll cause openldap23-client (or openldap23-sasl-client) to be installed as a normal consequence of ports dependency resolution. The problem comes if you've already got, say, openldap23-client installed and you want openldap24-client -- other applications: Apache, PHP etc. will work with just about any LDAP version but openldap-server needs the matching client version. The solution is something like this: # portupgrade -o net/openldap24-client -f openldap-client-2.3.41 # portupgrade -fr openldap-client-2.4.8 to switch from the 23 series to the 24 series. So my question was if I install the server I'll get the client, and you're saying yes? If thats the case then, why is it stopping because the client is already installed? Usually the problem there is either: that the openldap client that the openldap server requires is different to the one that is already installed, or else that the WANT_OPENLDAP_VER or other settings (particularly SASL related ones) in /etc/make.conf or from the OPTIONS dialog differ from one or other or both of the installed openldap-client and openldap-server. Get everything in synch and it will all go smoothly. A! Thats more than likely the problem... I'll let you know if it fails. And while I'm here... I tried installing the odbc backend, but it conflicts with other apps as well. How can I have both the libiodbc and unixodbc at the same time for openldap server (requires libiodbc), php5, etc? Do you really need the odbc *backend* for LDAP? That allows LDAP to store its data in a MSSQL database somewhere -- which implies the data store is on a different server to the OpenLDAP instance. That's not ideal for good performance. Unless you know you have a specific need for one of the particular back-ends and certainly if you are a beginner with openldap, I'd strongly recommend sticking with the default local storage based on Berkeley DB. Actually I thought it covered most sql servers not just mssql- if thats the case then good bye for sure. I was interested in maybe mysql though- this is not usable for that I take it? I believe there is a direct SQL backend which would work with a locally installed instance of MySQL, or possibly various others (PostgreSQL, SQLite) Even so, it's not a magic solution to make LDAP work better -- quite the reverse in fact, as it adds extra layers of overhead. It's one of those things where if you think you might possibly want it, then actually you don't -- only use it when you absolutely know you need it. I thought it might be easier to administrate - no? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openldap server install failure - openldap client conflict
On Wed, 2008-04-16 at 16:48 +1000, Da Rock wrote: On Wed, 2008-04-16 at 07:03 +0100, Matthew Seaman wrote: Da Rock wrote: I'm trying to install OpenLDAP as a server to attempt to try it out for our network. The problem is the openldap client is already installed for other apps as php, apache, asterisk, etc. So my question is: is it possible to uninstall the client? Will the server include the client required for these other apps? The client installs libldap.so and liblber.so (plus variants based on OpenLDAP version and ABI version) -- like so for OpenLDAP 2.3: /usr/local/lib/liblber-2.3.so /usr/local/lib/liblber-2.3.so.2 /usr/local/lib/liblber.a /usr/local/lib/liblber.la /usr/local/lib/liblber.so /usr/local/lib/libldap-2.3.so /usr/local/lib/libldap-2.3.so.2 /usr/local/lib/libldap.a /usr/local/lib/libldap.la /usr/local/lib/libldap.so /usr/local/lib/libldap_r-2.3.so /usr/local/lib/libldap_r-2.3.so.2 /usr/local/lib/libldap_r.a /usr/local/lib/libldap_r.la /usr/local/lib/libldap_r.so (OpenLDAP 2.4 does similarly except replace '2.3' with '2.4') If you force uninstall openldap-client, then everything depending on it will refuse to run because of the unfulfilled shlib dynamic linkage. One of the programs that depends on the client is OpenLDAP-server -- so just by typing portinstall net/openldap23-server you'll cause openldap23-client (or openldap23-sasl-client) to be installed as a normal consequence of ports dependency resolution. The problem comes if you've already got, say, openldap23-client installed and you want openldap24-client -- other applications: Apache, PHP etc. will work with just about any LDAP version but openldap-server needs the matching client version. The solution is something like this: # portupgrade -o net/openldap24-client -f openldap-client-2.3.41 # portupgrade -fr openldap-client-2.4.8 to switch from the 23 series to the 24 series. Also -- handy tip -- adding flags like the following to /etc/make.conf will generally enable LDAP and SASL capabilities for any ports that can support them. (SASL highly recommended for securing access to LDAP, and also LDAP highly recommended as a back-end for SASL...) WITH_SASL= yes WITH_LDAP= yes WANT_OPENLDAP_VER= 23 WANT_OPENLDAP_SASL= yes However, don't insert the 'WANT_OPENLDAP_VER' line into /etc/make.conf until /after/ you've got the right openldap-client port installed, as it screws up switching between versions. 23 is the default stable release, 24 is also available but still in beta. So my question was if I install the server I'll get the client, and you're saying yes? If thats the case then, why is it stopping because the client is already installed? Actually, let me clarify: The error message I get is openldap-sasl-server-2.3.40 conflicts with installed package openldap-client-2.3.40, they install files into the same place. Therefore, I cannot install openldap server 2.3.40 And while I'm here... I tried installing the odbc backend, but it conflicts with other apps as well. How can I have both the libiodbc and unixodbc at the same time for openldap server (requires libiodbc), php5, etc? Do you really need the odbc *backend* for LDAP? That allows LDAP to store its data in a MSSQL database somewhere -- which implies the data store is on a different server to the OpenLDAP instance. That's not ideal for good performance. Unless you know you have a specific need for one of the particular back-ends and certainly if you are a beginner with openldap, I'd strongly recommend sticking with the default local storage based on Berkeley DB. Actually I thought it covered most sql servers not just mssql- if thats the case then good bye for sure. I was interested in maybe mysql though- this is not usable for that I take it? If your aim is to interoperate with ActiveDirectory then I believe that is possible at the LDAP level via the usual delegation and referral mechanisms. It may even be possible to replicate either to or from AD or to use OpenLDAP (+ Kerberos + Samba v4 I think) as a drop in replacement for AD. I have no direct knowledge of that, but I'm sure a little Google action will turn up any number of HowTos on the subject. Replacing a Windows server would be a nice goal... I will succeed on that one in the near future- just not this project. Thanks for the help. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openldap server install failure - openldap client conflict
On Wed, 2008-04-16 at 08:46 +0100, Matthew Seaman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Da Rock wrote: Actually, let me clarify: The error message I get is openldap-sasl-server-2.3.40 conflicts with installed package openldap-client-2.3.40, they install files into the same place. Therefore, I cannot install openldap server 2.3.40 Add WANT_SASL=yes to /etc/make.conf, then: portupgrade -f openldap-client-2.3.40 which will turn into openldap-sasl-client-2.3.40 once reinstalled. The install openldap-sasl-server-2.3.40. et voilà. Yeah, I kinda figured that out - it sometimes takes a while to get through my thick head... Thanks though. My concern is that I think I stuffed up something- I deinstalled openldap client and installed the server, which installed what it required. My worry is, even though I didn't have anything setup specifically for ldap support in the apps, will this affect them (sasl-ldap v ldap)? Or are they only using the libraries- not the config files? I'm probably just paranoid... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Openldap server install failure - openldap client conflict
I'm trying to install OpenLDAP as a server to attempt to try it out for our network. The problem is the openldap client is already installed for other apps as php, apache, asterisk, etc. So my question is: is it possible to uninstall the client? Will the server include the client required for these other apps? And while I'm here... I tried installing the odbc backend, but it conflicts with other apps as well. How can I have both the libiodbc and unixodbc at the same time for openldap server (requires libiodbc), php5, etc? Cheers ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE 4
Just a quick question: is there anything on the horizon with porting KDE 4? Cheers ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE 4
On Fri, 2008-03-21 at 18:10 -0700, Xin LI wrote: Da Rock wrote: Just a quick question: is there anything on the horizon with porting KDE 4? I think it was being tested/refining. More information can be found at http://freebsd.kde.org/ . Thanks for that. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
mod_webapp port broken
I'm tearing my hair out here- I'm having absolutely no luck with getting a calendar server and my latest sore point is the mod_webapp port which won't build because of missing includes. I ran a search but it appears that is only marked broken for certain archs, well I'm only running a poxy little pentium box - not 64bit processor. Here is my output: Building for mod_webapp-4.1.24_2 /bin/mkdir -p /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/build /bin/mkdir -p /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/build/objs /usr/bin/perl /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/support/scandoc.pl \ -i /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/support/template.pl \ -p /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/build/docs/api-c/ \ /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/*.h Reading /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h Reading /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_config.h parsing class wa_connection parsing class wa_virtualhost parsing class wa_application Reading /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_main.h parsing class wa_chain parsing class wa_provider Reading /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_request.h parsing class wa_hostdata parsing class wa_ssldata parsing class wa_handler parsing class wa_request Reading /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_version.h gmake[1]: Entering directory `/usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp' gmake[1]: Entering directory /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib gmake[2]: Entering directory `/usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib' /usr/local/build-1/libtool --silent --mode=compile \ cc -c /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c -o wa_main.lo \ -I. -I/usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include -I/usr/local/include/apache22 \ \ -O2 -fno-strict-aliasing -pipe In file included from /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:59: /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:77:25: apr_general.h: No such file or directory /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:78:23: apr_pools.h: No such file or directory /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:79:25: apr_strings.h: No such file or directory /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:80:24: apr_tables.h: No such file or directory /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:82:22: apr_time.h: No such file or directory /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:83:28: apr_network_io.h: No such file or directory /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:84:27: apr_file_info.h: No such file or directory In file included from /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:115, from /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:59: /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_main.h:141: error: syntax error before apr_pool_t /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_main.h:150: error: syntax error before apr_pool_t /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_main.h:232: error: syntax error before '*' token /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_main.h:232: warning: data definition has no type or storage class In file included from /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa.h:117, from /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:59: /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_request.h:114: error: syntax error before apr_pool_t /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/include/wa_request.h:146: error: syntax error before apr_table_t /usr/ports/www/mod_webapp/work/jakarta-tomcat-connectors-4.1.24-src/webapp/lib/wa_main.c:62: error: syntax error before
Caldav calendar server for freebsd
Hi guys. This may be old news, but I'm looking for a calendar server for freebsd. I've searched the ports but found nothing suitable (I'm having an issue with webcalendar which I've posted on their forums, plus I'm not sure it's what I'm after- keep reading to find out why), and I've trawled the net. I need some functions which are a must: 1. web accessible (duh :)) 2. evolution accessible 3. evolution postable 4. multi-user I have seen a few, but I'm not sure whether they will work on freebsd, and as I am using a production mc I'm a little hesitant to test this. It seems most caldav servers revolve around java, and the php davical is only made on debian (although being php it should work?). I'm considering building my own, but it appears that caldav is the way to go anyway. My only other alternative then is to figure out the evolution problem of posting to webcal's, in which case I'll go and bug the guys at gnome evolution :) (that and a whole bunch of other problems I'm working on- yay!) Cheers _ Your Future Starts Here. Dream it? Then be it! Find it at www.seek.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2F%3Ftracking%3Dsk%3Ahet%3Ask%3Anine%3A0%3Ahot%3Atext_t=764565661_r=OCT07_endtext_Future_m=EXT___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Totem and Ghostscript-gpl build failure
Hi all. I've done quite a bit of searching and head scratching for 2 days now, and I can't find an answer for this. I'm trying to build rhythmbox and gnome2-lite and both fail to build in ports. I've tried building gnome instead and it stops in totem. The error returned for totem is gnome-libtool: link: libtotem_player_la-totem-statusbar.lo is not a valid libtool object. The error for ghostscript is undefined reference errors in function opvp_to_utf8 to libiconv_close, resulting in an error code 1 for gmake and an error code 2 for the port build. Is there a fix or workaround for this? Or am I missing something? Thanks guys. _ Telstra’s Next GTM Network - now on Pre-Paid. Find out more. www.spreadthegoodstuff.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fclk%2Eatdmt%2Ecom%2FOAT%2Fgo%2Fnnmsnnxg008046oat%2Fdirect%2F01%2F_t=765565283_r=Telstra_FFF_Prepaid_Hotmail_Email_Taglines_JuySep07_Aug_m=EXT___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FW: seamonkey make error
Apologies- I didn't really give a lot of info in the subject field last time did I? From: Da Rock [EMAIL PROTECTED] To: freebsd-ports@freebsd.org Subject: seamonkey Date: Sat, 07 Apr 2007 03:13:16 + I may have missed this in my searches but I'm getting a stop error 1 2 when I make seamonkey. Its problem appears to be with nsSmtpProtocol.cpp - it fail @ 370 with a PR_SI_HOSTNAME_TRUNCATED undeclared. Any ideas on how I can get around this? Am I missing a port? Cheers Da Rock _ Advertisement: Its simple! Sell your car for just $30 at carsales.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801577%2Fpi%5F1005244%2Fai%5F838588_t=754951090_r=tig_m=EXT ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] _ Advertisement: Silverchair: Young Modern listen to full tracks plus win gig tickets! http://ninemsn.com.au/share/redir/adTrack.asp?mode=clickclientID=772referral=competitionpageURL=http://music.ninemsn.com.au/silverchair ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
seamonkey
I may have missed this in my searches but I'm getting a stop error 1 2 when I make seamonkey. Its problem appears to be with nsSmtpProtocol.cpp - it fail @ 370 with a PR_SI_HOSTNAME_TRUNCATED undeclared. Any ideas on how I can get around this? Am I missing a port? Cheers Da Rock _ Advertisement: Its simple! Sell your car for just $30 at carsales.com.au http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801577%2Fpi%5F1005244%2Fai%5F838588_t=754951090_r=tig_m=EXT ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
