gksudo

2013-06-08 Thread Janet Sullivan
I'm having problems with gksudo.  Gksu works fine.  Sudo gksudo program_name 
works.  However gksudo program_name gives the following error:

Failed to run program_name as user root.

Failed to exec new process: No such file or directory

Any ideas what the "no such file or directory" is?


___
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: The vim port needs a refresh

2013-06-08 Thread Chris Rees
On 7 June 2013 19:56, David O'Brien  wrote:
> On Sat, May 25, 2013 at 09:50:50AM +0100, Chris Rees wrote:
>> For years, people have been begging him to get over his fear of
>> OPTIONS, and he sits in the way of progress against almost everyone's
>> wishes.
>
> It's funny -- it's not just my fear of options -- every FreeBSD using
> co-worker I talk to frequently about OPTIONS do not like them either.

What's not funny is your dreadful attitude at replying to email.  The
number of timeouts on the vim and bash ports are shameful, and we're
stuck with two bash ports because you're too lazy to keep the main one
up to date.  I really have no idea why you're still allowed to plant
your flag in the ports tree and stand in the way of progress.  Please
consider dropping the ports, so people who are happy to keep them up
to date and don't ignore bug reports can work on them.

Chris
___
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: The vim port needs a refresh

2013-06-08 Thread Janky Jay

On 06/07/2013 12:56 PM, David O'Brien wrote:
> On Sat, May 25, 2013 at 09:50:50AM +0100, Chris Rees wrote:
>> For years, people have been begging him to get over his fear of
>> OPTIONS, and he sits in the way of progress against almost everyone's
>> wishes.
> It's funny -- it's not just my fear of options -- every FreeBSD using 
> co-worker I talk to frequently about OPTIONS do not like them either.
>

Um... What?! If you don't like options, use packages. The ports system
is specifically designed to allow the user to *CHOOSE THEIR BUILD
OPTIONS*. How is this so difficult to understand?

-Janketh 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: www/web2ldap: distfile web2ldap-1.1.34.tar.gz outdated

2013-06-08 Thread Boris Samorodov
08.06.2013 14:30, Matthias Apitz пишет:

> The Subject: says it all: the source file does not exist anymore;
> Thx

The port has been updated. Thanks for the heads-up!

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
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: REWARD for working pam_mount

2013-06-08 Thread Kubilay Kocak
On 9/06/2013 12:33 AM, Janet Sullivan wrote:
> Thank you for the quick turnaround.  I'll make a donation to the foundation 
> in your honor. :-)
> 
> I am having problems with the patch, however, part of it is rejected, as seen 
> below.
> 
> (/usr/ports/sysutils/pam_mount) .oO Sat Jun 08 07:30 AM Oo.
> [co1gnsntxw01] (root)## patch < pam_mount-fix-libHX.patch
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --
> |Index: Makefile
> |===
> |--- Makefile   (revision 320195)
> |+++ Makefile   (working copy)
> --
> Patching file Makefile using Plan A...
> Hunk #1 failed at 14.
> 1 out of 1 hunks failed--saving rejects to Makefile.rej
> Hmm...  The next patch looks like a unified diff to me...
> The text leading up to this was:
> --
> |Index: files/patch-commit335500
> |===
> |--- files/patch-commit335500   (revision 0)
> |+++ files/patch-commit335500   (working copy)
> --
> (Creating file files/patch-commit335500...)
> Patching file files/patch-commit335500 using Plan A...
> Hunk #1 succeeded at 1.
> Hmm...  Ignoring the trailing garbage.
> done
> 
> -Original Message-
> From: Kubilay Kocak [mailto:koobs.free...@gmail.com] 
> Sent: Friday, June 7, 2013 10:42 PM
> To: Janet Sullivan
> Cc: po...@freebsd.org
> Subject: Re: REWARD for working pam_mount
> 
> On 8/06/2013 1:57 PM, Janet Sullivan wrote:
>> The /usr/ports/sysutils/pam_mount port is broken, because it's
>> expecting an older version of libHX.   I'd really like to have a
>> working pam_mount, and am willing to paypal US $50 over to the first
>> person who gets it working.   I'm not subscribed to the list, so
>> please email me directly to claim the prize.
> 
> Janet,
> 
> Your offer is commendable but unnecessary :)
> 
> Try this patch I just created (cherry picked from upstream), and let me know 
> how it goes. You'll want to apply it to the pam_mount port directory.
> 
> There's also something you can do to ensure pam_mount will work going
> forward:
> 
> I had to backport the fix because the new pam_mount 2.13 version requires 
> libmount. Let upstream know that FreeBSD doesn't have libmount, and request 
> they make it optional and configurable (--without-libmount configure option 
> for example), even if it disables certain functionality.
> 
> If it works for you, let me know so I can commit the change, and feel free to 
> consider donating to the FreeBSD Foundation instead
> 
> Koobs
> 

