Re: PlayStation 2 newlib port
Jeff Johnston <[email protected]>
| Newsgroups | gmane.comp.lib.newlib |
|---|---|
| Message-ID | <CAOox84thXZ5So5BQeYvSuORC1C1647CBZuSztf8VesyDJT7kvg@mail.gmail.com> |
Hi Francisco, If you would like help, I would suggest you tell others where they can get a proper toolset to build with or at least attach your build log which may provide more info. I certainly don't have a Playstation 2 toolset hanging around. In addition, looking at your patches, you are missing copyright/licensing info for the new files you are adding (as opposed to existing files you are modifying). If you are taking code from another location, you cannot change their license/copyright. If you wrote these from scratch you should indicate this but you still need to add the licensing/copyright info. Regards, -- Jeff J. On Tue, Jun 13, 2023 at 2:31 PM Francisco Javier Trujillo Mata < [email protected]> wrote: > Hi there! > I would like to mainstream the PS2 newlib port. So far the PS2 has had > newlib ports for years, however, it was never intended to be merged into > the mainstream. > > I'm now trying to port to the latest release 4.3.0, however, I'm suffering > some errors during the compilation process. > > I have attached the changes that I have done so far. > Then I just rerun the command `autoreconf` using the proper autoconf and > automake versions > > I execute `configure` with: > > PROC_NR=$(getconf _NPROCESSORS_ONLN) > > TARGET="mips64r5900el-ps2-elf" > TARGET_ALIAS="ee" > > ## Create and enter the toolchain/build directory > rm -rf "build-$TARGET" > mkdir "build-$TARGET" > cd "build-$TARGET" > > ## Configure the build. > CFLAGS_FOR_TARGET="-O2" ../configure \ > --prefix="$PS2DEV/$TARGET_ALIAS" \ > --target="$TARGET" \ > --enable-newlib-retargetable-locking \ > $TARG_XTRA_OPTS > > ## Compile and install. > make -j "$PROC_NR" all > > > And then it always fails with this error, > > fatal error: opening dependency file libc/sys/ps2/.deps/crt0.Tpo: No such > file or directory > > Could you help me to identify where the issue is? > > Cheers. >