Re: Port Request: Bongo
On Sat, 7 Nov 2009 04:27:45 +0300 Eygene Ryabinkin rea-f...@codelabs.ru wrote: Fri, Nov 06, 2009 at 06:44:59PM +0100, Georges Discry wrote: In fact, I started a port but hit some problems with CMake. It's having problems locating the libraries and include files of libical and openldap. Attached is the preliminary version of the port, they are packed with shar(1). Attachment stripped. How about a URL? --- Gary Jennejohn ___ 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 Request: Bongo
Sat, Nov 07, 2009 at 04:27:44AM +0300, Eygene Ryabinkin wrote:
I hadn't tested it in the Tinderbox for the clean build, but I'll
try to do it next week. If you're interested -- I'll post the
results and modifications to the port.
Some iterations over the Tinderbox helped to bring the port to the
much better shape and now it gained some more dependencies, plist
was fixed and some patches were updated.
Sat, Nov 07, 2009 at 11:31:41AM +0100, Gary Jennejohn wrote:
Attachment stripped. How about a URL?
http://codelabs.ru/fbsd/ports/bongo-0.6.1.shar
It contains the latest version with all fixes embedded. Still, I
hadn't tested if it really works :((
--
Eygene
____ _.--. #
\`.|\.....-'` `-._.-'_.-'` # Remember that it is hard
/ ' ` , __.--' # to read the on-line manual
)/' _/ \ `-_, /# while single-stepping the kernel.
`-' `\_ ,_.-;_.-\_ ', fsc/as #
_.-'_./ {_.' ; / #-- FreeBSD Developers handbook
{_.-``-' {_/#
___
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: php5-5.2.11_1 upgrade path to 5.3.0/1
Doug Barton wrote: Miroslav Lachman wrote: Even if there are just a few incompatibilities, it means some clients applications on webhosting will stop working and clients will scream on helpline right after the update of the servers PHP... Sounds like you're familiar with the problems, why don't you volunteer to maintain the 5.2.x set of ports after a fork? Now both problems are solved. :) I expected this answer :) And my answer is - I can try it. PHP with all extensions is not the simplest way to start learning port maintaining, but I can try it. The question is - are there committers willing to commit it or is it something against some people opinion / against some rules? (changes in Mk/bsd.php.mk will be needed) And yes, I'm serious, assuming that there will be updates in the 5.2.x series that users will need. If not, simply not updating their existing ports is a reasonable solution. It can be useful even if there will be no more updates - in case somebody need to install new machine in to farm with older versions. [until there will be next security hole in PHP 5.2 :)] Seriously - if ports team is willing to have legacy versions in ports, we need to discuss some rules for this work. Not just for PHP, but more general. In which conditions we need/allow them, the naming conventions (some ports already have more versions but names are not consistent, some ports are using -dev, -devel, -current [3 different sufixes for the development branch], Perl always uses p5- prefix, Python have py25-, py26- etc.) So is it better to renumber the legacy (forked) version to php52-ext_name-5.2.12 leaving php5- line for 5.3 version or do it like Python (py25, py26): php52- and php53-. And wouldn't it be better to have for example PHP 5.3 in devel state in ports for some evaluation period - earlier before PHP 5.3 will be given as new 5.x main line so more people can test it even with limited features, web developers can write/test own apps for PHP 5.3 etc.? Availability of the devel version will give possibility to those that want to play with new features accepting the risk and lighten the pressure on maintainers to commit the new version to the main line. Again - I can try to do the php52 port if it have sense. Miroslav Lachman ___ 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
Are we in ports freeze?
I may have missed the announcement. Robert Huff ___ 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: Are we in ports freeze?
As an experiment, we never had a 'hard freeze' this release. We're still in a mode where we are asking for no sweeping changes to be committed until 8.0 is out the door, in case we have to do tag slips and rebuilds to catch up with security problems. mcl ___ 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
ports devel/pear
I'm having a very difficult time installing the php pear port. and pkd-add only installs pear-1.7 Could someone either build/compile 1.9 for the postinstall packages for FreeBSD 6.2 or fix the port for pear on FreeBSD 6.2? portinstall devel/pear [Gathering depends for devel/pear done] --- Installing 'pear-1.9.0' from a port (devel/pear) --- Building '/usr/ports/devel/pear' === Cleaning for pear-1.9.0 === Extracting for pear-1.9.0 = MD5 Checksum OK for pear-1.9.0.tar.bz2. = SHA256 Checksum OK for pear-1.9.0.tar.bz2. === Patching for pear-1.9.0 === Applying FreeBSD patches for pear-1.9.0 === Configuring for pear-1.9.0 --- Installing the new version via the port === Installing for pear-1.9.0 === pear-1.9.0 depends on file: /usr/local/include/php/main/php.h - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/pcre.so - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/xml.so - found === Generating temporary packing list === Checking if devel/pear already installed PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20060613/memcache.so' - /usr/local/lib/php/20060613/memcache.so: Undefined symbol php_session_create_id in Unknown on line 0 Bootstrapping Installer... Using previously install ... ok Extracting installer.. Using previously installed installer ... ok Preparing installer.. Updating channel doc.php.net Channel doc.php.net is up to date Updating channel pear.php.net Channel pear.php.net is up to date Updating channel pecl.php.net Channel pecl.php.net is up to date Installing selected packages.. Package: PEAR-stable.. already installed ... ok Package: Structures_Graph-stable.. already installed ... ok Package: Archive_Tar-stable... already installed ... ok Package: Console_Getopt-stable already installed ... ok *** Signal 11 Stop in /usr/ports/devel/pear. *** Error code 1 Stop in /usr/ports/devel/pear. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall20091107-64767-1rrb3k5-0 env make reinstall ** Fix the installation problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! devel/pear(install error) ___ 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
aalib issue
When I call aclocal command, I get warning about syntax in aalib.m4 file. In attachment I'am sending patch which is fixing this issue. patch-aalib.m4 Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: ports devel/pear
Agrapha wrote: I'm having a very difficult time installing the php pear port. and pkd-add only installs pear-1.7 Could someone either build/compile 1.9 for the postinstall packages for FreeBSD 6.2 or fix the port for pear on FreeBSD 6.2? portinstall devel/pear [Gathering depends for devel/pear done] --- Installing 'pear-1.9.0' from a port (devel/pear) --- Building '/usr/ports/devel/pear' === Cleaning for pear-1.9.0 === Extracting for pear-1.9.0 = MD5 Checksum OK for pear-1.9.0.tar.bz2. = SHA256 Checksum OK for pear-1.9.0.tar.bz2. === Patching for pear-1.9.0 === Applying FreeBSD patches for pear-1.9.0 === Configuring for pear-1.9.0 --- Installing the new version via the port === Installing for pear-1.9.0 === pear-1.9.0 depends on file: /usr/local/include/php/main/php.h - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/pcre.so - found === pear-1.9.0 depends on file: /usr/local/lib/php/20060613/xml.so - found === Generating temporary packing list === Checking if devel/pear already installed PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20060613/memcache.so' - /usr/local/lib/php/20060613/memcache.so: Undefined symbol php_session_create_id in Unknown on line 0 [...] It seems you have problem with your current PHP installation, not only with PEAR. Do you have memcache extension installed? If not, do you have it listed in the /usr/local/etc/php/extensions.ini or php.ini? Try to commented out or reinstall your PHP and extensions. Miroslav Lachman ___ 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: bugzilla-3.4.2 needs updated to bugzilla-3.4.3
On Fri, 06 Nov 2009, Jared Barneck wrote: Bugzilla 3.4.3 is out. Indeed it is. [...] Not sure if pkg-plist needs updating. It does. See ports/140327 which was filed on Fri Nov 06 03:40:01 UTC. Give skv@ a few days to review, revise and commit. :) -- Sahil Tandon sa...@tandon.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: FreeBSD Port: openssl-0.9.8k_5
On Fri, 06 Nov 2009, Frank de Bot wrote: I like to know if there are plans to update this port to 0.9.8l. It's an update to solve CVE-2009-3555 % cvs log -r1.55 security/openssl/distinfo | tail -n 5 revision 1.55 date: 2009/11/06 20:09:49; author: dinoex; state: Exp; lines: +3 -3 - Security update to 0.9.8l Security: CVE-2009-3555 = -- Sahil Tandon sa...@tandon.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
Now OK (Re: cvs commit: ports/devel/rudiments Makefile ports/devel/rudiments/files patch-Makefile)
devel/rudiments, which was previously failing is OK after this commit. Thanks for fixing it! A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - HMC and EOI? - Halt, Melt and Catch fire or Execute Operator Immediately. ___ 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
trouble porting dash shell (make errors)
I tried the dash mailing list with no reply. mksignames.c is attached. Here is the output from ./configure gmake if gcc -DHAVE_CONFIG_H -I. -I. -I.. -include ../config.h -DBSD=1 -DSHELL -DIFS_BROKEN -Wall -g -O2 -MT nodes.o -MD -MP -MF .deps/nodes.Tpo -c -o nodes.o nodes.c; \ then mv -f .deps/nodes.Tpo .deps/nodes.Po; else rm -f .deps/nodes.Tpo; exit 1; fi gcc -include ../config.h -DBSD=1 -DSHELL -DIFS_BROKEN -g -O2 -Wall -o mksignames mksignames.c ./mksignames gmake[3]: *** [signames.c] Segmentation fault: 11 (core dumped) gmake[3]: *** Deleting file `signames.c' gmake[3]: Leaving directory `/home/eitan/dash/dash-0.5.5.1/src' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/home/eitan/dash/dash-0.5.5.1/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/home/eitan/dash/dash-0.5.5.1' gmake: *** [all] Error 2 mksignames.c Description: Binary data ___ 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-f8-pango - fix or replacement?
Hi, I am using the linux-f8 ports on FreeBSD 7.2-stable (mainly to get linux-flashplugin to work). However linux-f8-pango have an open security issue (and have had for some time now). There is no update of linux-f8-pango (not yet anyway) in the ports tree. Can I replace it with something else? (but without changing all ports to linux-f10) -- Regards, Torfinn Ingolfsen ___ 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: semi OT: CUPS and printservers
Hi, On Sat, Nov 7, 2009 at 2:59 PM, Robert Huff roberth...@rcn.com wrote: Is anyone out there using CUPS with a printserver? I have a Netgear PS-100, but any success story will probably help. It works fine with Windows XP, but I can't find the magic formula to get it working with CUPS. Well, according to chapter 5 (UNIX Printing using TCP/IP) in the PS-100 reference manual, this printerserver understands (amongst other) the LPD protocol. The CUPS documentation have a description for LPD: http://www.cups.org/doc-1.4/network.html#LPD The PS-100 also supports DSI, sp you can use: socket://*address*:4010 socket://*address*:4020 socket://*address*:4030 For the three logical printers it supports inthat mode. HTH -- Regards, Torfinn Ingolfsen ___ 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: audio/py-tagpy broken
Nicola Vitale wrote: Hi Dominic, [2009/11/5 Dominic Fandrey kamik...@bsdforen.de] Whatever kind of information you require, I'm willing to provide. Sorry, your build failed. Try rerunning configure.py with different options. Traceback (most recent call last): File setup.py, line 114, in module main() File setup.py, line 105, in main extra_compile_args=conf[CXXFLAGS], It's strange, I have compiled it on my system and built in tinderbox too (http://people.freebsd.org/~nivit/tb_logs/py26-tagpy-0.94.7.log ), and there were not errors. I'll check on an AMD64 system, thanks for the report. Ciao. I have found the strangest workaround, after the failure I just have to cd into the working directory, run make without parameters and it finishes building. It's only from the port that building doesn't work. I quickly found out that something in MAKE_ENV must be causing it, so I tried compiling repeatedly, each time stripping another variable and discovered that CXX causes my problem. If I leave it out of the MAKE_ENV it builds just fine. Considering that CXX is not even used this strikes me as quite strange and I know of no non-hacky way of removing it from MAKE_ENV. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: semi OT: CUPS and printservers
Torfinn Ingolfsen writes: Is anyone out there using CUPS with a printserver? I have a Netgear PS-100, but any success story will probably help. It works fine with Windows XP, but I can't find the magic formula to get it working with CUPS. Well, according to chapter 5 (UNIX Printing using TCP/IP) in the PS-100 reference manual, this printerserver understands (amongst other) the LPD protocol. The CUPS documentation have a description for LPD: http://www.cups.org/doc-1.4/network.html#LPD The PS-100 also supports DSI, sp you can use: socket://*address*:4010 socket://*address*:4020 socket://*address*:4030 For the three logical printers it supports inthat mode. socket://ip addr worked fine. Thanks immensely. Robert Huff ___ 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
Improving Ada support on FreeBSD and in the ports system
[Apologies for the possible double-post, I mistyped the From: address] Hello. It's come to my attention that the FreeBSD ports system has very poor support for Ada and Ada software in general. A quick search on Freshports for 'Ada' shows the following packages: devel/adabooch- No dependencies registered! devel/adacurses - lang/gnat devel/adasdl - lang/gnat net/adasockets- lang/gnat (broken) textproc/xmlada - lang/gnat-gcc41 (broken) textproc/xmlada-gps - lang/gnat (broken) x11-toolkits/gtkada - lang/gnat (broken) x11-toolkits/gtkada-devel - lang/gnat (broken) x11-toolkits/gtkada-gcc - lang/gnat-gcc41 (broken) x11-toolkits/gtkada-gps - lang/gnat (broken) I'm aware there are more packages than this in the ports sytem. The situation doesn't get any better the more you read... The problems any user of Ada on FreeBSD faces are: PROBLEM 1. Lack of packages (as shown above) Of the 10 packages listed, only three of those (maybe two) actually work. PROBLEM 2. No choice in the use of compiler The Ada world is essentially divided between the GCC version of GNAT that can produce executables not tainted by the GPL (GNAT-FSF) and the GPL version (GNAT-GPL) from AdaCore which can't. Debian, for example, only uses GNAT-FSF (but one can, of course, just download GNAT-GPL from AdaCore and use it without issue). PROBLEM 3. Compiler version chaos and lack of architecture support We have: lang/gnat (GPL 2009 version, i386 only) lang/gnat-gcc41 (GCC 4.1, i386 only) lang/gnat-gcc42 (GCC 4.2, i386 only) lang/gnat-gcc43 (GCC 4.3, i386 only) lang/gnat-gcc44 (GCC 4.4, i386 and amd64) Apart from the fact that nobody using Ada knows which one of the above five ports they want, they'll also be forced into using at least one of them due to lack of architecture support and ports unconditionally depending on lang/gnat. Debian, for example, has a wide range of compiler architectures available for GNAT: http://packages.debian.org/unstable/devel/gnat Anybody that wants to install Ada packages from ports on AMD64 is stuck. Despite having an AMD64 compiler (gnat-gcc44) in ports, packages will demand lang/gnat and will then fail due to ONLY_FOR_ARCHS=i386. PROBLEM 4. Lack of a debugger We currently only have gdb 6.1.1 in the base system and I've never been able to get any of the other gdb ports to compile (version = 6.8 of gdb have explicit Ada support). PROBLEM 5. Lack of a consistent policy for Ada packages Debian, for example, has this: http://people.debian.org/~lbrenta/debian-ada-policy.html I would like to (attempt to) solve all of the above problems and make FreeBSD a serious platform for Ada development. I will attempt to address the five points above with possible solutions to each. PROBLEM 1. Lack of packages This is something I will work on personally. I have quite a large number of packages I have developed myself to be submitted to ports but have been unable until now due to the problems described above. I am also willing to spend time porting the big name packages such as GtkAda and AWS to FreeBSD (porting Ada programs tends to be quite painless, usually). PROBLEM 2. No choice in the use of compiler PROBLEM 3. Compiler version chaos and lack of architecture support I believe there needs to be a mechanism to select an Ada compiler for use with packages. I'm not sure what the Ports system currently provides for this case. I do not want to force a particular compiler choice on the users of packages. Some packages (currently) require GNAT GPL to function (any program using ASIS[1] currently needs an extra support library[2] to work with GNAT FSF). The setting should probably be a port option that can be set in make.conf. I would be interested to hear ideas on this. I would like to see the number of GNAT ports brought down to two - one for GNAT-FSF and one for GNAT-GPL. This would require input from the maintainers of the older gnat-gcc ports and a coordinated effort to make sure the small selection of packages available work with both of the resulting ports (before adding new packages). Lack of architecture support is a time-consuming issue. Both GCC and GNAT have support for a wide range of architectures but GNAT only has support for FreeBSD i386 (and now AMD64 in trunk). I have produced bootstrap binaries for GCC 4.4 on i386 and AMD64 on FreeBSD 7.2 (and will produce binaries for 8.0 when it arrives) but do not have access to any other architectures running FreeBSD. This is more or less an issue of manpower and patience. PROBLEM 4. Lack of a debugger This should not be a major problem to solve. Presumably the
Issues with devel/boost-* on Sparc64
HI folks! As I know, currently devel/boost-libs port fails to build on sparc64. I had a discussion of this in September. The root cause is unknown for me. To investigate into this further I need either access to a sparc64 box or a person who has access and whom I may instruct with the actions to perform. Are there any plans to fix ports for sparc64 before the release? Sincerely, Alexander Churanov, maintainer of devel/boost-* ___ 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
How to fix fetching from sourceforge.org? [ devel/boost-* ]
Hi folks! I've noticed that my ports are unable to fetch from sourceforge and usually fetch from FreeBSD sites. I recall there was a discussion on this, but I've missed the final statement. Was the solution proposed? If yes, please point me to it, to let me fix my ports. Alexander Churanov, maintainer of devel/boost-* ___ 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: Issues with devel/boost-* on Sparc64
Alexander Churanov wrote: HI folks! As I know, currently devel/boost-libs port fails to build on sparc64. I had a discussion of this in September. The root cause is unknown for me. To investigate into this further I need either access to a sparc64 box or a person who has access and whom I may instruct with the actions to perform. Are there any plans to fix ports for sparc64 before the release? Sincerely, Alexander Churanov, maintainer of devel/boost-* ___ 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 Ahoy. I can give you shell access to a reasonably-speedy sparc64 machine (4 x 300 MHz) running 8.0-BETA. -Boris ___ 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: How to fix fetching from sourceforge.org? [ devel/boost-* ]
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
I've noticed that my ports are unable to fetch from sourceforge and
usually fetch from FreeBSD sites.
boost-* fetches just fine for me.
I recall there was a discussion on this, but I've missed the final
statement.
After SF updated their distribution scheme, there was change to sites.mk
and all ports hosted on SF.
Nothing more than correct MASTER_SITES is required. If your port doesn't
fetch, try `make fetch-urlall-list` and then try when on one of the
URLs - there should be no redirects or index.html's. If there are,
just go to SF download page, get the download url and give it to
wget again. There will be bunch of redirects and finally direct URL
which may be used in MASTER_SITES.
For example, if you're playing with boost 1.41 beta 1:
http://sourceforge.net/projects/boost/files/boost/1.41.0.beta.1/boost_1_41_0_beta1.tar.bz2/download
(from download page)
V
http://downloads.sourceforge.net/project/boost/boost/1.41.0.beta.1/boost_1_41_0_beta1.tar.bz2
(redirect)
V
http://sunet.dl.sourceforge.net/project/boost/boost/1.41.0.beta.1/boost_1_41_0_beta1.tar.bz2
(finally, direct link)
^
That's SF/boost/boost/1.41.0.beta.1, or
SF/boost/boost/${DISTVERSION:C/something/} if you like.
If you use firefox, you may be interested in this GreaseMonkey script,
which converts download URLs on SF to direct ones:
http://userscripts.org/scripts/show/50136
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru
___
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: Improving Ada support on FreeBSD and in the ports system
On Sat, 7 Nov 2009, freebsd-po...@coreland.ath.cx wrote: [Apologies for the possible double-post, I mistyped the From: address] Hello. It's come to my attention that the FreeBSD ports system has very poor support for Ada and Ada software in general. A quick search on Freshports for 'Ada' shows the following packages: devel/adabooch- No dependencies registered! devel/adacurses - lang/gnat devel/adasdl - lang/gnat net/adasockets- lang/gnat (broken) textproc/xmlada - lang/gnat-gcc41 (broken) textproc/xmlada-gps - lang/gnat (broken) x11-toolkits/gtkada - lang/gnat (broken) x11-toolkits/gtkada-devel - lang/gnat (broken) x11-toolkits/gtkada-gcc - lang/gnat-gcc41 (broken) x11-toolkits/gtkada-gps - lang/gnat (broken) I'm aware there are more packages than this in the ports sytem. The situation doesn't get any better the more you read... The problems any user of Ada on FreeBSD faces are: PROBLEM 1. Lack of packages (as shown above) Of the 10 packages listed, only three of those (maybe two) actually work. The packages are way out of date and don't build with the newer GNAT's. Patches welcome. PROBLEM 2. No choice in the use of compiler The Ada world is essentially divided between the GCC version of GNAT that can produce executables not tainted by the GPL (GNAT-FSF) and the GPL version (GNAT-GPL) from AdaCore which can't. Debian, for example, only uses GNAT-FSF (but one can, of course, just download GNAT-GPL from AdaCore and use it without issue). PROBLEM 3. Compiler version chaos and lack of architecture support We have: lang/gnat (GPL 2009 version, i386 only) Patches for amd64 support are also welcome. I thought you were going to do a port for GNAT-gpl amd64? -- DE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: trouble porting dash shell (make errors)
* Eitan Adler (eitanadlerl...@gmail.com) wrote: I tried the dash mailing list with no reply. mksignames.c is attached. Here is the output from ./configure gmake You should've use gdb to get a line where it dies: -- % gdb ./mksignames ... (gdb) run Starting program: /tmp/dash/dash-0.5.5.1/src/mksignames Assertion failed: (arena-magic == ARENA_MAGIC), function arena_malloc, file /usr/src/lib/libc/stdlib/malloc.c, line 3348. Program received signal SIGABRT, Aborted. 0x2816f7e7 in kill () from /lib/libc.so.7 (gdb) bt #0 0x2816f7e7 in kill () from /lib/libc.so.7 #1 0x2816f746 in raise () from /lib/libc.so.7 #2 0x2816e4d4 in abort () from /lib/libc.so.7 #3 0x281553f6 in __assert () from /lib/libc.so.7 #4 0x280f512e in malloc_usable_size () from /lib/libc.so.7 #5 0x280f8b26 in malloc () from /lib/libc.so.7 #6 0x0804861d in initialize_signames () at mksignames.c:112 #7 0x08048a98 in main (argc=1, argv=0xbfbfea24) at mksignames.c:414 (gdb) frame 6 #6 0x0804861d in initialize_signames () at mksignames.c:112 112 signal_names[rtmax-i] = (char *)malloc(RTLEN); (gdb) print sizeof(signal_names)/sizeof(signal_names[0]) $1 = 67 (gdb) print rtmax-i $2 = 124 -- Obviously the array is accessed out of bounds. Size of signal_names is 2*NSIG+3, and given that NSIG (sys/signal.h) is 32, that is really not enough for signals up to SIGRTMAX (126). The easiest way to fix it is to add -DUNUSABLE_RT_SIGNALS to compiler flags. This way it'll ignore realtime signals and only list standart 32 ones. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.ru ___ 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
