Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Bump xfsprogs to next version for better compatibility with arm
Date: Sat, 17 Jul 2010 12:17:43 +0200	[thread overview]
Message-ID: <4C418347.4070304@gmx.net> (raw)

Hi mailinglist,

I tried to use a newer version of xfsprogs (3.1.2). According to the 
xfs-homepage there are some issues fixed for usage with arm based systems.

I'll give it a green try by changing to higher version in xfsprogs.mk. I 
found a patch on gentoo (building with shared libs) and they changed the 
dependency from e2fsprogs to util-linux. I've done the same in 
xfsprogs.mk and Config.in in the packages directory.

Now I get an error. Libtool doesn't want to link it:
"libtool: link: only absolute run-paths are allowed"
Google gives a ton of hits, but I can't adapt any answer to building 
xfsprogs 3.1.2 within buildroot.

Maybe someone of the list readers trapped into the same error with 
building shared/static and host libpaths and internal br lib paths?

Thanks for any hint.

Kind regards,
Marcus



/usr/bin/make -j1 
PATH="/home/ossy/buildroot/buildroot-dev/output/host/bin:/home/ossy/buildroot/buildroot-dev/output/host/usr/bin:/home/ossy
/buildroot/buildroot-dev/output/host/usr/sbin/:/usr/local/bin:/usr/bin:/bin:/usr/games" 
CPPFLAGS="-I/home/ossy/buildroot/buildroot-dev/outpu
t/build/util-linux-2.13-pre7/lib" \
 
LDFLAGS="-L/home/ossy/buildroot/buildroot-dev/output/build/util-linux-2.13-pre7/lib" 
-C /home/ossy/buildroot/buildroot-dev/o
utput/build/xfsprogs-3.1.2
make[1]: Entering directory 
`/home/ossy/buildroot/buildroot-dev/output/build/xfsprogs-3.1.2'
Building include
Building libxfs
     [DEP]
     [LD]     libxfs.la
libtool: link: only absolute run-paths are allowed

                 reply	other threads:[~2010-07-17 10:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C418347.4070304@gmx.net \
    --to=ossy1980@gmx.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox