On Nov 6 21:53, Corinna Vinschen via Cygwin wrote:
> - create binaries with debug info
> - create debug info files from the non-stripped binaries and copy
> them to usr/debug/...
sorry, usr/lib/debug/...
> - strip the binary and pack it into the base package "foo"
> - pack the debug info files
On Nov 6 20:29, Federico Kircheis via Cygwin wrote:
>
> On 06/11/2021 18.30, Corinna Vinschen via Cygwin wrote:
> > On Nov 6 15:31, Federico Kircheis via Cygwin wrote:
> > > it seems that cygport always strip binaries, but I have one program that
> > > when stripped does not work correctly.
> >
On 06/11/2021 18.30, Corinna Vinschen via Cygwin wrote:
On Nov 6 15:31, Federico Kircheis via Cygwin wrote:
it seems that cygport always strip binaries, but I have one program that
when stripped does not work correctly.
Out of curiosity, what program is that? And why does it require the
sym
On Nov 6 15:31, Federico Kircheis via Cygwin wrote:
> it seems that cygport always strip binaries, but I have one program that
> when stripped does not work correctly.
Out of curiosity, what program is that? And why does it require the
symbols to be present in the executable?
Corinna
--
Prob
Federico Kircheis via Cygwin writes:
> I should be able to set something like
>
> STRIP=/usr/bin/true
>
> and then stripping should be a no-op, but it did not work, the
> binaries in the install folder are still stripped.
That only works if strip was used to remove the symbol information. You
pro
Hello,
it seems that cygport always strip binaries, but I have one program that
when stripped does not work correctly.
As far as I've understood
https://cygwin.github.io/cygport/compilers_cygpart.html#robo759
I should be able to set something like
STRIP=/usr/bin/true
and then stripping
6 matches
Mail list logo