You're welcome Janet

For the Makefile, all you want to change is:

-LIB_DEPENDS=   HX.27:${PORTSDIR}/lang/libhx
+LIB_DEPENDS=   HX:${PORTSDIR}/lang/libhx

If that doesn't work for you, I've also attached a second version of the
patch

Let me know how you go

Koobs

===> Generating patch
===> Viewing diff with more
diff -ruN /usr/ports/sysutils/pam_mount/Makefile ./Makefile
--- /usr/ports/sysutils/pam_mount/Makefile  2012-11-17 17:01:40.0 
+1100
+++ ./Makefile  2013-06-08 14:23:04.506365111 +1000
@@ -3,7 +3,7 @@
 # Date created:14 October 2010
 # Whom:gahr
 #
-# $FreeBSD: ports/sysutils/pam_mount/Makefile,v 1.11 2012/11/17 06:01:40 
svnexp Exp $
+# $FreeBSD: head/sysutils/pam_mount/Makefile 300897 2012-07-14 14:29:18Z beat $
 #
 
 PORTNAME=  pam_mount
@@ -14,7 +14,7 @@
 MAINTAINER=g...@freebsd.org
 COMMENT=   A PAM that can mount volumes for a user session
 
-LIB_DEPENDS=   HX.27:${PORTSDIR}/lang/libhx
+LIB_DEPENDS=   HX:${PORTSDIR}/lang/libhx
 
 USE_GNOME= pkgconfig libxml2
 USE_PERL5= yes
diff -ruN /usr/ports/sysutils/pam_mount/files/patch-commit335500 
./files/patch-commit335500
--- /usr/ports/sysutils/pam_mount/files/patch-commit335500  1970-01-01 
10:00:00.0 +1000
+++ ./files/patch-commit335500  2013-06-08 15:30:41.045578737 +1000
@@ -0,0 +1,144 @@
+# Patch for commit 33550036cb0c9311c9dc4da9b3b359435319420e (pam-mount)
+# Log: src: update for libHX 3.12
+# Authored by: Jan Engelhardt 2011-12-02
+
+--- ./configure.ac.orig2011-10-06 22:48:08.0 +1100
 ./configure.ac 2013-06-08 14:52:22.855624000 +1000
+@@ -63,7 +63,7 @@
+ AM_CONDITIONAL([HAVE_MDIO], [test "x$ac_cv_header_sys_mdioctl_h" = "xyes"])
+ AM_CONDITIONAL([HAVE_VND], [test "x$ac_cv_header_dev_vndvar_h" = "xyes"])
+ 
+-PKG_CHECK_MODULES([libHX], [libHX >= 3.10.1])
++PKG_CHECK_MODULES([libHX], [libHX >= 3.12])
+ PKG_CHECK_MODULES([libxml], [libxml-2.0 >= 2.6])
+ 
+ AC_ARG_WITH(
+--- ./src/autoloop.c.orig  2011-10-06 22:48:08.0 +1100
 ./src/autoloop.c   2013-06-08 14:45:47.846247000 +1000
+@@ -54,7 +54,8 @@
+   HXOPT_AUTOHELP,
+   HXOPT_TABLEEND,
+   };
+-  if (HX_getopt(options_table, argc, argv, HXOPT_USAGEONERR) <= 0)
++  if (HX_getopt(options_tab

RE: REWARD for working pam_mount

2013-06-08 Thread Janet Sullivan
Thank you for the quick turnaround.  I'll make a donation to the foundation in 
your honor. :-)

I am having problems with the patch, however, part of it is rejected, as seen 
below.

(/usr/ports/sysutils/pam_mount) .oO Sat Jun 08 07:30 AM Oo.
[co1gnsntxw01] (root)## patch < pam_mount-fix-libHX.patch
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--
|Index: Makefile
|===
|--- Makefile   (revision 320195)
|+++ Makefile   (working copy)
--
Patching file Makefile using Plan A...
Hunk #1 failed at 14.
1 out of 1 hunks failed--saving rejects to Makefile.rej
Hmm...  The next patch looks like a unified diff to me...
The text leading up to this was:
--
|Index: files/patch-commit335500
|===
|--- files/patch-commit335500   (revision 0)
|+++ files/patch-commit335500   (working copy)
--
(Creating file files/patch-commit335500...)
Patching file files/patch-commit335500 using Plan A...
Hunk #1 succeeded at 1.
Hmm...  Ignoring the trailing garbage.
done

-Original Message-
From: Kubilay Kocak [mailto:koobs.free...@gmail.com] 
Sent: Friday, June 7, 2013 10:42 PM
To: Janet Sullivan
Cc: po...@freebsd.org
Subject: Re: REWARD for working pam_mount

On 8/06/2013 1:57 PM, Janet Sullivan wrote:
> The /usr/ports/sysutils/pam_mount port is broken, because it's
> expecting an older version of libHX.   I'd really like to have a
> working pam_mount, and am willing to paypal US $50 over to the first
> person who gets it working.   I'm not subscribed to the list, so
> please email me directly to claim the prize.

Janet,

Your offer is commendable but unnecessary :)

