Ray Kiddy wrote:

And I did an fclone...

I assume an fclone of http://hg.openjdk.java.net/bsd-port/bsd-port/, e.g.

  rm -f -r your-bsd-forest
  hg fclone http://hg.openjdk.java.net/bsd-port/bsd-port your-bsd-forest

Once you have the forest, all you need to refresh it is
  cd your-bsd-forest
  hg fpull -u

Being a forest, the hg tags only tells you what the tags are for that
one repo, e.g. try 'cd jdk && hg tags | head -2' you will see different
changesetids.

Run 'hg ftrees' to see a list of all the repos in your forest, each
is pretty independent, only the forest commands apply to all repos,
e.g. fpull, fclone, fpush, fstatus, etc.


% hg tags | head -2
tip                              163:dca45e0a2395
jdk7-b76                         161:c8b63075403d
...

And...

....K/bsd-port/build/bsd-i586/tmp/sun/sun.awt/splashscreen/obj/zadler32.o /Users/ray/Projects/OpenJDK/bsd-port/build/bsd-i586/tmp/sun/sun.awt/splashscreen/obj/zcrc32.o /Users/ray/Projects/OpenJDK/bsd-port/build/bsd-i586/tmp/sun/sun.awt/splashscreen/obj/zutil.o -liconv -L/usr/X11/lib -lX11 -lXext -lm -pthread
ld: library not found for -lX11
collect2: ld returned 1 exit status
make[4]: *** [/Users/ray/Projects/OpenJDK/bsd-port/build/bsd-i586/lib/i386/libsplashscreen.dylib] Error 1
make[3]: *** [all] Error 1
make[2]: *** [all] Error 1
make[1]: *** [jdk-build] Error 2
make: *** [build_product_image] Error 2

I don't know much about the state of the bsd-port.

It looks like it is in the middle of awt build (inside the jdk repository) and
it cannot find X11.  Is X11 installed on your Mac? I think it's an optional
install on Macs.


Same error.

Nobody has mentioned a bug database. I have the mailing list and there is a wiki.....

See http://openjdk.java.net/groups/web/bugzilla.html

But you realize that most of us work on the linux, solaris, or
windows side of things. Not many of us doing mac work.

You probably want the bsd-port email aliases:
  http://openjdk.java.net/projects/bsd-port/

-kto


Could it be that the library can not be in the form of an .la?

% ls /usr/X11/lib/
libAppleWM.la* libXaw8.la* libXft.la* libXrender.la* libfontenc.la* libxcb-record.la* libxcb-xinerama.la* libFS.la* libXcomposite.la* libXi.la* libXss.la* liblbxutil.la* libxcb-render.la* libxcb-xlib.la* libICE.la* libXcursor.la* libXinerama.la* libXt.la* liboldX.la* libxcb-res.la* libxcb-xprint.la* libSM.la* libXdamage.la* libXmu.la* libXtst.la* libpng.la* libxcb-screensaver.la* libxcb-xtest.la* libX11.la* libXdmcp.la* libXmuu.la* libXv.la* libpng12.la* libxcb-shape.la* libxcb-xv.la* libXRes.la* libXevie.la* libXp.la* libXvMC.la* libxcb-composite.la* libxcb-shm.la* libxcb-xvmc.la* libXTrap.la* libXext.la* libXpm.la* libXvMCW.la* libxcb-damage.la* libxcb-sync.la* libxcb.la* libXau.la* libXfixes.la* libXprintAppUtil.la* libXxf86misc.la* libxcb-dpms.la* libxcb-xevie.la* libxkbfile.la* libXaw6.la* libXfont.la* libXprintUtil.la* libXxf86vm.la* libxcb-glx.la* libxcb-xf86dri.la* libxkbui.la* libXaw7.la* libXfontcache.la* libXrandr.la* libdmx.la* libxcb-randr.la* libxcb-xfixes.la*
%

- ray

On Dec 10, 2009, at 3:26 PM, Ray Kiddy wrote:


On Dec 10, 2009, at 3:00 PM, Kelly O'Hair wrote:

Andrew John Hughes wrote:
2009/12/10 Ray Kiddy <r...@ganymede.org>:
On Dec 10, 2009, at 9:05 AM, Andrew John Hughes wrote:

2009/12/10 Ray Kiddy <r...@ganymede.org>:

I just wanted to update build people on this issue. There are pages on the

<snip>



If I do "hg fupdate" in the bsd-ports directory, I get nothing new and if I
do "hg tags", I get
% hg tags
tip                              153:d7f4d0dd8d30
jdk7-b74                         150:2c88089b6e1c
...
So i think I am current.
Yeah, sounds like the BSD tree is not yet up-to-date with mainline
OpenJDK (b77).

Just to be clear...  with mercurial...

The command 'hg fupdate' does NOT pull changes from the parent.
You need to do a 'hg fpull -u' to get the latest changes in the parent.

Both the hg update and hg tags commands are just telling you about what
you have in your repositories, it tells you nothing about being 'up to date'
with the parent repositories.

Just making sure....

-kto

Yes, I think that was my problem. Too much svn-ism....

- ray




Reply via email to