GNU bug report logs - #26016
Regarding how to link gzip

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26016 in the body.
You can then email your comments to 26016 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
To: "bug-gzip <at> gnu.org" <bug-gzip <at> gnu.org>
Subject: Regarding how to link gzip
Date: Tue, 7 Mar 2017 12:07:01 +0000

[Message part 1 (text/plain, inline)]

Hi,

I am Sarthak Jain working as a Software Developer at Novell, India.

We are using gzip library in our product and I was upgrading the library to the latest version 1.8. While building, we saw that is it using '/usr/bin/ld' for linking. But on our build machine, we want to link it with 'gcc'.
Is there any flag we need to pass while configuring to tell it to link using 'gcc' instead of '/usr/bin/ld'.

I tried to see in the configure script but I was not able to get one. Can you please share some info on this?

Thanks
Sarthak

[Message part 2 (text/html, inline)]

Message #8 received at 26016 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
Cc: 26016 <at> debbugs.gnu.org
Subject: Re: bug#26016: Regarding how to link gzip
Date: Fri, 10 Mar 2017 19:39:12 -0800

tags 26016 moreinfo
done

On Tue, Mar 7, 2017 at 4:07 AM, Sarthak Jain
<Sarthak.Jain <at> microfocus.com> wrote:
> We are using gzip library in our product and I was upgrading the library to the latest version 1.8. While building, we saw that is it using '/usr/bin/ld' for linking. But on our build machine, we want to link it with 'gcc'.
> Is there any flag we need to pass while configuring to tell it to link using 'gcc' instead of '/usr/bin/ld'.
>
> I tried to see in the configure script but I was not able to get one. Can you please share some info on this?

We may be able to help, but only if you first tell us more about your problem:
  - what precise commands you ran (starting from the pristine unpacked
gzip-1.8 tarball)
  - what output they produced
  - describe your system, i.e., Fedora 25, Solaris 11, Debian unstable, etc.

Message #11 received at 26016 <at> debbugs.gnu.org (full text, mbox):

From: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: "26016 <at> debbugs.gnu.org" <26016 <at> debbugs.gnu.org>
Subject: RE: bug#26016: Regarding how to link gzip
Date: Thu, 16 Mar 2017 09:03:35 +0000

[Message part 1 (text/plain, inline)]

Hi,
We have followed the following shell commands-

CFLAGS := -gdwarf-2
gunzip gzip-1.8.tar.gz && tar -xf gzip-1.8.tar
export CFLAGS
./configure --prefix=<some-dir>
make all
make install

These are the commands we have executed. Please find the attached output of './configure'. Our build machine is (x86_64 SuSE10SP4)

Thanks
Sarthak

-----Original Message-----
From: meyering <at> gmail.com [mailto:meyering <at> gmail.com] On Behalf Of Jim Meyering
Sent: Saturday, March 11, 2017 9:09 AM
To: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
Cc: 26016 <at> debbugs.gnu.org
Subject: Re: bug#26016: Regarding how to link gzip

tags 26016 moreinfo
done

On Tue, Mar 7, 2017 at 4:07 AM, Sarthak Jain <Sarthak.Jain <at> microfocus.com> wrote:
> We are using gzip library in our product and I was upgrading the library to the latest version 1.8. While building, we saw that is it using '/usr/bin/ld' for linking. But on our build machine, we want to link it with 'gcc'.
> Is there any flag we need to pass while configuring to tell it to link using 'gcc' instead of '/usr/bin/ld'.
>
> I tried to see in the configure script but I was not able to get one. Can you please share some info on this?

We may be able to help, but only if you first tell us more about your problem:
  - what precise commands you ran (starting from the pristine unpacked
gzip-1.8 tarball)
  - what output they produced
  - describe your system, i.e., Fedora 25, Solaris 11, Debian unstable, etc.

[output-configure.txt (text/plain, attachment)]

Message #14 received at 26016 <at> debbugs.gnu.org (full text, mbox):