Try this patch I just created (cherry picked from upstream), and let me know 
how it goes. You'll want to apply it to the pam_mount port directory.

There's also something you can do to ensure pam_mount will work going
forward:

I had to backport the fix because the new pam_mount 2.13 version requires 
libmount. Let upstream know that FreeBSD doesn't have libmount, and request 
they make it optional and configurable (--without-libmount configure option for 
example), even if it disables certain functionality.

If it works for you, let me know so I can commit the change, and feel free to 
consider donating to the FreeBSD Foundation instead

Koobs
___
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"


[QAT] r320245: 4x leftovers

2013-06-08 Thread Ports-QAT
- Update to checkin e38d69a149

Changes:

- Jail tar(1) and pkg(8) invokations
- Remove unneeded ldd temp script
- Fix appending MASTERNAME-make.conf twice [1]
- Use swap-based disk for MDMFS [2]
- HTML: Move assets into assets/ so that tab completion
  is not hindered for logs/ by logo.jpg

Reported by:kwm [1]
Submitted by:   ak [2]
-

  Build ID:  20130608135400-43645
  Job owner: bdrew...@freebsd.org
  Buildtime: 36 minutes
  Enddate:   Sat, 08 Jun 2013 14:29:45 GMT

  Revision:  r320245
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=320245

-

Port:ports-mgmt/poudriere-devel 3.0.99.20130608

  Buildgroup: 9.1-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~bdrew...@freebsd.org/20130608135400-43645-148852/poudriere-devel-3.0.99.20130608.log

  Buildgroup: 9.1-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~bdrew...@freebsd.org/20130608135400-43645-148853/poudriere-devel-3.0.99.20130608.log

  Buildgroup: 8.3-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~bdrew...@freebsd.org/20130608135400-43645-148854/poudriere-devel-3.0.99.20130608.log

  Buildgroup: 8.3-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~bdrew...@freebsd.org/20130608135400-43645-148855/poudriere-devel-3.0.99.20130608.log


--
Buildarchive URL: 
redports 
___
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: [HEADSUP] dialog4ports does not popup anymore only for global options

2013-06-08 Thread Andrew W. Nosenko
On Fri, Jun 7, 2013 at 9:58 PM, Chris Rees  wrote:
> On 7 June 2013 18:49, Andrew W. Nosenko  wrote:
>> On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees  wrote:
>>>
>>> I can see your point when talking about DOCS, but for NLS it's insanity
>>> *for general use*.  Give me an example of where NLS non-globals are
>>> appropriate and I'll shut up.
>>
>> The GIMP in Russian locale.
>> GNU Make in any non-English locale.
>
> I guess you mean the translations are bad?

Your guess is wrong.  For some reason you are treating NLS as "black
and white" thing.  Either completely enable, or completely disable.
Please, just belive that there are lot of grays in between.

But I'm completely against:
1. Poor or confusing translations (when easiest way to understand
something is to try to back-translate to English, or in some
pathological cases, start application in the English locale and match
UI elements by position);
2. Translations of tools, which are intended to or used to interact
with other tools, as opposed to the end users (GNU make, GCC, Git,
GnuPG are perfect examples)
3. Ports which do not provide the easy enough and consistent way to
disable NLS.  Just because it deprives me a way to workaround cases #1
and #2.

And the #3 is the reason, why I stand up in this thread.
I don't bother about popping-up dialogs.  After all, I'm not in a
business of rebuilding the whole ports tree from scratch every day.
And even a machine will wait my answer the whole night -- not a
problem.  Summary time required to build plus wasted time is
negligible in comparison to time spent in using application.
Therefore, the first thing, which I optimize, is a comfort of using
application, and other things are going only after that.

