Re: New FS driver (and support for a new OS).

[Jochen Hoenicke]

On Oct 31, Kurt Skauen wrote:
> The only solution I found to this (other than hacking the
> linker-scripts) was to strip away the offending sections with the "-R"
> option to objcopy.
> 
> The resulting makfile rule:
> 
> %: %.exec
>       $(OBJCOPY) -O binary -R .hash -R .dynsym -R .dynstr -R .rel.text \
>       -R .rel.data -R .rel.got -R .rel.rodata -R .dynamic $< $@
> 
> Could this cause problems on some other platforms? Or can it be left
> as it is? Or does anyobody know about a better solution to this
> problem?

I don't think that stripping unused sections can cause problems.  But
the cleanest solution is probably to write a ".lds" script describing
how to layout the data.

> > > I'm also wondering if the filesystem driver must follow the GNU coding
> > > style?
> > 
> >   It should.
> 
> So I have to rewrite it?
> Anybody who know about a portable code-obfuscator? :)

regarding formatting: man indent

Changing the variable names to gnu style is probably not so important.
If you get difficulties to maintain the code if you change the names,
it is against the intention of coding standards.

> >   BTW, I think you will also have to send a copyright assignment to
> > the FSF. Gordon will describe how to send it.
> 
> Why? And what do this imply?

The FSF needs to hold the copyright for their projects. This ensures
that the FSF has the legal right to distribute the package, and the
right to defend its free status in court if necessary.

  Jochen