From: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: "26016 <at> debbugs.gnu.org" <26016 <at> debbugs.gnu.org>
Subject: RE: bug#26016: Regarding how to link gzip
Date: Thu, 16 Mar 2017 09:05:50 +0000

Somehow the newlines in the commands I mentioned got removed which is making it clumsy. Please find the commands as:

CFLAGS := -gdwarf-2
gunzip gzip-1.8.tar.gz && tar -xf gzip-1.8.tar
export CFLAGS
./configure --prefix=<some-dir>
make all
make install


-----Original Message-----
From: Sarthak Jain 
Sent: Thursday, March 16, 2017 2:34 PM
To: 'Jim Meyering' <jim <at> meyering.net>
Cc: 26016 <at> debbugs.gnu.org
Subject: RE: bug#26016: Regarding how to link gzip

Hi,
We have followed the following shell commands-

CFLAGS := -gdwarf-2
gunzip gzip-1.8.tar.gz && tar -xf gzip-1.8.tar export CFLAGS ./configure --prefix=<some-dir> make all make install

These are the commands we have executed. Please find the attached output of './configure'. Our build machine is (x86_64 SuSE10SP4)

Thanks
Sarthak

-----Original Message-----
From: meyering <at> gmail.com [mailto:meyering <at> gmail.com] On Behalf Of Jim Meyering
Sent: Saturday, March 11, 2017 9:09 AM
To: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
Cc: 26016 <at> debbugs.gnu.org
Subject: Re: bug#26016: Regarding how to link gzip

tags 26016 moreinfo
done

On Tue, Mar 7, 2017 at 4:07 AM, Sarthak Jain <Sarthak.Jain <at> microfocus.com> wrote:
> We are using gzip library in our product and I was upgrading the library to the latest version 1.8. While building, we saw that is it using '/usr/bin/ld' for linking. But on our build machine, we want to link it with 'gcc'.
> Is there any flag we need to pass while configuring to tell it to link using 'gcc' instead of '/usr/bin/ld'.
>
> I tried to see in the configure script but I was not able to get one. Can you please share some info on this?

We may be able to help, but only if you first tell us more about your problem:
  - what precise commands you ran (starting from the pristine unpacked
gzip-1.8 tarball)
  - what output they produced
  - describe your system, i.e., Fedora 25, Solaris 11, Debian unstable, etc.

Message #17 received at 26016 <at> debbugs.gnu.org (full text, mbox):

From: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
To: Jim Meyering <jim <at> meyering.net>
Cc: "26016 <at> debbugs.gnu.org" <26016 <at> debbugs.gnu.org>
Subject: RE: bug#26016: Regarding how to link gzip
Date: Mon, 20 Mar 2017 09:56:51 +0000

Can I please expect some reply from my previous email?  I am running out of time.

Thank you!

-----Original Message-----
From: Sarthak Jain 
Sent: Thursday, March 16, 2017 2:36 PM
To: 'Jim Meyering' <jim <at> meyering.net>
Cc: '26016 <at> debbugs.gnu.org' <26016 <at> debbugs.gnu.org>
Subject: RE: bug#26016: Regarding how to link gzip

Somehow the newlines in the commands I mentioned got removed which is making it clumsy. Please find the commands as:

CFLAGS := -gdwarf-2
gunzip gzip-1.8.tar.gz && tar -xf gzip-1.8.tar
export CFLAGS
./configure --prefix=<some-dir>
make all
make install


-----Original Message-----
From: Sarthak Jain 
Sent: Thursday, March 16, 2017 2:34 PM
To: 'Jim Meyering' <jim <at> meyering.net>
Cc: 26016 <at> debbugs.gnu.org
Subject: RE: bug#26016: Regarding how to link gzip

Hi,
We have followed the following shell commands-

CFLAGS := -gdwarf-2
gunzip gzip-1.8.tar.gz && tar -xf gzip-1.8.tar export CFLAGS ./configure --prefix=<some-dir> make all make install

