Package Base Details: pjproject

Git Clone URL: https://aur.archlinux.org/pjproject.git (read-only, click to copy)
Submitter: None
Maintainer: alerque (GNUtoo, wuestengecko)
Last Packager: alerque
Votes: 33
Popularity: 0.026254
First Submitted: 2007-09-07 12:14 (UTC)
Last Updated: 2023-05-03 22:49 (UTC)

Pinned Comments

alerque commented on 2020-02-22 05:37 (UTC)

PSA: I've started hosting this and also many other packages I maintain in the AUR as prebuilt packages in my repository for those that want to install them using pacman without messing around with building from the AUR.

Latest Comments

1 2 3 4 5 6 7 Next › Last »

alerque commented on 2023-02-23 10:40 (UTC)

@jfernandz The main project and the python bindings are built from the same sources released at the same time, hence the split package. This is the correct arrangement and your AUR tooling should be fixed to handle this, there are many such projects around.

There is no pjusa package listed in official Arch repos or the AUR, so there is no reason for this package to list it as a conflict. If there are externally built packages somewhere the onus is on them to mark conflicts with anything available in the Arch ecosystem. Anything installed from source is on you.

jfernandz commented on 2022-11-30 16:29 (UTC) (edited on 2022-11-30 16:30 (UTC) by jfernandz)

I'm not sure, but ... I'd say this package should have a conflict with pjsua package

Also ... It's a little strange for me a base package that produces two different packages, I usually clone a base package with its dependencies recursively (with auracle clone --recurse <package>), but I guess it's easier for you to build at once pjproject and python-pjproject :-)

alerque commented on 2022-02-17 11:34 (UTC)

Thanks for the heads sup @severach. I'm really not sure how that happened, those commit-as-patch URLs should have stable contents.

severach commented on 2022-02-17 01:08 (UTC)

Patch 0002-Fix checksum has changed.

kilobytech commented on 2021-11-19 14:27 (UTC)

Found the culprit for the build error. Looks like I installed pjproject at some point with make install which resulted in some leftover libraries under /usr/lib which got linked during building instead of the fresh built libraries. Fixed it with rm -r /usr/lib/libpj*.a.

kilobytech commented on 2021-11-19 11:35 (UTC)

Have the same build error like @duthils

/usr/bin/ld: output/pjlib-test-x86_64-unknown-linux-gnu/timer.o: in function `timer_test':
timer.c:(.text+0x1a4b): undefined reference to `pj_pool_secure_release'
collect2: error: ld returned 1 exit status

alerque commented on 2021-08-29 06:05 (UTC)

@TheKinrar I assume because none of us that have worked on this have needed the Java bindings. If you do I'd be happy to accept a patch that sets up a split package build that reenables the necessary instructions to build and adds the bits to install the Java bindings. You can either post a patch (using git format-patch) here or send a PR to this repo.

TheKinrar commented on 2021-08-29 01:55 (UTC)

Thanks for publishing this package! I was wondering why the Java bindings are not built while the Python ones are?

alerque commented on 2021-07-23 07:48 (UTC)

@duthils No I have not seen than error. I also routinely build this package in a completely clean chroot setup using makechrootpkg, so I know the dependencies are correct. Perhaps you have something out of date or otherwise cross wired on your system? I suggest building it it a chroot yourself. Also try the current version, and run a full system update first.

duthils commented on 2021-07-10 13:22 (UTC)

Hi, I get the following error when building pjproject 2.11-5:

/usr/sbin/ld: output/pjlib-test-x86_64-unknown-linux-gnu/timer.o: in function `timer_test'
timer.c:(.text+0x1a5b): undefined reference to `pj_pool_secure_release'

Have you encountered this error before?