Search Criteria
Package Details: mips-harvard-os161-gdb 7.8+os161_2.1-3
Git Clone URL: | https://aur.archlinux.org/mips-harvard-os161-gdb.git (read-only, click to copy) |
---|---|
Package Base: | mips-harvard-os161-gdb |
Description: | The GNU Debugger modified for mips-harvard-os161 arquitecture. This is part of toolset for the course os161 from Harvard. |
Upstream URL: | http://os161.eecs.harvard.edu/ |
Licenses: | |
Groups: | |
Submitter: | gerito |
Maintainer: | gerito |
Last Packager: | gerito |
Votes: | 3 |
Popularity: | 0.002717 |
First Submitted: | 2017-02-13 12:47 |
Last Updated: | 2019-09-18 03:34 |
Dependencies (7)
- gmp (gmp-hg, scipoptsuite, scipoptsuite-bin)
- guile2.0
- libmpc (libmpc-git)
- mpfr (mpfr-svn)
- mips-harvard-os161-binutils>=2.24
- bison (byacc-bison, bison-git) (make)
- flex (flex-git) (make)
Latest Comments
1 2 Next › Last »
gerito commented on 2019-09-18 04:02
@johnramsden Welp. I swear I couldn't find it. Yes, that one. XP
johnramsden commented on 2019-09-18 03:55
No worries, thanks for your time @gerito. In the meantime I was able to get it to build by building in a clean chroot with no python3.
Isn't this the emulator? https://aur.archlinux.org/packages/sys161/
gerito commented on 2019-09-18 03:42
@johnramsden I'm so sorry for the delay. I have been busy lately and stuff. I hope this fixes the build issue, unfortunately I discovered that the sys161 emulator is no longer available in aur anymore. I'm not sure if I should provide one or no. It is not difficult to set it up by yourself, once the toolchain, bmake and all other dependencies are installed. If you have any other problem I will try to answer but keep in mind it could take time. It took me most part of my afternoon to fix this, granted it wasn't difficult (I had to back-port a patch) but I had to set up my environment and stuff. Again I'm sorry for the delay.
johnramsden commented on 2019-09-11 01:24
I'm getting the following during builds:
Anonymous comment on 2018-06-01 02:39
@sommd The error is caused because the python modules that mips-harvard-os161-gdb depend on are deleted during install.
When gdb from extra isn't installed, the modules cannot load (there's a brief error). If it is installed, then the modules that load cause errors like you're seeing because they aren't compatible. I suspect that this is because gdb in extra is at version 8+ while the one in the OS/161 toolchain is still in version 7.
This quick hack to get this working is by using the
--data-directory
argument while running mips-harvard-os161-gdb.Edit PKGBUILD so that the line I mentioned at the beginning is commented out and make sure you have mips-harvard-os161-gdb installed as is before doing the following.
Store the folder somewhere and make an alias for mips-harvard-os161-gdb so that you don't have to add it every time.
This isn't ideal but it should do until @gerito can sort out a way to fix this.
@gerito Would it be possible to install the modules in another directory that doesn't interfere with gdb from the official repos? Like
/usr/share/mips-harvard-os161-gdb
so that it's distinguished from/usr/share/gdb
?sommd commented on 2018-05-31 13:23
Keep getting the following error:
Which keeps printing after almost every command, making the output unreadable. The only solution I've found is to uninstall normal GDB. Any proper solutions?
Anonymous comment on 2017-07-31 17:32
@gerito Sorry for the delay! It builds perfectly fine now. Thank You.
gerito commented on 2017-07-29 08:20
I hope it works now @0xelectron, and @m51.
Please notify me for success/failure.
I wish that I could said I fixed it, but after unsuccessfully tracking the root of the problem I found a patch and I just applied.
I found another error, and I added a new dependency.
gerito commented on 2017-07-29 03:56
Sorry for the delay, I missed the first message. @m51
It takes ages for me to compile, so when I get time I will get into.
I don't know the problem, for the moment I need to create a fresh install and start from there.
I'm on it @0xelectron, and @m51.
Anonymous comment on 2017-07-27 17:23
can confirm. I've the same error as @m51. I'll too look into it.