Re: Issue about adapting japanese/ruby-mecab to new options framework
From: Jason Helfman j...@freebsd.org
Subject: Re: Issue about adapting japanese/ruby-mecab to new options framework
Date: Sun, 27 Jan 2013 11:40:04 -0800
You could look at setting OPTIONSFILE in the ports Makefile, itself.
For instance, this is set in net/rubygem-net-ssh. Although this may not be
the exact entry, this is an example you can work with to get it to work as
it should.
OPTIONSFILE?= ${PORT_DBDIR}/rubygem-${PORTNAME}/options
From: Scot Hetzel swhet...@gmail.com
Subject: Re: Issue about adapting japanese/ruby-mecab to new options framework
Date: Sun, 27 Jan 2013 13:41:00 -0600
You could add OPTIONSFILE to japanese/ruby-mecab/Makefile as:
OPTIONSFILE= ${PORT_DBDIR}/ruby-mecab/options
This way it will always find it's own options file.
When following line is added in japanese/ruby-mecab/Makefile, options
dialog doesn't displayed only once:
OPTIONSFILE=${PORT_DBDIR}/ja-ruby-mecab/options
But when following line is added, it displayed every time:
OPTIONSFILE= ${PORT_DBDIR}/ja-${RUBY_PKGNAMEPREFIX}${PORTNAME}/options
Does it mean RUBY_PKGNAMEPREFIX cannot be used to assign OPTIONSFILE?
If answer is yes then the former is best solution. But if possible I
would like to reflect the version of ruby on OPTIONSFILE.
---
Yasuhiro KIMURA
___
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: devel/gobject-introspection failure on ARM
On 01/28/13 05:55, Koop Mast wrote: On Sun, 2013-01-27 at 10:57 -0500, George Mitchell wrote: System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) ports: svnversion 308518 Build dies with message sizeof(ArrayTypeBlob) is expected to be 8 but is 12. (Complete build log attached.) I made a naive attempt to fix it by rearranging the order of the structure members, but obviously I don't understand structure packing on the ARM and it didn't help. It also didn't get rid of the huge number of cast increases required alignment of target type warnings. I note we're at version 0.10.8 of this package, but upstream is at 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). What's the best way to proceed? -- George Mitchell I'm currently in the process of making a patch [1] for the ports tree for glib 2.34.3 and gobject-introspection 1.34.1.1. If you want to give this a shot on ARM. Please note that the patch is WIP. Not all ports have been tested yet. -Koop [1] http://people.freebsd.org/~kwm/glib-2.34_1.diff Thanks! I'll try this if I have time later today. -- George ___ 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
About lua 5.2
Hello there, Lua 5.2 has been release for more than one year, and the first release 5.2.1 on june 2012. Lua has some disavantages to break compatibility between major versions, thus I'm not sure if current lua modules in the ports tree will still works with that version. Should we start a repocopy of all modules to lua51-* before creating the new port for lua 5.2? -- Demelier David ___ 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: devel/gobject-introspection failure on ARM
On Sun, 27 Jan 2013 10:57:19 -0500 George Mitchell george+free...@m5p.com wrote: System: Raspberry Pi uname: r245840M (Alie Tan's image from 25 January) ports: svnversion 308518 Build dies with message sizeof(ArrayTypeBlob) is expected to be 8 but is 12. (Complete build log attached.) I made a naive attempt to fix it by rearranging the order of the structure members, but obviously I don't understand structure packing on the ARM and it didn't help. It also didn't get rid of the huge number of cast increases required alignment of target type warnings. I note we're at version 0.10.8 of this package, but upstream is at 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8). What's the best way to proceed? -- George Mitchell Hi, It can be fixed by just change gitypelib.c: CHECK_SIZE (ArrayTypeBlob, 8); to gitypelib.c: CHECK_SIZE (ArrayTypeBlob, 12); But problem not in gobject-introspection, but in old ARM ABI. I was ask andrew@, and he test it with ARM EABI, and it compiled fine with size 8. So if somebody will fix it, please #ifdef that fix to make it only with old ARM ABI. Or, better help with EABI testing :-D Thanks! WBW -- Aleksandr Rybalko r...@ddteam.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: Cronjob Cvsup - What?
On Sun, 27 Jan 2013 08:22:02 -0500 Thomas Mueller wrote: I've always used portsnap fetch update after the initial portsnap fetch and portsnap extract. What would be the adverse side effect of using svn instead? RW rwmailli...@googlemail.com responded: In general it's best to avoid mixing update tools unless you fully understand all the corner cases and know it's safe. The most significant problem is they can lose track of what files need to be deleted, which can lead to obsolete patch files being left in the tree. One of the functions of portsnap extract is to eliminate extra files in port directories to avoid this problem. You miss my point. The intent was not to mix portsnap and svn but to use svn in a separate location, /usr/ports as opposed to the present /BETA1/usr/ports, with the intent to switch to svn. Of course, I realize I'd have to update at least three etc/make.conf files: hard drive installation, USB stick amd64 and USB stick i386. Tom ___ 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: databases/mongodb fails to start, assertion failure in unit test
On Sat, Jan 26, 2013 at 07:06:21AM -0800, Waitman Gobble wrote:
Waitman Gobble uzi...@da3m0n8t3r.com wrote ..
Hi,
I've installed databases/mongodb and get an error when starting.
# /usr/local/etc/rc.d/mongod start
Starting mongod.
forked process: 59576
all output going to: /var/db/mongodb/mongod.log
/usr/local/etc/rc.d/mongod: WARNING: failed to start mongod
# cat /var/db/mongodb/mongod.log
Fri Jan 25 00:30:57 Assertion failure l bigl src/mongo/db/btree.cpp 1973
0x5a503d 0x5eb41d 0x74dce9 0x547638 0x545ed9 0x542bc1
0x5a503d _ZN5mongo12verifyFailedEPKcS1_j+285 at /usr/local/bin/mongod
0x5eb41d _ZN5mongo10BTUnitTest3runEv+333 at /usr/local/bin/mongod
0x74dce9 _ZN5mongo11StartupTest8runTestsEv+57 at /usr/local/bin/mongod
0x547638 main+5992 at /usr/local/bin/mongod
0x545ed9 main+9 at /usr/local/bin/mongod
0x542bc1 _start+145 at /usr/local/bin/mongod
Fri Jan 25 00:30:57 Got signal: 6 (Abort trap: 6).
# portversion -v mongodb
mongodb-2.2.0_1 = up-to-date with port
# uname -a
FreeBSD kamira.waitman.net 9.1-STABLE FreeBSD 9.1-STABLE #0 r245772M: Tue
Jan 22
06:09:00 PST 2013 r...@kamira.waitman.net:/usr/obj/usr/src/sys/BURPLEX
amd64
I added a couple lines to print the values before the failure.
src/mongo/db/btree.h
..
struct BTUnitTest : public StartupTest {
void run() {
DiskLoc big(0xf12312, 0x70001234);
DiskLoc56Bit bigl;
{
bigl = big;
verify( big == bigl );
DiskLoc e = bigl;
verify( big == e );
}
{
DiskLoc d;
verify( d.isNull() );
DiskLoc56Bit l;
l = d;
verify( l.isNull() );
d = l;
verify( d.isNull() );
printf(bigl %s\n,bigl.toString().c_str());
printf(l %s\n,l.toString().c_str());
verify( l bigl );
}
}
} btunittest;
..
output:
bigl f12312:70001234
l null
Thu Jan 24 23:18:17 Assertion failure l bigl src/mongo/db/btree.cpp 1978
looking at
src/mongo/db/diskloc.h
bool isNull() const { return _a == -1; }
..
int compare(const DiskLoc b) const {
int x = _a - b._a;
if ( x )
return x;
return ofs - b.ofs;
}
bool operator(const DiskLoc b) const {
return compare(b) 0;
}
..
void Null() {
_a = -1;
ofs = 0; /* note NullOfs is different. todo clean up. see refs
to
NullOfs in code - use is valid but outside DiskLoc context so confusing
as-is.
*/
}
it seems that this should be working!
test model:
#include stdio.h
int
compare (int a, int b)
{
int x = a - b;
if ( x )
return x;
return 555;
}
bool
ncompare (int a, int b)
{
return compare(a,b) 0;
}
int
main (void)
{
int a, b;
a = -1;
b = 0xf12312;
int c = a - b;
printf(%d\n,c);
c = compare(a,b);
printf(%d\n,c);
bool d = ncompare(a,b);
printf(%d\n,d);
bool e = ncompare(b,a);
printf(%d\n,e);
return 0;
}
# clang++ -o test test.cpp
# ./test
-15803155
-15803155
1
0
I'm missing something...
Suggestions, tips, hints much appreciated.
Thanks,
--
Waitman Gobble
San Jose California USA
Hi,
I've tinkered around with this problem. Commenting out the 'verify( l
bigl );' line in src/mongo/db/btree.h solves the assertion failure
problem, and mongodb starts and runs. However, after reviewing the
code it seems this 'start' unit test is only actually testing if the
thing can 'subtract integers.' I'm very puzzled as to why it is
failing, it's bombing out when it does 'verify ((-1 - 0xf12312)0)'.
which seems trivial.
The code that runs the unit test/StartupTest is simple, but i haven't
yet found the 'verify' macro, at least i believe it's a macro.
Anyhow, commenting out the test line gets mongodb running, but I'm
wondering what other problems there could be. (?)
I found that compiling with base gcc avoids the startup problem, so
this indeed seems to be an issue related to building with clang. clang
builds mongodb without error, however running the mongodb compiled
with clang fails during 'startuptest'.
IMHO It would be good to track down the problem, at least understand
the cause, but at this moment it seems like compiling mongodb with gcc
is the way to go.
I've updated the port to use the latest release/ 2.2.2 version of
mongodb, I'll submit a PR in a bit, (it does not appear to have
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ textproc/py-jaxml | 3.02| 7.00 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org 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: databases/mongodb fails to start, assertion failure in unit test
Wesley Shields w...@freebsd.org wrote ..
On Sat, Jan 26, 2013 at 07:06:21AM -0800, Waitman Gobble wrote:
Waitman Gobble uzi...@da3m0n8t3r.com wrote ..
Hi,
I've installed databases/mongodb and get an error when starting.
# /usr/local/etc/rc.d/mongod start
Starting mongod.
forked process: 59576
all output going to: /var/db/mongodb/mongod.log
/usr/local/etc/rc.d/mongod: WARNING: failed to start mongod
# cat /var/db/mongodb/mongod.log
Fri Jan 25 00:30:57 Assertion failure l bigl src/mongo/db/btree.cpp
1973
0x5a503d 0x5eb41d 0x74dce9 0x547638 0x545ed9 0x542bc1
0x5a503d _ZN5mongo12verifyFailedEPKcS1_j+285 at /usr/local/bin/mongod
0x5eb41d _ZN5mongo10BTUnitTest3runEv+333 at /usr/local/bin/mongod
0x74dce9 _ZN5mongo11StartupTest8runTestsEv+57 at /usr/local/bin/mongod
0x547638 main+5992 at /usr/local/bin/mongod
0x545ed9 main+9 at /usr/local/bin/mongod
0x542bc1 _start+145 at /usr/local/bin/mongod
Fri Jan 25 00:30:57 Got signal: 6 (Abort trap: 6).
# portversion -v mongodb
mongodb-2.2.0_1 = up-to-date with port
# uname -a
FreeBSD kamira.waitman.net 9.1-STABLE FreeBSD 9.1-STABLE #0 r245772M: Tue
Jan
22
06:09:00 PST 2013 r...@kamira.waitman.net:/usr/obj/usr/src/sys/BURPLEX
amd64
I added a couple lines to print the values before the failure.
src/mongo/db/btree.h
..
struct BTUnitTest : public StartupTest {
void run() {
DiskLoc big(0xf12312, 0x70001234);
DiskLoc56Bit bigl;
{
bigl = big;
verify( big == bigl );
DiskLoc e = bigl;
verify( big == e );
}
{
DiskLoc d;
verify( d.isNull() );
DiskLoc56Bit l;
l = d;
verify( l.isNull() );
d = l;
verify( d.isNull() );
printf(bigl %s\n,bigl.toString().c_str());
printf(l %s\n,l.toString().c_str());
verify( l bigl );
}
}
} btunittest;
..
output:
bigl f12312:70001234
l null
Thu Jan 24 23:18:17 Assertion failure l bigl src/mongo/db/btree.cpp
1978
looking at
src/mongo/db/diskloc.h
bool isNull() const { return _a == -1; }
..
int compare(const DiskLoc b) const {
int x = _a - b._a;
if ( x )
return x;
return ofs - b.ofs;
}
bool operator(const DiskLoc b) const {
return compare(b) 0;
}
..
void Null() {
_a = -1;
ofs = 0; /* note NullOfs is different. todo clean up. see
refs
to
NullOfs in code - use is valid but outside DiskLoc context so confusing
as-is.
*/
}
it seems that this should be working!
test model:
#include stdio.h
int
compare (int a, int b)
{
int x = a - b;
if ( x )
return x;
return 555;
}
bool
ncompare (int a, int b)
{
return compare(a,b) 0;
}
int
main (void)
{
int a, b;
a = -1;
b = 0xf12312;
int c = a - b;
printf(%d\n,c);
c = compare(a,b);
printf(%d\n,c);
bool d = ncompare(a,b);
printf(%d\n,d);
bool e = ncompare(b,a);
printf(%d\n,e);
return 0;
}
# clang++ -o test test.cpp
# ./test
-15803155
-15803155
1
0
I'm missing something...
Suggestions, tips, hints much appreciated.
Thanks,
--
Waitman Gobble
San Jose California USA
Hi,
I've tinkered around with this problem. Commenting out the 'verify( l
bigl );' line in src/mongo/db/btree.h solves the assertion failure
problem, and mongodb starts and runs. However, after reviewing the
code it seems this 'start' unit test is only actually testing if the
thing can 'subtract integers.' I'm very puzzled as to why it is
failing, it's bombing out when it does 'verify ((-1 - 0xf12312)0)'.
which seems trivial.
The code that runs the unit test/StartupTest is simple, but i haven't
yet found the 'verify' macro, at least i believe it's a macro.
Anyhow, commenting out the test line gets mongodb running, but I'm
wondering what other problems there could be. (?)
I found that compiling with base gcc avoids the startup problem, so
this indeed seems to be an issue related to building with clang. clang
builds mongodb without error, however running the mongodb compiled
with clang fails during 'startuptest'.
IMHO It would be good to track down the problem, at least
Re: Updating ports with portmaster after two month vacation
Probably will follow someone else with the same reply but even more informative than this one... reply is at the bottom. Sorry for the formatting... --- On Mon, 1/28/13, Edwin L. Culp W. edwinlc...@gmail.com wrote: From: Edwin L. Culp W. edwinlc...@gmail.com Subject: Updating ports with portmaster after two month vacation To: freebsd-ports freebsd-ports@freebsd.org Date: Monday, January 28, 2013, 10:56 AM I have not updated all my ports since the end of Noviember. I am still using cvsup to update the machine daily and have, what I hope is, an uptodate kernel and all programes. # uname -a FreeBSD home.encontacto.net 9.1-STABLE FreeBSD 9.1-STABLE #391 r229960M: Sat Jan 26 05:06:18 CST 2013 r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO amd64 The first strange thing that I notice is: # portversion -v portmaster [Updating the pkgdb format:bdb_btree in /var/db/pkg ... USING PKGNG - 959 packages found (-2 +3) (...)... done] USING PKGNG portmaster-3.14_8 succeeds port (port has 3.11) The last thing I remember doing era updating ports to PKGNG and that could be my problem. If so, I have no idea how to reconstruct and I'm also not sure that cvsup is still working as before. The kernel seems to work fine. Another error message that I find unusual and can't explain is: # portmaster -a === Gathering distinfo list for installed ports === Starting check of installed ports for available updates === The ports-mgmt/portmanager port has been deleted: Has expired: Does not support modern ports features such as MOVED, is lacking upstream and active contributions, and does not support pkgng. Consider using ports-mgmt/portmaster, ports-mgmt/portupgrade or pkgng === Aborting update I can't understand the relationship to portupgrade. I'm sure that I missed something very important since portmaster is trying to use portupgrade. Thanks for any help. ed -- Bienes Raíces in Coatepec, Veracruz, Mexico http://www.facebook.com/pages/Inmobiliaria-Bienes-Raices-httpEcoManiainfo/102249989850215?sk=photos_albums ___ 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 The message about portmanager portupgrade is not using it AFAIK. Portmanager may still work unless you remove it or permit portmaster to do so. AFAIK csup/cvsup will no longer work to upgrade ports, I switched all CPU over to svn (devel/subversion) awhile back and have posted in the forum informative posts. As to svn for the kernel sources, the freebsd-questions list this month (jan/enero 2013) has a detailed howto also in that regard. I would hesitate to use portmaster -a... portmaster -L --index-only | tee -a /tmp/upgrade.log wait a while... grep -A 3 -B 3 version /tmp/upgrade.log | tee -a /tmp/upgrade2.log in one xterm head -10 /tmp/upgrade2.log | tail -12 ..head -20 /tmp/upgrade2.log | tail -12 ...head -30 /tmp/upgrade2.log | tail -12 then in another xterm... portmaster -d -B -P -i -g devel/doxygen devel/cmake # etc as shown in each segment of the latter file from the pipes. Sorry for any typos or incomplete information or inaccuracies or easier ways others may currently do it, especially if one has lesser than thousands of ports installed. J. Bouquet ___ 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: Updating ports with portmaster after two month vacation
On Mon, 28 Jan 2013, Edwin L. Culp W. wrote: I have not updated all my ports since the end of Noviember. I am still using cvsup to update the machine daily and have, what I hope is, an uptodate kernel and all programes. # uname -a FreeBSD home.encontacto.net 9.1-STABLE FreeBSD 9.1-STABLE #391 r229960M: Sat Jan 26 05:06:18 CST 2013 r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO amd64 The first strange thing that I notice is: # portversion -v portmaster [Updating the pkgdb format:bdb_btree in /var/db/pkg ... USING PKGNG - 959 packages found (-2 +3) (...)... done] USING PKGNG portmaster-3.14_8 succeeds port (port has 3.11) A. The security problem caused a lot of files to not be rebuilt for a while. One of those was the INDEX file, which should be back to normal now. B. portversion is a program that is included with portupgrade. It may not show accurate results until you have run pkgdb -Fu, another portupgrade program. Or just switch to using portmaster entirely. # portmaster -a Did you check /usr/ports/UPDATING first, and do all the things that applied to that system? === The ports-mgmt/portmanager port has been deleted: Has expired: Does not support modern ports features such as MOVED, is lacking upstream and active contributions, and does not support pkgng. Consider using ports-mgmt/portmaster, ports-mgmt/portupgrade or pkgng === Aborting update I can't understand the relationship to portupgrade. There is no relation. You have at least three different upgrade programs installed. One was deleted as obsolete (portmanager), and the message recommends switching to one of the others. ___ 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
The upcoming phpMyAdmin 4.0.0
Dear all, phpMyAdmin-4.0.0 is in the early stages of its release process, with 4.0.0-alpha2 released earlier today, alongside the just-committed update for the released version to 3.5.6. Now, my usual approach with the databases/phpmyadmin port is to track the latest released version, except for occasional forays into beta or release-candidate version when there have been early releases forced by security problems. Currently my intent is to switch databases/phpMyAdmin to track 4.0.x shortly after that version is released. It's a new major version with lots of new code, a different look and feel, and one of the principal changes is that it will require javascript to function. What do people think? If anyone has any reasoned objections to this, please let me know. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
status of ports/175298 (net/tightvnc fails with clang)
Hi, Anyone working for ports/175298? http://www.freebsd.org/cgi/query-pr.cgi?pr=175298 The workaround adding USE_GCC= 4.2+ goes well for me. If anyone can fix it to build with clang, that's pretty good. But how about just marking it to use gcc for now? -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ 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
