Re: [blfs-support] JSON-C fails to build
On 12/21/2013 03:06 PM, Chris Staub wrote: > On 12/21/13 10:54, Dan McGhee wrote: >> On 12/21/2013 01:40 AM, Chris Staub wrote: >> This happened again for me with cdparanoia, which also, as the book >> says, does not support a parallel build. I'm not sure how to set, change >> or remove these flags. >> >> Dan >> > There's almost certainly something in your own build scripts that sets > MAKEFLAGS, or some other variable that tells make to use -j, as this is > not something that is done by default. Try to grep your build scripts > for "MAKEFLAGS", "-j", "CONFIG_SITE" or "config.site" to see where it's > coming from. This arrived as I was posting a reply to this thread. It's got to be in the "install_package" wrapper for Package Users. I can use the scripts as me and root with no problems, but, as I said in the other posts, for each pacage user, $MAKEFLAGS=-j8. Don't ask. I don't know. :) Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/21/2013 02:55 PM, Bruce Dubbs wrote: > Pierre Labastie wrote: >> Le 21/12/2013 16:54, Dan McGhee a écrit : >>> On 12/21/2013 01:40 AM, Chris Staub wrote: I don't normally use json-c, but as I use package users myself I thought I'd try it. I got exactly the same build failure when I used "-j4" with make, and BLFS does say that this package does not support parallel builds. It worked fine once I removed the -j. If it worked as root it's probably just because you don't have MAKEFLAGS or something defined as root. >>> This happened again for me with cdparanoia, which also, as the book >>> says, does not support a parallel build. I'm not sure how to set, change >>> or remove these flags. >>> >>> Dan >>> >> The -j flag for make is either set on the command line (takes precedence) or >> in MAKEFLAGS. >> >> Try "echo $MAKEFLAGS", to see what is in there. If it is empty, well, this >> is something else. Do you use some kinf of cache (say config.site or so)? >> MAKEFLAGS is maybe defined there. >> >> OTOH, it is always possible to replace "make" with "make -j1", whether in >> scripts or on the command line. > Or 'MAKEFLAGS="" make' > > -- Bruce > I found something interesting in my system. I had this problem with JSON-C, S-LANG and cdparanoia. All these packages have the "don't support parallel builds" note. This has never been a problem for me in the past or until just recently. After Ken's and Chris's posts, I looked. For both root and me, $MAKEFLAGS="". But for the package users, $MAKEFLAGS=-j8. How that happened is beyond me. I changed my build.conf to compensate for this and all the packages, with which I had problems, built without a hitch. Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/21/13 10:54, Dan McGhee wrote: > On 12/21/2013 01:40 AM, Chris Staub wrote: > This happened again for me with cdparanoia, which also, as the book > says, does not support a parallel build. I'm not sure how to set, change > or remove these flags. > > Dan > There's almost certainly something in your own build scripts that sets MAKEFLAGS, or some other variable that tells make to use -j, as this is not something that is done by default. Try to grep your build scripts for "MAKEFLAGS", "-j", "CONFIG_SITE" or "config.site" to see where it's coming from. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
Pierre Labastie wrote: > Le 21/12/2013 16:54, Dan McGhee a écrit : >> On 12/21/2013 01:40 AM, Chris Staub wrote: >>> I don't normally use json-c, but as I use package users myself I thought >>> I'd try it. I got exactly the same build failure when I used "-j4" with >>> make, and BLFS does say that this package does not support parallel >>> builds. It worked fine once I removed the -j. If it worked as root it's >>> probably just because you don't have MAKEFLAGS or something defined as root. >> This happened again for me with cdparanoia, which also, as the book >> says, does not support a parallel build. I'm not sure how to set, change >> or remove these flags. >> >> Dan >> > The -j flag for make is either set on the command line (takes precedence) or > in MAKEFLAGS. > > Try "echo $MAKEFLAGS", to see what is in there. If it is empty, well, this > is something else. Do you use some kinf of cache (say config.site or so)? > MAKEFLAGS is maybe defined there. > > OTOH, it is always possible to replace "make" with "make -j1", whether in > scripts or on the command line. Or 'MAKEFLAGS="" make' -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
Le 21/12/2013 16:54, Dan McGhee a écrit : > On 12/21/2013 01:40 AM, Chris Staub wrote: >> I don't normally use json-c, but as I use package users myself I thought >> I'd try it. I got exactly the same build failure when I used "-j4" with >> make, and BLFS does say that this package does not support parallel >> builds. It worked fine once I removed the -j. If it worked as root it's >> probably just because you don't have MAKEFLAGS or something defined as root. > This happened again for me with cdparanoia, which also, as the book > says, does not support a parallel build. I'm not sure how to set, change > or remove these flags. > > Dan > The -j flag for make is either set on the command line (takes precedence) or in MAKEFLAGS. Try "echo $MAKEFLAGS", to see what is in there. If it is empty, well, this is something else. Do you use some kinf of cache (say config.site or so)? MAKEFLAGS is maybe defined there. OTOH, it is always possible to replace "make" with "make -j1", whether in scripts or on the command line. Regards Pierre -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/21/2013 01:40 AM, Chris Staub wrote: > I don't normally use json-c, but as I use package users myself I thought > I'd try it. I got exactly the same build failure when I used "-j4" with > make, and BLFS does say that this package does not support parallel > builds. It worked fine once I removed the -j. If it worked as root it's > probably just because you don't have MAKEFLAGS or something defined as root. This happened again for me with cdparanoia, which also, as the book says, does not support a parallel build. I'm not sure how to set, change or remove these flags. Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
I'm building JSON-C as a dependency for PulseAudio. It fails to build with: > > > /bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra > > -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE > > -D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o > > libjson.la -rpath /usr/lib libjson.lo -ljson-c > > mv -f .deps/json_util.Tpo .deps/json_util.Plo > > mv -f .deps/printbuf.Tpo .deps/printbuf.Plo > > mv -f .deps/linkhash.Tpo .deps/linkhash.Plo > > libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname > > -Wl,libjson.so.0 -o .libs/libjson.so.0.1.0 > > /usr/bin/ld: cannot find -ljson-c > > collect2: error: ld returned 1 exit status > > make[2]: *** [libjson.la] Error 1 > > make[2]: *** Waiting for unfinished jobs > > mv -f .deps/json_object.Tpo .deps/json_object.Plo > > mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo > > make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' > > make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' > > make[1]: *** [all-recursive] Error 1 > > make: *** [all] Error 2 > > I don't know if it's relevant, but the README file contains this: > > > Linking to libjson-c > > > > If your system has pkgconfig then you can just add this to your makefile > > > > CFLAGS += $(shell pkg-config --cflags json-c) > > LDFLAGS += $(shell pkg-config --libs json-c) > > > > Without pkgconfig, you would do something like this: > > > > JSON_C_DIR=/path/to/json_c/install > > CFLAGS += -I$(JSON_C_DIR)/include/json-c > > LDFLAGS+= -L$(JSON_C_DIR)/lib -ljson-c > > If it's relevant to pass any of these things to get JSON-C to build, how > and where would I do it? > > You could try Jansson, I think it's a drop-in replacement and that built just fine for me. Richard -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/20/13 13:09, Dan McGhee wrote: > On 12/20/2013 11:41 AM, Bruce Dubbs wrote: > I'm building JSON-C as a dependency for PulseAudio. It fails to build > with: > >> /bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra >> -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE >> -D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o >> libjson.la -rpath /usr/lib libjson.lo -ljson-c >> mv -f .deps/json_util.Tpo .deps/json_util.Plo >> mv -f .deps/printbuf.Tpo .deps/printbuf.Plo >> mv -f .deps/linkhash.Tpo .deps/linkhash.Plo >> libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname >> -Wl,libjson.so.0 -o .libs/libjson.so.0.1.0 >> /usr/bin/ld: cannot find -ljson-c >> collect2: error: ld returned 1 exit status >> make[2]: *** [libjson.la] Error 1 >> make[2]: *** Waiting for unfinished jobs >> mv -f .deps/json_object.Tpo .deps/json_object.Plo >> mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo >> make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' >> make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 > I don't know if it's relevant, but the README file contains this: > > Thanks, Bruce. I'm so locked in on getting sound that I didn't think > about that until after I responded to Armin. First, I built and did a > DESTDIR install as me, then a DESTIR and a final install as root. Then > used chown to get the package user involved. There didn't seem to be any > permissions problems. > > This is actually a mosquito bite right now. I *think* it's a path and > permissions problem with `/usr/bin/ld.` Things worked fine when I built > as me. When I'm through with sound and printing, I'll come back and > troubleshoot this some more. > > Dan > I don't normally use json-c, but as I use package users myself I thought I'd try it. I got exactly the same build failure when I used "-j4" with make, and BLFS does say that this package does not support parallel builds. It worked fine once I removed the -j. If it worked as root it's probably just because you don't have MAKEFLAGS or something defined as root. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On Fri, Dec 20, 2013 at 12:09:30PM -0600, Dan McGhee wrote: > Thanks, Bruce. I'm so locked in on getting sound that I didn't think > about that until after I responded to Armin. First, I built and did a > DESTDIR install as me, then a DESTIR and a final install as root. Then > used chown to get the package user involved. There didn't seem to be any > permissions problems. > > This is actually a mosquito bite right now. I *think* it's a path and > permissions problem with `/usr/bin/ld.` Things worked fine when I built > as me. When I'm through with sound and printing, I'll come back and > troubleshoot this some more. > I've been away from my machines, so coming late to this thread. I had a similar problem when building this to test some gnome packages with make-4.0. In my case, falling back to make -j1 instead of -j4 fixed it for me. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/20/2013 11:41 AM, Bruce Dubbs wrote:
> Dan McGhee wrote:
>> On 12/20/2013 11:18 AM, Armin K. wrote:
>>> On 12/20/2013 06:15 PM, Dan McGhee wrote:
I'm building JSON-C as a dependency for PulseAudio. It fails to build
with:
> /bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra
> -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE
> -D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o
> libjson.la -rpath /usr/lib libjson.lo -ljson-c
> mv -f .deps/json_util.Tpo .deps/json_util.Plo
> mv -f .deps/printbuf.Tpo .deps/printbuf.Plo
> mv -f .deps/linkhash.Tpo .deps/linkhash.Plo
> libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname
> -Wl,libjson.so.0 -o .libs/libjson.so.0.1.0
> /usr/bin/ld: cannot find -ljson-c
> collect2: error: ld returned 1 exit status
> make[2]: *** [libjson.la] Error 1
> make[2]: *** Waiting for unfinished jobs
> mv -f .deps/json_object.Tpo .deps/json_object.Plo
> mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo
> make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
> make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
I don't know if it's relevant, but the README file contains this:
> Linking to libjson-c
>
> If your system has pkgconfig then you can just add this to your makefile
>
> CFLAGS += $(shell pkg-config --cflags json-c)
> LDFLAGS += $(shell pkg-config --libs json-c)
>
> Without pkgconfig, you would do something like this:
>
> JSON_C_DIR=/path/to/json_c/install
> CFLAGS += -I$(JSON_C_DIR)/include/json-c
> LDFLAGS+= -L$(JSON_C_DIR)/lib -ljson-c
If it's relevant to pass any of these things to get JSON-C to build, how
and where would I do it?
Thanks,
Dan
>>> libjson-c is built as part of the same package and it should be present
>>> in the build directory, .libs subdirectory.
>>>
>> That's what I thought, and what I saw when I looked into the build
>> directory. That's what I found so strange. But the build failed four
>> times. I wonder if there's something wrong in $PATH. I use the Package
>> Users system, and I'm investigating that possibility right now. However,
>> this is the first and only package of almost 200 that I've built in
>> {,B}LFS so far that has failed to build.
> When you have a problem with package users, try falling back to the
> standard build procedures up to the point where you install. Also try
> building (again not installing) as root to remove possible permission
> problems. If that works, you need to go back and debug the problems you
> introduced.
Thanks, Bruce. I'm so locked in on getting sound that I didn't think
about that until after I responded to Armin. First, I built and did a
DESTDIR install as me, then a DESTIR and a final install as root. Then
used chown to get the package user involved. There didn't seem to be any
permissions problems.
This is actually a mosquito bite right now. I *think* it's a path and
permissions problem with `/usr/bin/ld.` Things worked fine when I built
as me. When I'm through with sound and printing, I'll come back and
troubleshoot this some more.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
Dan McGhee wrote:
> On 12/20/2013 11:18 AM, Armin K. wrote:
>> On 12/20/2013 06:15 PM, Dan McGhee wrote:
>>> I'm building JSON-C as a dependency for PulseAudio. It fails to build with:
>>>
/bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra
-Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE
-D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o
libjson.la -rpath /usr/lib libjson.lo -ljson-c
mv -f .deps/json_util.Tpo .deps/json_util.Plo
mv -f .deps/printbuf.Tpo .deps/printbuf.Plo
mv -f .deps/linkhash.Tpo .deps/linkhash.Plo
libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname
-Wl,libjson.so.0 -o .libs/libjson.so.0.1.0
/usr/bin/ld: cannot find -ljson-c
collect2: error: ld returned 1 exit status
make[2]: *** [libjson.la] Error 1
make[2]: *** Waiting for unfinished jobs
mv -f .deps/json_object.Tpo .deps/json_object.Plo
mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo
make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
>>> I don't know if it's relevant, but the README file contains this:
>>>
Linking to libjson-c
If your system has pkgconfig then you can just add this to your makefile
CFLAGS += $(shell pkg-config --cflags json-c)
LDFLAGS += $(shell pkg-config --libs json-c)
Without pkgconfig, you would do something like this:
JSON_C_DIR=/path/to/json_c/install
CFLAGS += -I$(JSON_C_DIR)/include/json-c
LDFLAGS+= -L$(JSON_C_DIR)/lib -ljson-c
>>> If it's relevant to pass any of these things to get JSON-C to build, how
>>> and where would I do it?
>>>
>>> Thanks,
>>> Dan
>>>
>>>
>>>
>> libjson-c is built as part of the same package and it should be present
>> in the build directory, .libs subdirectory.
>>
> That's what I thought, and what I saw when I looked into the build
> directory. That's what I found so strange. But the build failed four
> times. I wonder if there's something wrong in $PATH. I use the Package
> Users system, and I'm investigating that possibility right now. However,
> this is the first and only package of almost 200 that I've built in
> {,B}LFS so far that has failed to build.
When you have a problem with package users, try falling back to the
standard build procedures up to the point where you install. Also try
building (again not installing) as root to remove possible permission
problems. If that works, you need to go back and debug the problems you
introduced.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/20/2013 11:32 AM, Dan McGhee wrote:
> On 12/20/2013 11:18 AM, Armin K. wrote:
>> On 12/20/2013 06:15 PM, Dan McGhee wrote:
>>> I'm building JSON-C as a dependency for PulseAudio. It fails to build with:
>>>
/bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra
-Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE
-D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o
libjson.la -rpath /usr/lib libjson.lo -ljson-c
mv -f .deps/json_util.Tpo .deps/json_util.Plo
mv -f .deps/printbuf.Tpo .deps/printbuf.Plo
mv -f .deps/linkhash.Tpo .deps/linkhash.Plo
libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname
-Wl,libjson.so.0 -o .libs/libjson.so.0.1.0
/usr/bin/ld: cannot find -ljson-c
collect2: error: ld returned 1 exit status
make[2]: *** [libjson.la] Error 1
make[2]: *** Waiting for unfinished jobs
mv -f .deps/json_object.Tpo .deps/json_object.Plo
mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo
make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
>>> I don't know if it's relevant, but the README file contains this:
>>>
Linking to libjson-c
If your system has pkgconfig then you can just add this to your makefile
CFLAGS += $(shell pkg-config --cflags json-c)
LDFLAGS += $(shell pkg-config --libs json-c)
Without pkgconfig, you would do something like this:
JSON_C_DIR=/path/to/json_c/install
CFLAGS += -I$(JSON_C_DIR)/include/json-c
LDFLAGS+= -L$(JSON_C_DIR)/lib -ljson-c
>>> If it's relevant to pass any of these things to get JSON-C to build, how
>>> and where would I do it?
>>>
>>> Thanks,
>>> Dan
>>>
>>>
>>>
>> libjson-c is built as part of the same package and it should be present
>> in the build directory, .libs subdirectory.
>>
> That's what I thought, and what I saw when I looked into the build
> directory. That's what I found so strange. But the build failed four
> times. I wonder if there's something wrong in $PATH. I use the Package
> Users system, and I'm investigating that possibility right now. However,
> this is the first and only package of almost 200 that I've built in
> {,B}LFS so far that has failed to build.
>
> Dan
>
>
>
There must be some conflict between this package and the Package Users
system. I didn't want to mess with it so I built as me and installed as
root. Everything was fine. No problems now.
Thanks for at least looking, Armin.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/20/2013 11:18 AM, Armin K. wrote:
> On 12/20/2013 06:15 PM, Dan McGhee wrote:
>> I'm building JSON-C as a dependency for PulseAudio. It fails to build with:
>>
>>> /bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra
>>> -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE
>>> -D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o
>>> libjson.la -rpath /usr/lib libjson.lo -ljson-c
>>> mv -f .deps/json_util.Tpo .deps/json_util.Plo
>>> mv -f .deps/printbuf.Tpo .deps/printbuf.Plo
>>> mv -f .deps/linkhash.Tpo .deps/linkhash.Plo
>>> libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname
>>> -Wl,libjson.so.0 -o .libs/libjson.so.0.1.0
>>> /usr/bin/ld: cannot find -ljson-c
>>> collect2: error: ld returned 1 exit status
>>> make[2]: *** [libjson.la] Error 1
>>> make[2]: *** Waiting for unfinished jobs
>>> mv -f .deps/json_object.Tpo .deps/json_object.Plo
>>> mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo
>>> make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
>>> make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11'
>>> make[1]: *** [all-recursive] Error 1
>>> make: *** [all] Error 2
>> I don't know if it's relevant, but the README file contains this:
>>
>>> Linking to libjson-c
>>>
>>> If your system has pkgconfig then you can just add this to your makefile
>>>
>>> CFLAGS += $(shell pkg-config --cflags json-c)
>>> LDFLAGS += $(shell pkg-config --libs json-c)
>>>
>>> Without pkgconfig, you would do something like this:
>>>
>>> JSON_C_DIR=/path/to/json_c/install
>>> CFLAGS += -I$(JSON_C_DIR)/include/json-c
>>> LDFLAGS+= -L$(JSON_C_DIR)/lib -ljson-c
>> If it's relevant to pass any of these things to get JSON-C to build, how
>> and where would I do it?
>>
>> Thanks,
>> Dan
>>
>>
>>
> libjson-c is built as part of the same package and it should be present
> in the build directory, .libs subdirectory.
>
That's what I thought, and what I saw when I looked into the build
directory. That's what I found so strange. But the build failed four
times. I wonder if there's something wrong in $PATH. I use the Package
Users system, and I'm investigating that possibility right now. However,
this is the first and only package of almost 200 that I've built in
{,B}LFS so far that has failed to build.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] JSON-C fails to build
On 12/20/2013 06:15 PM, Dan McGhee wrote: > I'm building JSON-C as a dependency for PulseAudio. It fails to build with: > >> /bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra >> -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE >> -D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o >> libjson.la -rpath /usr/lib libjson.lo -ljson-c >> mv -f .deps/json_util.Tpo .deps/json_util.Plo >> mv -f .deps/printbuf.Tpo .deps/printbuf.Plo >> mv -f .deps/linkhash.Tpo .deps/linkhash.Plo >> libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname >> -Wl,libjson.so.0 -o .libs/libjson.so.0.1.0 >> /usr/bin/ld: cannot find -ljson-c >> collect2: error: ld returned 1 exit status >> make[2]: *** [libjson.la] Error 1 >> make[2]: *** Waiting for unfinished jobs >> mv -f .deps/json_object.Tpo .deps/json_object.Plo >> mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo >> make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' >> make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' >> make[1]: *** [all-recursive] Error 1 >> make: *** [all] Error 2 > > I don't know if it's relevant, but the README file contains this: > >> Linking to libjson-c >> >> If your system has pkgconfig then you can just add this to your makefile >> >> CFLAGS += $(shell pkg-config --cflags json-c) >> LDFLAGS += $(shell pkg-config --libs json-c) >> >> Without pkgconfig, you would do something like this: >> >> JSON_C_DIR=/path/to/json_c/install >> CFLAGS += -I$(JSON_C_DIR)/include/json-c >> LDFLAGS+= -L$(JSON_C_DIR)/lib -ljson-c > > If it's relevant to pass any of these things to get JSON-C to build, how > and where would I do it? > > Thanks, > Dan > > > libjson-c is built as part of the same package and it should be present in the build directory, .libs subdirectory. -- Note: My last name is not Krejzi. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-support] JSON-C fails to build
I'm building JSON-C as a dependency for PulseAudio. It fails to build with: > /bin/sh ./libtool --tag=CC --mode=link gcc -Wall -Werror -Wextra > -Wwrite-strings -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE > -D_REENTRANT -g -O2 -version-info 1:0:1 -no-undefined -ljson-c -o > libjson.la -rpath /usr/lib libjson.lo -ljson-c > mv -f .deps/json_util.Tpo .deps/json_util.Plo > mv -f .deps/printbuf.Tpo .deps/printbuf.Plo > mv -f .deps/linkhash.Tpo .deps/linkhash.Plo > libtool: link: gcc -shared .libs/libjson.o -ljson-c -Wl,-soname > -Wl,libjson.so.0 -o .libs/libjson.so.0.1.0 > /usr/bin/ld: cannot find -ljson-c > collect2: error: ld returned 1 exit status > make[2]: *** [libjson.la] Error 1 > make[2]: *** Waiting for unfinished jobs > mv -f .deps/json_object.Tpo .deps/json_object.Plo > mv -f .deps/json_tokener.Tpo .deps/json_tokener.Plo > make[2]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' > make[1]: Leaving directory `/usr/src/json-c-0.11/json-c-0.11' > make[1]: *** [all-recursive] Error 1 > make: *** [all] Error 2 I don't know if it's relevant, but the README file contains this: > Linking to libjson-c > > If your system has pkgconfig then you can just add this to your makefile > > CFLAGS += $(shell pkg-config --cflags json-c) > LDFLAGS += $(shell pkg-config --libs json-c) > > Without pkgconfig, you would do something like this: > > JSON_C_DIR=/path/to/json_c/install > CFLAGS += -I$(JSON_C_DIR)/include/json-c > LDFLAGS+= -L$(JSON_C_DIR)/lib -ljson-c If it's relevant to pass any of these things to get JSON-C to build, how and where would I do it? Thanks, Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