These are the commands we have executed. Please find the attached output of './configure'. Our build machine is (x86_64 SuSE10SP4)

Thanks
Sarthak

-----Original Message-----
From: meyering <at> gmail.com [mailto:meyering <at> gmail.com] On Behalf Of Jim Meyering
Sent: Saturday, March 11, 2017 9:09 AM
To: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
Cc: 26016 <at> debbugs.gnu.org
Subject: Re: bug#26016: Regarding how to link gzip

tags 26016 moreinfo
done

On Tue, Mar 7, 2017 at 4:07 AM, Sarthak Jain <Sarthak.Jain <at> microfocus.com> wrote:
> We are using gzip library in our product and I was upgrading the library to the latest version 1.8. While building, we saw that is it using '/usr/bin/ld' for linking. But on our build machine, we want to link it with 'gcc'.
> Is there any flag we need to pass while configuring to tell it to link using 'gcc' instead of '/usr/bin/ld'.
>
> I tried to see in the configure script but I was not able to get one. Can you please share some info on this?

We may be able to help, but only if you first tell us more about your problem:
  - what precise commands you ran (starting from the pristine unpacked
gzip-1.8 tarball)
  - what output they produced
  - describe your system, i.e., Fedora 25, Solaris 11, Debian unstable, etc.

Message #20 received at 26016 <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
Cc: "26016 <at> debbugs.gnu.org" <26016 <at> debbugs.gnu.org>
Subject: Re: bug#26016: Regarding how to link gzip
Date: Mon, 20 Mar 2017 06:50:37 -0700

On Thu, Mar 16, 2017 at 2:03 AM, Sarthak Jain
<Sarthak.Jain <at> microfocus.com> wrote:
> Hi,
> We have followed the following shell commands-
>
> CFLAGS := -gdwarf-2
> gunzip gzip-1.8.tar.gz && tar -xf gzip-1.8.tar
> export CFLAGS
> ./configure --prefix=<some-dir>
> make all
> make install
>
> These are the commands we have executed. Please find the attached output of './configure'. Our build machine is (x86_64 SuSE10SP4)
>
> Thanks
> Sarthak
>
> -----Original Message-----
> From: meyering <at> gmail.com [mailto:meyering <at> gmail.com] On Behalf Of Jim Meyering
> Sent: Saturday, March 11, 2017 9:09 AM
> To: Sarthak Jain <Sarthak.Jain <at> microfocus.com>
> Cc: 26016 <at> debbugs.gnu.org
> Subject: Re: bug#26016: Regarding how to link gzip
>
> tags 26016 moreinfo
> done
>
> On Tue, Mar 7, 2017 at 4:07 AM, Sarthak Jain <Sarthak.Jain <at> microfocus.com> wrote:
>> We are using gzip library in our product and I was upgrading the library to the latest version 1.8. While building, we saw that is it using '/usr/bin/ld' for linking. But on our build machine, we want to link it with 'gcc'.
>> Is there any flag we need to pass while configuring to tell it to link using 'gcc' instead of '/usr/bin/ld'.
>>
>> I tried to see in the configure script but I was not able to get one. Can you please share some info on this?
>
> We may be able to help, but only if you first tell us more about your problem:
>   - what precise commands you ran (starting from the pristine unpacked
> gzip-1.8 tarball)
>   - what output they produced
>   - describe your system, i.e., Fedora 25, Solaris 11, Debian unstable, etc.

Please do not top-post on technical mailing lists.

Your commands start with an invalid "CFLAGS := -gdwarf-2". That would
evoke an error for any bourne shell. If you actually did something
else, please include the *precise* commands that you ran and all
output. Did you actually type "CFLAGS=-gdwarf-2" ? You make it
unnecessarily hard to debug your problem when we have to guess things
like this.

Nothing about your configure output suggests there is a problem, and
you included no output from the "make" commands. I suggest that you
run "make V=1 > out 2>&1" and attach that "out" file if there is some
failure.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.