Package Details: microchip-mplabx-bin 5.25-1

Git Clone URL: (read-only)
Package Base: microchip-mplabx-bin
Description: IDE for Microchip PIC and dsPIC development
Upstream URL:
Licenses: custom
Conflicts: mplab
Provides: mplab
Submitter: bxs
Maintainer: mickael9 (danwood76)
Last Packager: danwood76
Votes: 52
Popularity: 0.537484
First Submitted: 2011-12-17 04:28
Last Updated: 2019-08-15 08:33

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

leo72 commented on 2017-06-24 19:39

I solved the disk space by resizing the /tmp dir. But I still continue to get this:

sed: impossibile leggere /tmp/yaourt-tmp-leo/aur-microchip-mplabx-bin/pkg/microchip-mplabx-bin/etc/udev/rules.d/99-jlink.rules: File o directory non esistente

by commenting the following line:
# Fix broken udev rules
sed -i '/^BUS!="usb"/c \ACTION!="add", SUBSYSTEM!="usb_device", GOTO="jlink_rules_end"\r' "${pkgdir}/etc/udev/rules.d/99-jlink.rules"

I was able to install the package

danwood76 commented on 2017-06-24 17:47

Hi Leo72,

It looks like your /tmp drive is full

"Insufficient Disk Space"

A reboot might fix the issue for you or you could try building the package in a separate directory using makepkg rather than an AUR installer.

leo72 commented on 2017-06-24 17:41

I got these errors when I try to install the package:

==> Estrazione dei sorgenti in corso...
-> Estrazione di MPLABX-v3.61-linux-installer.tar usando bsdtar in corso...
-> Estrazione di fakechroot-i686.pkg.tar.xz usando bsdtar in corso...
==> Entro nell'ambiente fakeroot...
==> Avvio di package() in corso...
Extracting installers...
Running MPLABX installer...
dlsym(acl_get_fd): /usr/lib32/libfakeroot/ undefined symbol: acl_get_fd
dlsym(acl_get_file): /usr/lib32/libfakeroot/ undefined symbol: acl_get_file
dlsym(acl_set_fd): /usr/lib32/libfakeroot/ undefined symbol: acl_set_fd
dlsym(acl_set_file): /usr/lib32/libfakeroot/ undefined symbol: acl_set_file
Error copying file from packed archive /tmp/ to /opt/microchip/mplabx/v3.61/mplab_ide/ide/modules/ext/icu4j-4_4_2.jar
:Insufficient Disk Space
sed: impossibile leggere /tmp/yaourt-tmp-leo/aur-microchip-mplabx-bin/pkg/microchip-mplabx-bin/etc/udev/rules.d/99-jlink.rules: File o directory non esistente
==> ERRORE: Si è verificato un errore in package().
L'operazione sta per essere interrotta...
==> ERRORE: Makepkg non è riuscito a compilare microchip-mplabx-bin.

(File o directory non esistente => File or Directory doesn't exist)
I don't use Jlink, I didn't install it on my system. And why I get "insufficient space"?

danwood76 commented on 2017-05-16 08:09

Hi Mickael,

Just to let you know, the Segger is working fine in your latest PKGBUILD.
Microchip haven't responded yet.

Thanks for all your work!


danwood76 commented on 2017-05-11 07:40

Hi Mickael,

Yes, that fixes the issue.

I will mention that in my support ticket with microchip.


mickael9 commented on 2017-05-10 15:54

@danwood76: does this fix the issue?

sed -i 's#/usr/local/lib/\x00\x00\x00\x00\x00\x00#'

danwood76 commented on 2017-05-10 15:34


I recently got a Segger Jlink to work with the PIC32 series of devices and unfortunately found that it didn't work when using this package.

I eventually tracked the issue down today, in the current PKGBUILD the jlink library ( is moved out of /usr/local/lib into /usr/lib

Unfortunately this breaks the MPLABX jlink plugin that appears to have a hard coded library path (symlinking to the lib from /usr/local/lib fixes the issue).

Is it possible to add an additional symlink to the PKGBUILD to work around this bug? (I am opening a ticket in the microchip support system as we speak)

ln -s /usr/lib/ /usr/local/lib/

Fixes the issue.

Best regards,

torkelatgenet commented on 2017-01-17 19:41

==> Validating source files with md5sums...
MPLABX-v3.50-linux-installer.tar ... Passed
LICENSE ... Passed
==> Validating source_x86_64 files with md5sums...
fakechroot-i686.pkg.tar.xz ... FAILED
==> ERROR: One or more files did not pass the validity check!

Im getting this.

potatoe commented on 2016-11-01 22:24

@mickael9: You're right, I didn't realize how much was bundled in with MPLABX. I think just renaming the rules file to something unique to this package, like 99-mplab-jlink.rules, is indeed the best choice.

I agree there shouldn't be any harm with both rules files installed, they're both the same file contents currently, and I think they're just setting a world-writable MODE on the devices anyway.

mickael9 commented on 2016-10-31 20:13

@potatoe: I'm not sure what to do here here and I don't use J-Link.

MPLABX seems to bundle everything that is needed, requiring installation of a a separate package just for the udev rules seems a bit silly unless most users needing J-Link support are most likely to also want jlink-software-and-documentation (you tell me)

One solution would be to rename the jlink rules file so that it doesn't conflict with the one from jlink-software-and-documentation. The rules will be applied twice but this won't cause any harm. What do you think?