Re: PHP 5.1.6 Command Line Arg Gives Seg Fault
Jeremy Chadwick wrote: Even if php is built without debug hooks, you should still get a stack trace with function names from gdb. Make sure everything builds with -g, and doesn't link with -s. :-) It turns out it's the module, not php itself. The behaviour is still strange, but at least it's not php doing it... I don't think. Thanks for all your helpful suggestions, Jeremy. -Ron T. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Please help
Hi, I've read your mail: Please Help (Thu Sep 4 06:26:55 PDT 2003 ) at http://lists.freebsd.org/pipermail/freebsd-ports/2003-September/004268.html About the complilation of Pysol 4.82 for winXP: Have you any news, please? I have the same problem. Thank you in advance Marco ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ODBC variables naming problems
Hi all, In databases/postgresql-odbc, the variable name for the ODBC flavour is 'DRIVER_MANAGER'. In net/openldap23-server, it is 'WITH_ODBC_TYPE'. Would it be possible to use uniform variable names between these ports ? Ganaël LAPLANCHE [EMAIL PROTECTED] http://www.martymac.com Tel : (+33)6.84.03.57.24. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ODBC variables naming problems
ganael.laplanche wrote: Hi all, In databases/postgresql-odbc, the variable name for the ODBC flavour is 'DRIVER_MANAGER'. In net/openldap23-server, it is 'WITH_ODBC_TYPE'. Would it be possible to use uniform variable names between these ports ? This might be a candidate for ports/KNOBS. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Samba and FAM
On Wed, 2006-Sep-13 11:42:06 -0500, Thomas T. Veldhouse wrote: >The catch 22 is that Courier-Imap attempts to use FAM even when it is >not configured to do so. So, I have to have FAM installed. I could get >it all working by deinstalling and reinstalling in the right order ... >until portmanager comes along and upgrades samba sometime in the future. I don't have the samba configure script to hand but if it's a typical GNU configure script, you should be able to specify something like '--without-fam' to stop samba looking for FAM. This would mean tweaking the FreeBSD Makefile but that's a lot easier than remembering to deinstall/reinstall various ports. -- Peter Jeremy pgpNf16p0QGNq.pgp Description: PGP signature
Re: Please help
Marco Merli wrote: > Hi, > I've read your mail: Please Help (Thu Sep 4 06:26:55 PDT 2003 ) > at http://lists.freebsd.org/pipermail/freebsd-ports/2003-September/004268.html > > About the complilation of Pysol 4.82 for winXP: Have you any news, please? > I have the same problem. > > Thank you in advance You can extract the stuff with popular archive managers like WinRAR, etc. I see nothing this do with freebsd-ports@, though. Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: ODBC variables naming problems
> > Would it be possible to use uniform variable names between these ports ? > > > This might be a candidate for ports/KNOBS. I think so... Could the porters handle this ? Best regards, Ganael. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: ipmi-kmod-20060418_1
Nick Barkas wrote: Thanks for your reply. I unfortunately do not have any Dell hardware to test with. We have a "spare" machine (it is a hot-backup of a production machine) I can test stuff on occasionally, if you got something specific. It looks like there have not been any significant changes to the IMPI code in - -CURRENT recently that might fix this, either. I do see a note in the "Fixes and Enhancements" section on the latest BIOS download page from Dell for the SC1425 that says "Added Native IPMI support," so they definitely did something. I managed to dig out the output from a working and non-working BIOS/IPMI: BIOS A02 (working): ipmi0: at iomem 0xfa840-0xfa85e,0xfa860-0xfb357 o n isa0 ipmi0: SMBIOS Version: 2.03, revision: 2.03 ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa ipmi0: IPMI device rev. 0, firmware rev. 1.81, version 1.5 ipmi0: Number of channels 4 ipmi0: Attached watchdog BIOS A03 (not working): ipmi0: at iomem 0xfa830-0xfa84e,0xfa850-0xfb356 o n isa0 ipmi0: SMBIOS Version: 2.03, revision: 2.03 ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa ipmi0: couldn't configure smbios io res I don't know if the IPMI-stuff actually moved or not in the BIOS, but the memory ranges differ. Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HEADS UP]: sdl port will be updated
* Stanislav Sedov ([EMAIL PROTECTED]) wrote: > We are going to update all sdl ports to latest version. > This will require modifications to sdl-dependent ports, > and we are currently doing full build in tinderbox > to ensure that all goes right. I.e. that will be include/SDL12, sdl12-config, etc.? Are there other changes besides version? I would like a patch to test my ports :) -- Best regards, Dmitry mailto:[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: Samba and FAM
On 9/14/06, Peter Jeremy <[EMAIL PROTECTED]> wrote: On Wed, 2006-Sep-13 11:42:06 -0500, Thomas T. Veldhouse wrote: >The catch 22 is that Courier-Imap attempts to use FAM even when it is >not configured to do so. So, I have to have FAM installed. I could get >it all working by deinstalling and reinstalling in the right order ... >until portmanager comes along and upgrades samba sometime in the future. I don't have the samba configure script to hand but if it's a typical GNU configure script, you should be able to specify something like '--without-fam' to stop samba looking for FAM. This would mean tweaking the FreeBSD Makefile but that's a lot easier than remembering to deinstall/reinstall various ports. I had a look at the configure script, and it doesn't have that option to exclude FAM when FAM is installed. Instead it will automatically add FAM support when it finds it. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HEADS UP]: sdl port will be updated
On Thu, 14 Sep 2006 16:35:51 +0400
Dmitry Marakasov <[EMAIL PROTECTED]> mentioned:
> * Stanislav Sedov ([EMAIL PROTECTED]) wrote:
> > We are going to update all sdl ports to latest version.
> > This will require modifications to sdl-dependent ports,
> > and we are currently doing full build in tinderbox
> > to ensure that all goes right.
> I.e. that will be include/SDL12, sdl12-config, etc.?
> Are there other changes besides version?
>
> I would like a patch to test my ports :)
>
No, it will resemble original distribution (include/SDL, sdl-config).
In any case you should not rely on this and always use bsd.sdl.mk
supplied variables(e.g. ${SDL_CONFIG}).
Your ports will be patches as well among other 375+. If you like to see,
the latest patch available here: http://mbsd.msk.ru/dist/sdl.diff.7
It's against yesterday cvs.
As kris said, we'll preform the update after 6.2 release, so don't
worry now. We'll ensure that there's no regression before commit.
--
Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]>
Россия, Москва http://mbsd.msk.ru
If the facts don't fit the theory, change the facts. -- A. Einstein
PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581
signature.asc
Description: PGP signature
R: Re: gtk-glade
The program "incollector" isn't in the ports but I'm trying to build a port (I'm a newbye port-builder!) from the original *nix sources. With your answer do you mean that gtk-glade is a linux library only OR did I misled you speaking of "linux documentation"? In other words that gtk- glade stuff is only available for linux? Ciao by a newbye Vittorio >Messaggio originale >Da: [EMAIL PROTECTED] >Data: 13-set- 2006 22.23 >A: >Ogg: Re: gtk-glade > >vittorio wrote: >> in the >> linux documentation of a program I'm trying to compile I read that it requires >> as dependency "gtk- glade". >> Therefore, being unable to find anything similar under >> freebsd, I installed libglade2 and glade2 but it seems to no avail. >> Any suggestion? >> What port(-s) should I install for that dependency? >> >> Ciao >> Vittorio > >Which program? > >Are you trying to install from ports? Your dependencies should be there >already. If it's something not in ports, maybe you're thinking: > >linux-libglade-0.17_1 and >linux-gtk-1.2.10_4 or >linux-gtk2-2.6.10 > >-- >B Briggs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HEADS UP]: sdl port will be updated
* Stanislav Sedov ([EMAIL PROTECTED]) wrote:
> > I.e. that will be include/SDL12, sdl12-config, etc.?
> > Are there other changes besides version?
> No, it will resemble original distribution (include/SDL, sdl-config).
> In any case you should not rely on this and always use bsd.sdl.mk
> supplied variables(e.g. ${SDL_CONFIG}).
At last! So cool :)
> Your ports will be patches as well among other 375+. If you like to see,
> the latest patch available here: http://mbsd.msk.ru/dist/sdl.diff.7
> It's against yesterday cvs.
>
> As kris said, we'll preform the update after 6.2 release, so don't
> worry now. We'll ensure that there's no regression before commit.
Yeah, as I see there was great amount of work done. Thank you!
--
Best regards,
Dmitry mailto:[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: R: Re: gtk-glade
Vittorio wrote: The program "incollector" isn't in the ports but I'm trying to build a port (I'm a newbye port-builder!) from the original *nix sources. With your answer do you mean that gtk-glade is a linux library only OR did I misled you speaking of "linux documentation"? In other words that gtk- glade stuff is only available for linux? Ciao by a newbye Vittorio Yes, I guess I misunderstood. Are you sure you're not talking about gtk-sharp-2? (/usr/ports/x11-toolkits/gtk-sharp20) The page I'm looking on says it also requires mono. http://www.incollector.devnull.pl/downloads.php -- B Briggs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: R: Re: gtk-glade
Right, I could have missed that depency but if I compile and install incollector "./configure;make;make check;make install" here what happens bash-2.05b$ incollector Unhandled Exception: System.ArgumentException: Cannot get resource file 'gui.glade' Parameter name: resource_name in <0x0018c> Glade.XML:.ctor (System. Reflection.Assembly assembly, System.String resource_name, System. String root, System.String domain) in <0x0002d> Glade.XML:FromAssembly (System.String resource_name, System.String root, System.String domain) in <0x0001b> Incollector.GUI.FirstStartDialog:.ctor () in <0x00208> Incollector.MainClass:Main (System.String[] args) Any idea? Ciao by this would-be-port-builder from Rome Vittorio Alle 16:39, giovedì 14 settembre 2006, B Briggs ha scritto: > Vittorio wrote: > > The program "incollector" isn't in the ports but I'm trying to build a > > port (I'm a newbye port-builder!) from the original *nix sources. > > With > > your answer do you mean that gtk-glade is a linux library only OR did I > > misled you speaking of "linux documentation"? In other words that gtk- > > glade stuff is only available for linux? > > > > Ciao by a newbye > > Vittorio > > Yes, I guess I misunderstood. Are you sure you're not talking about > gtk-sharp-2? (/usr/ports/x11-toolkits/gtk-sharp20) > > The page I'm looking on says it also requires mono. > http://www.incollector.devnull.pl/downloads.php ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: R: Re: gtk-glade
vittorio wrote: Right, I could have missed that depency but if I compile and install =20 incollector "./configure;make;make check;make install"=20 here what happens bash-2.05b$ incollector Unhandled Exception:=20 System.ArgumentException: Cannot get resource file 'gui.glade' Parameter name: resource_name in <0x0018c> Glade.XML:.ctor (System. Reflection.Assembly assembly, System.String resource_name, System. String root, System.String domain) in <0x0002d> Glade.XML:FromAssembly=20 (System.String resource_name, System.String root, System.String domain) in <0x0001b> Incollector.GUI.FirstStartDialog:.ctor () in <0x00208>=20 Incollector.MainClass:Main (System.String[] args) Any idea? Ciao by this would-be-port-builder from Rome Vittorio Alle 16:39, gioved=EC 14 settembre 2006, B Briggs ha scritto: Vittorio wrote: The program "incollector" isn't in the ports but I'm trying to build a port (I'm a newbye port-builder!) from the original *nix sources. With your answer do you mean that gtk-glade is a linux library only OR did I misled you speaking of "linux documentation"? In other words that gtk- glade stuff is only available for linux? Ciao by a newbye Vittorio Yes, I guess I misunderstood. Are you sure you're not talking about gtk-sharp-2? (/usr/ports/x11-toolkits/gtk-sharp20) The page I'm looking on says it also requires mono. http://www.incollector.devnull.pl/downloads.php ___ Looks to me like you have all of your dependencies, this is a runtime error, or possibly gui.glade not being installed. A quick google revealed this: http://bugzilla.ximian.com/show_bug.cgi?id=78040 I don't know enough about C#, mono, glade, or gtk# to help you, and I don't want to install all of the dependencies, but here's what I found. Look in src/GUI/MainWindow.cs (search gui.glade). If gui.glade is not being installed, it can be found in resources/gui.glade. Maybe it is installed, but under a different name. Personally, I would try a mono group for further help if nobody else here knows the solution. -- B Briggs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: fpc-fcl-2.0.4
The dependency of FCL in ports on mysql and other databases is wrong. You don't need mysql or others installed for FCL to "work". There are many units in the FCL but most of them are stand-alone header translations. Imagine that when you install java, you'd have to install all possible databases and libs it has interface to.. that's just not right. FCL is also a collection of pure fpc libs like containers required to compile alot of projects/programs which DON'T need any of the databases or other external libs. Please remove the dependency in the port and possibly add a warning to the user that if they want to use external libs from fpc they need to install them. Ales Katona ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: php5-5.1.6
Hi. I'm having some problems with php5 port. I have two machines with standard php5-extensions (from ports) install... And I'm unable to install Zend Platform in both. I have asked about it in ZP forum. http://www.zend.com/forums/index.php? t=msg&th=1874&start=0&S=fa23716a1b184ffc12ffb9875428bdca And I got this answer: "You have "--enable-versioning" in your PHP setup. This flag is not compatible with Zend extensions. You need to recompile without this flag - and then try again." I have tried to remove --enable-versioning from MakeFile in ports/lang/php5 and recompile it. # Step 1: cd /usr/ports/lang/php5 make deinstall make clean make fetch # Step 2: edit MakeFile (removed "--enable-versioning") # Step 3: make ... stopped here ... But it doesn't work: ===> Building for php5-5.1.6 /bin/sh /usr/ports/lang/php5/work/php-5.1.6/libtool --silent --preserve- dup-deps --mode=compile cc -Iext/date/lib -Iext/date/ - I/usr/ports/lang/php5/work/php-5.1.6/ext/date/ -DPHP_ATOM_INC - I/usr/ports/lang/php5/work/php-5.1.6/include - I/usr/ports/lang/php5/work/php-5.1.6/main -I/usr/ports/lang/php5/work/php- 5.1.6 -I/usr/local/include/libxml2 -I/usr/local/include - I/usr/ports/lang/php5/work/php-5.1.6/ext/date/lib - I/usr/ports/lang/php5/work/php-5.1.6/TSRM -I/usr/ports/lang/php5/work/php- 5.1.6/Zend-O2 -fno-strict-aliasing -pipe -prefer-non-pic - c /usr/ports/lang/php5/work/php-5.1.6/ext/date/lib/parse_date.c -o ext/date/lib/parse_date.lo cc: Internal error: Killed: 9 (program cc1) Please submit a full bug report. See http://gcc.gnu.org/bugs.html> for instructions. *** Error code 1 Stop in /usr/ports/lang/php5/work/php-5.1.6. *** Error code 1 Stop in /usr/ports/lang/php5. - In fact, I have Zend Optimizer instaled and working fine in one of theses machine. Only Zend Platform does not work. Do you have some patch, or a way to install Zend Platform in php5 port? Or a way to remove --enable-versioning from configure? I'm waiting for a solution... Thank's Rafael Henrique Faria University of São Paulo - Brazil ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mgetty broken
Hi all, mgetty is currently marked as broken due to incomplete pkg-plist. Just checking to see if this might be corrected in time for 6.2. Thanks Pat ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mgetty broken
On Thu, Sep 14, 2006 at 05:44:27PM -0500, Patrick Reich wrote: > > Hi all, > > mgetty is currently marked as broken due to incomplete > pkg-plist. Just checking to see if this might be > corrected in time for 6.2. I hope so :) The maintainer didn't respond yet though - so perhaps someone else can fix it. Kris pgpiBbkSx2Iba.pgp Description: PGP signature
Re: FreeBSD Port: php5-5.1.6
[EMAIL PROTECTED] wrote: > Hi. > > I'm having some problems with php5 port. > > I have two machines with standard php5-extensions (from ports) install... > And I'm unable to install Zend Platform in both. > > I have asked about it in ZP forum. > http://www.zend.com/forums/index.php? > t=msg&th=1874&start=0&S=fa23716a1b184ffc12ffb9875428bdca > > And I got this answer: "You have "--enable-versioning" in your PHP setup. > This flag is not compatible with Zend extensions. You need to recompile > without this flag - and then try again." > > I have tried to remove --enable-versioning from MakeFile in > ports/lang/php5 and recompile it. > > # Step 1: > cd /usr/ports/lang/php5 > make deinstall > make clean > make fetch > > # Step 2: > edit MakeFile > (removed "--enable-versioning") > > # Step 3: > make > ... stopped here ... > > But it doesn't work: > > ===> Building for php5-5.1.6 > /bin/sh /usr/ports/lang/php5/work/php-5.1.6/libtool --silent --preserve- > dup-deps --mode=compile cc -Iext/date/lib -Iext/date/ - > I/usr/ports/lang/php5/work/php-5.1.6/ext/date/ -DPHP_ATOM_INC - > I/usr/ports/lang/php5/work/php-5.1.6/include - > I/usr/ports/lang/php5/work/php-5.1.6/main -I/usr/ports/lang/php5/work/php- > 5.1.6 -I/usr/local/include/libxml2 -I/usr/local/include - > I/usr/ports/lang/php5/work/php-5.1.6/ext/date/lib - > I/usr/ports/lang/php5/work/php-5.1.6/TSRM -I/usr/ports/lang/php5/work/php- > 5.1.6/Zend-O2 -fno-strict-aliasing -pipe -prefer-non-pic - > c /usr/ports/lang/php5/work/php-5.1.6/ext/date/lib/parse_date.c -o > ext/date/lib/parse_date.lo > cc: Internal error: Killed: 9 (program cc1) > Please submit a full bug report. > See http://gcc.gnu.org/bugs.html> for instructions. > *** Error code 1 > > Stop in /usr/ports/lang/php5/work/php-5.1.6. > *** Error code 1 > > Stop in /usr/ports/lang/php5. > > - > In fact, I have Zend Optimizer instaled and working fine in one of theses > machine. Only Zend Platform does not work. > > Do you have some patch, or a way to install Zend Platform in php5 port? Or > a way to remove --enable-versioning from configure? This looks strange. What did "dmesg" say? Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: FreeBSD Port: ipmi-kmod-20060418_1
I believe our 2950 is BIOS Rev. A03 as well, I'll reboot it tomorrow if I have a chance and get the Dell version ID. dmesg-wise, my first iomem range is the same as for A02, but my second is not. I'm leaning toward the explanation that Dell moved something on us and done went and broke the module :-/ ipmi0: at iomem 0xfd040-0xfd05e, 0xcffbc000-0xcffbcc3a on isa0 ipmi0: SMBIOS Version: 2.04, revision: 2.04 ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa ipmi0: couldn't configure smbios io res In case it proves helpful -MG On Sep 14, 2006, at 7:28 AM, J. Martin Petersen wrote: Nick Barkas wrote: Thanks for your reply. I unfortunately do not have any Dell hardware to test with. We have a "spare" machine (it is a hot-backup of a production machine) I can test stuff on occasionally, if you got something specific. It looks like there have not been any significant changes to the IMPI code in - -CURRENT recently that might fix this, either. I do see a note in the "Fixes and Enhancements" section on the latest BIOS download page from Dell for the SC1425 that says "Added Native IPMI support," so they definitely did something. I managed to dig out the output from a working and non-working BIOS/ IPMI: BIOS A02 (working): ipmi0: at iomem 0xfa840-0xfa85e, 0xfa860-0xfb357 o n isa0 ipmi0: SMBIOS Version: 2.03, revision: 2.03 ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa ipmi0: IPMI device rev. 0, firmware rev. 1.81, version 1.5 ipmi0: Number of channels 4 ipmi0: Attached watchdog BIOS A03 (not working): ipmi0: at iomem 0xfa830-0xfa84e, 0xfa850-0xfb356 o n isa0 ipmi0: SMBIOS Version: 2.03, revision: 2.03 ipmi0: KCS mode found at io 0xca8 alignment 0x4 on isa ipmi0: couldn't configure smbios io res I don't know if the IPMI-stuff actually moved or not in the BIOS, but the memory ranges differ. Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Port Makefiles and the MANPREFIX macro
Hi all,
Currently doing battle with some port updates and I have come across a
strange problem. It's probably my fault, but some guidance would be
appreciated.
Three of the ports I maintain have decided that the man pages belong in
${PREFIX}/share/man/man(n). Now, reading the Porter's Handbook, it appears
this is exactly what the MAN[n]PREFIX macro is for, and sure enough after
removing the man page from pkg-plist and telling the Makefile about it, the
ports system compresses the resultant man page in its new location. So far so
good.
However, on deinstall, if appeand two lots of ${PREFIX} when trying to remove
the man page. For example, grig installs a man page
to /usr/local/share/man/man1/grig.1 (for a ${PREFIX} of /usr/local). The
deinstall routine trys to delete grig.1.gz
from /usr/local/share//usr/local/share/man/man1, which is just a little
crazy. Note the two slashes between the two iterations of the MANPREFIX.
Any clues, folks? I'd like to get these updates in before the ports tree is
frozen for 6.2 if at all possible.
--
Matt Dawson.
[EMAIL PROTECTED]
MTD15-RIPE OpenNIC M_D9
MD51-6BONE
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Port Makefiles and the MANPREFIX macro
On Fri, Sep 15, 2006 at 07:22:15AM +0100, Matt Dawson wrote:
> Hi all,
> Currently doing battle with some port updates and I have come across a
> strange problem. It's probably my fault, but some guidance would be
> appreciated.
>
> Three of the ports I maintain have decided that the man pages belong in
> ${PREFIX}/share/man/man(n). Now, reading the Porter's Handbook, it appears
> this is exactly what the MAN[n]PREFIX macro is for, and sure enough after
> removing the man page from pkg-plist and telling the Makefile about it, the
> ports system compresses the resultant man page in its new location. So far so
> good.
>
> However, on deinstall, if appeand two lots of ${PREFIX} when trying to remove
> the man page. For example, grig installs a man page
> to /usr/local/share/man/man1/grig.1 (for a ${PREFIX} of /usr/local). The
> deinstall routine trys to delete grig.1.gz
> from /usr/local/share//usr/local/share/man/man1, which is just a little
> crazy. Note the two slashes between the two iterations of the MANPREFIX.
>
> Any clues, folks? I'd like to get these updates in before the ports tree is
> frozen for 6.2 if at all possible.
Don't include MANPREFIX=${PREFIX}... since it's apparently being used
as ${PREFIX}${MANPREFIX}; you could confirm this by reading
bsd.port.mk.
Kris
pgpGIUiFJVrpb.pgp
Description: PGP signature
Re: Port Makefiles and the MANPREFIX macro
On Fri, Sep 15, 2006 at 02:25:14AM -0400, Kris Kennaway wrote:
> On Fri, Sep 15, 2006 at 07:22:15AM +0100, Matt Dawson wrote:
> > Hi all,
> > Currently doing battle with some port updates and I have come across a
> > strange problem. It's probably my fault, but some guidance would be
> > appreciated.
> >
> > Three of the ports I maintain have decided that the man pages belong in
> > ${PREFIX}/share/man/man(n). Now, reading the Porter's Handbook, it appears
> > this is exactly what the MAN[n]PREFIX macro is for, and sure enough after
> > removing the man page from pkg-plist and telling the Makefile about it, the
> > ports system compresses the resultant man page in its new location. So far
> > so
> > good.
> >
> > However, on deinstall, if appeand two lots of ${PREFIX} when trying to
> > remove
> > the man page. For example, grig installs a man page
> > to /usr/local/share/man/man1/grig.1 (for a ${PREFIX} of /usr/local). The
> > deinstall routine trys to delete grig.1.gz
> > from /usr/local/share//usr/local/share/man/man1, which is just a little
> > crazy. Note the two slashes between the two iterations of the MANPREFIX.
> >
> > Any clues, folks? I'd like to get these updates in before the ports tree is
> > frozen for 6.2 if at all possible.
>
> Don't include MANPREFIX=${PREFIX}... since it's apparently being used
> as ${PREFIX}${MANPREFIX}; you could confirm this by reading
> bsd.port.mk.
Actually this appears to be incorrect, I'm not sure what is the cause.
Kris
pgpY2BjlMxU0q.pgp
Description: PGP signature
Re: Port Makefiles and the MANPREFIX macro
On Fri, 15 Sep 2006 07:22:15 +0100
Matt Dawson <[EMAIL PROTECTED]> mentioned:
> Hi all,
> Currently doing battle with some port updates and I have come across a
> strange problem. It's probably my fault, but some guidance would be
> appreciated.
>
It's probably happened because of recent autoconf 2.60 changed it's
manpage and info locations to share/man and share/info accordingly.
It can be solved by adding --mandir=${PREFIX}/man and --infodir=
${PREFIX}/info to CONFIGURE_ARGS.
I have submitted a change to bsd.port.mk to add this as default
since it will not break existing ports (for autoconf prior to 2.60
this is default), but, unfortunately, this proposal didn't find support.
In fact, many people have faced to this problem recently (on irc/mailing
lists).
--
Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]>
Россия, Москва http://mbsd.msk.ru
If the facts don't fit the theory, change the facts. -- A. Einstein
PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581
signature.asc
Description: PGP signature
