Hi Tracey,
Base Pr1me writes:
> Is there anyone willing and have time to look at the attached wip and
> give me some feedback on what I'm doing wrong? I can't get the thing
> to build a package.
>
> Everything runs through fake properly, but errors with "Bad package
> name" when package creation runs.
Package names require a package version; see packages-specs(7).
There are some basic requirements for a port that this one doesn't
meet. First, it has to come from a versioned source, but you're
building from the (presumably volatile) "lx106" branch. Second,
it looks like you're trying to package not crosstool-NG itself, but
a toolchain generated from it. So your build process actually
builds and installs crosstool-NG during post-configure?
@cd ${WRKSRC} && gmake && gmake install && \
./ct-ng xtensa-lx106-elf
Please, don't do that!!
You should first create a port for crosstool-NG, and have your xtensa
port depend on that port.
Third, this doesn't appear to be regular crosstool-NG, but a third-party
fork. The ports tree does have some third-party forks of bigger projects,
but I'd like to request a justification of why this toolchain can't be
built from vanilla crosstool-NG. You might be encouraged to integrate
the necessary features upstream.
--
Anthony J. Bentley