-- 
Andrew W. Nosenko 
___
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 build openjdk7 for customized FreeBSD system

2013-06-08 Thread Xu Zhe
? 6/8/13 5:23 PM, Chris Rees ??:
>
>
> On 8 Jun 2013 04:05, "Peter Xu"  > wrote:
> >
> > I did this in a stupid way. I am sending this out in case someone
> met the
> > same problem (or to say, you want to build openjdk on an platform
> that have
> > no older version of JDK supported).
> >
> > The main idea is, firstly find a generic FreeBSD 8.2 system, build the
> > openjdk7 package (well, there is no problem on generic system, as
> long as
> > you are using the port collections corresponding to that specific
> version I
> > suppose). Then, we can leverage all the Java-built output (includes
> > *.class, *.jar, and some *.java/*.[ch] if they are auto-generated by the
> > build system using JVM) in the generic systems, replacing all the
> > $(JAVAC_CMD) and $(JAVAH_CMD) lines in Makefiles with something like
> (or we
> > can try direct copy of the object files, but sometimes we still need
> to do
> > this since the dependencies of 'make' are not the JAR files sometimes):
> >
> > scp $GENERIC_BSD:$JAR_FILE_PATH $PRIVATE_BSD:$JAR_FILE_PATH
> >
> > Or to say, we do fetch the good 'jar' from the generic systems
> instead of
> > invoking a sick JVM and build it until we met error and stop the make
> > process.
> >
> > I suppose all these things need some knowledge on the Makefile
> structure of
> > openjdk. This is nasty work, but it did work for us.
> >
> > Another solution I thought about is cross-compile the whole JDK on a
> > generic system, and copy all the private C libraries on the private
> system
> > to the generic one before-hand (this may only be working when the
> generic
> > system has cross-toolchain I suppose, or in my case that the two systems
> > are using the same CPU arch). Just an idea, no need to try currently.
>
> I'm really pleased you fixed it in the end; I'd just succeeded in
> making you a package too, but never mind.
>
> Now you have time to migrate your hacks to later FreeBSD, and even get
> some of them committed ;)
>
> Chris
>
Hi, Chris,

Thanks for the attempt to help. :)

However, I am not quite sure on the migrate thing. Do you mean that, I
can re-arrange the hack so that openjdk on FreeBSD would support build
across two machines (or to say, to seperate Java/native code build)?

Peter
___
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: REWARD for working pam_mount

2013-06-08 Thread Kubilay Kocak
On 8/06/2013 8:32 PM, Jerry wrote:
> On Sat, 08 Jun 2013 15:42:23 +1000
> Kubilay Kocak articulated:
> 
>> I had to backport the fix because the new pam_mount 2.13 version
>> requires libmount. Let upstream know that FreeBSD doesn't have
>> libmount, and request they make it optional and configurable
>> (--without-libmount configure option for example), even if it
>> disables certain functionality.
> 
> Maybe it is just me; however, wouldn't it make more sense for FreeBSD to
> acquire "libmount" and thereby eliminate the whole problem to begin
> with, not to mention losing potential functionality?
> 

If that's the whole problem, and if it makes sense, absolutely.

Though not explicit, my advice was based on the following:

a) That my cherry-picked patch is likely only an interim measure.

b) That the easiest thing an end-user could do to contribute to a
solution is to notify the authors that portability would help.

c) We can no longer track pam_mount updates given the recent addition of
libmount as a hard dependency.

d) that libmount (part of util-linux) is likely quite Linux centric and
not useful in FreeBSD terms. I may be wrong here.

The root cause of Janets reported issue is only a LIB_DEPENDS pointing
to a specific library version (unnecessarily) and a libhx port that has
moved on that pam_mount didn't support.

But definitely, there may be more 'longer term' solutions such as what
you eluded to.

koobs


___
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: REWARD for working pam_mount

2013-06-08 Thread Jerry
On Sat, 08 Jun 2013 15:42:23 +1000
Kubilay Kocak articulated:

> I had to backport the fix because the new pam_mount 2.13 version
> requires libmount. Let upstream know that FreeBSD doesn't have
> libmount, and request they make it optional and configurable
> (--without-libmount configure option for example), even if it
> disables certain functionality.

Maybe it is just me; however, wouldn't it make more sense for FreeBSD to
acquire "libmount" and thereby eliminate the whole problem to begin
with, not to mention losing potential functionality?

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
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"

www/web2ldap: distfile web2ldap-1.1.34.tar.gz outdated

2013-06-08 Thread Matthias Apitz

Hi,

The Subject: says it all: the source file does not exist anymore;
Thx

matthias

-- 
Matthias Apitz   |  /"\ ASCII Ribbon Campaign: www.asciiribbon.org
E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
phone: +49-170-4527211   |  / \ - Respect for open standards
___
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: [HEADSUP] dialog4ports does not popup anymore only for global options

2013-06-08 Thread Michael Gmelin
On Fri, 7 Jun 2013 21:06:32 +0300
"Andrew W. Nosenko"  wrote:

> On Fri, Jun 7, 2013 at 8:23 PM, Michael Gmelin 
> wrote:
> >
> > I was mostly talking about DOCS, I (poorly) chose NLS as an
> > additional example to show how multiple groups could work. Usually
> > NLS is a true global option.
> 
> NLS is global option only for people with en_* locale, who, therefore,
> just don't see the pain produced by it.  DOCS are just a space on HDD.
>  But localized names of image filters, tools & Co in GIMP -- it's just
> a barrier to use books and other knowledge sources.  And I don't say
> just about stupid eye-blow errors in translations, when results of
> automatic merge went in the release and the wild without even fast
> looking through by the someone, who has that language as native.
> 

Translations tend to be bad when there is no QA process. Ever been
asked if you want to "nearby the application"?

I usually disable NLS or use LANG=C/en_US.UTF-8 all the time for most
development tools (gmake, gcc etc.) since the translations are just
irritating, but explicitly switch to my native language for certain UI
apps. That's fairly easy to do though, so in most cases messing with
NLS on a ports level is unnecessary, e.g.

export LANG=en_US.UTF-8
alias gimp="LANG=de_DE.UTF-8 gimp"

(for those who prefer using gimp in German)

-- 
Michael Gmelin
___
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: [HEADSUP] dialog4ports does not popup anymore only for global options

2013-06-08 Thread Daniel Nebdal
On Fri, Jun 7, 2013 at 8:58 PM, Chris Rees  wrote:
> On 7 June 2013 18:49, Andrew W. Nosenko  wrote:
>> On Fri, Jun 7, 2013 at 8:15 PM, Chris Rees  wrote:
>>>
>>> I can see your point when talking about DOCS, but for NLS it's insanity
>>> *for general use*.  Give me an example of where NLS non-globals are
>>> appropriate and I'll shut up.
>>
>> The GIMP in Russian locale.
>> GNU Make in any non-English locale.
>
> I guess you mean the translations are bad?
>
> Chris


Even good translations can be annoying if you're trying to use them
together with resources in English. (For values of "resources" that
can also include searching for the exact error string online...)


--
Daniel Nebdal
___
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 build openjdk7 for customized FreeBSD system

2013-06-08 Thread Chris Rees
On 8 Jun 2013 04:05, "Peter Xu"  wrote:
>
> I did this in a stupid way. I am sending this out in case someone met the
> same problem (or to say, you want to build openjdk on an platform that
have
> no older version of JDK supported).
>
> The main idea is, firstly find a generic FreeBSD 8.2 system, build the
> openjdk7 package (well, there is no problem on generic system, as long as
> you are using the port collections corresponding to that specific version
I
> suppose). Then, we can leverage all the Java-built output (includes
> *.class, *.jar, and some *.java/*.[ch] if they are auto-generated by the
> build system using JVM) in the generic systems, replacing all the
> $(JAVAC_CMD) and $(JAVAH_CMD) lines in Makefiles with something like (or
we
> can try direct copy of the object files, but sometimes we still need to do
> this since the dependencies of 'make' are not the JAR files sometimes):
>
> scp $GENERIC_BSD:$JAR_FILE_PATH $PRIVATE_BSD:$JAR_FILE_PATH
>
> Or to say, we do fetch the good 'jar' from the generic systems instead of
> invoking a sick JVM and build it until we met error and stop the make
> process.
>
> I suppose all these things need some knowledge on the Makefile structure
of
> openjdk. This is nasty work, but it did work for us.
>
> Another solution I thought about is cross-compile the whole JDK on a
> generic system, and copy all the private C libraries on the private system
> to the generic one before-hand (this may only be working when the generic
> system has cross-toolchain I suppose, or in my case that the two systems
> are using the same CPU arch). Just an idea, no need to try currently.

I'm really pleased you fixed it in the end; I'd just succeeded in making
you a package too, but never mind.

Now you have time to migrate your hacks to later FreeBSD, and even get some
of them committed ;)

Chris
___
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"